Lstrange: Difference between revisions
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
This page documents the lstrange function of Python module [[Analysis Utilities|analysisUtils]]. | This page documents the lstrange function of Python module [[Analysis Utilities|analysisUtils]]. | ||
Sometimes it is useful to know the LST range over which your scheduling block (SB) was run. For example, this information is useful to the JAO data reduction scientist who can request a certain LST for the next execution of your SB. This command will do that, along with providing the UT and MJD and duration. The only parameter is the ms name. It will calculate the range for the entire ms, and then calculate the range restricted to the scans with ON_SOURCE intent. It also lists the range of elevations ON_SOURCE, and a one-line summary that can be pasted into a table on the SCOPS wikipages. Note that the range on source is typically larger than the total integration time on source. Use the TimeOnSource function to compute the latter. | Sometimes it is useful to know the LST range over which your scheduling block (SB) was run. For example, this information is useful to the JAO data reduction scientist who can request a certain LST for the next execution of your SB. This command will do that, along with providing the UT and MJD and duration. The only parameter is the ms name. It will calculate the range for the entire ms, and then calculate the range restricted to the scans with ON_SOURCE intent. It also lists the range of elevations ON_SOURCE, and a one-line summary that can be pasted into a table on the SCOPS wikipages. Note that the range on source is typically larger than the total integration time on source. Use the [[TimeOnSource]] function to compute the latter. | ||
==Example== | ==Example== | ||
Revision as of 20:42, 4 January 2012
Return to Analysis Utilities
This page documents the lstrange function of Python module analysisUtils.
Sometimes it is useful to know the LST range over which your scheduling block (SB) was run. For example, this information is useful to the JAO data reduction scientist who can request a certain LST for the next execution of your SB. This command will do that, along with providing the UT and MJD and duration. The only parameter is the ms name. It will calculate the range for the entire ms, and then calculate the range restricted to the scans with ON_SOURCE intent. It also lists the range of elevations ON_SOURCE, and a one-line summary that can be pasted into a table on the SCOPS wikipages. Note that the range on source is typically larger than the total integration time on source. Use the TimeOnSource function to compute the latter.
Example
aU.lstrange('uid___A002_X2eea47_X1e0.ms')
Found observatory = ALMA
Running ValueMapping... (this may take a minute)
Ignoring spectral window [0, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37] because it is WVR related
Found scans = [ 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27]
On source scans = [15 18 22 25]
LST range of whole SB = 19.56 to 20.75 = 19:33 to 20:45 (71.4 minutes)
MJD range of whole SB = 55854.9226 to 55854.9721
UT range of whole SB = 2011-10-20 22:08:36 UT to 2011-10-20 23:19:49 UT
LST range on source = 20.20 to 20.71 = 20:12 to 20:42 (30.4 minutes)
MJD range on source = 55854.9493 to 55854.9704
UT range on source = 2011-10-20 22:47:02 UT to 2011-10-20 23:17:24 UT
