OPT: Importing Scheduling Blocks
Note: due to a recent upgrade in Firefox (version 115.x), the functionality of uploading an SB as a text file has been broken. If you want to upload an SB as a text file, NRAO staff have determined that the following browsers and platforms will work: Safari (Mac), Chrome (Mac, Windows, Linux), Opera (Mac, Windows, Linux), and Microsoft Edge (Windows).
Scheduling Blocks and Scan Lists
First, note the differences between importing scan lists and importing complete scheduling blocks:
- A text file representing a complete scheduling block (SB) defines not only the scan list, but also defines the variables needed for a scheduling block
- Importing scheduling blocks will create a new SB entry in the active Program Block, whereas importing a scan list will add the scans to an active Scheduling Block directly after the active scan, or at the start if the active field is the SB name.
In this section we discuss the scheduling block preamble, and in the next we describe importing scan lists. Note that we are creating experimental scripts that take an ordered list of source names and produce a text file for import into the OPT. This should be helpful to create simple observing schedules. Please let the NRAO Science Helpdesk know if you are interested in trying this out.
Scheduling Block Preamble
A text file defining a scheduling block has to begin with the following case-sensitive content (boldface lines are mandatory):
VERSION;versionNumber;
SCHED-BLOCK;schedBlockName;schedulingType;iterationCount;date;timeOfDay;shadowLimit;. . .
. . .shadowCalcConfiguration;initTeleAz;initTeleEl;avoidSunrise?;avoidSunset?;. . .
. . .windApi;commentsToOperator;
The VERSION line is optional, but if present it must be the first data line and include an integer versionNumber in the second field between two semi-colons (;). The current maximum versionNumber is 6. If the line is omitted, versionNumber defaults to the latest version of the syntax. The documentation here is for the latest version.
The SCHED-BLOCK line distinguishes a complete scheduling block input text file from a scan list input text file. Only a single SCHED-BLOCK line is allowed in the file and has to precede any scan list lines (below). If it is not present the file will be interpreted as a scan list only file as described later. Apart from the data field identifier “SCHED-BLOCK”, this line includes 13 fields and exactly 14 semi-colons (;), including the last. Details and possible (predefined) values per field are described in the table below. Note that unless specified otherwise, the parsing of strings is case sensitive.
schedBlockName |
Optional, single value (defaults to [New Scheduling Block])
|
schedulingType |
Optional, single value (defaults to Dynamic), not case-sensitive
|
iterationCount |
Optional, single value (defaults to 1)
|
date |
Mandatory single value for Fixed, optional multi-value for Dynamic scheduling type
|
timeOfDay |
Mandatory single value for Fixed, optional multi-value for Dynamic scheduling type
|
shadowLimit |
Optional, single value (defaults to 0.0)
|
shadowCalcConfiguration |
Optional, single value (defaults to the first array configuration in the Program Block)
|
initTeleAz |
Optional, single value (defaults to 225)
|
initTeleEl |
Optional, single value (defaults to 35)
|
avoidSunrise? |
Optional, single value (defaults to N), not case-sensitive; leave blank for Fixed
|
avoidSunset? |
Optional, single value (defaults to N), not case-sensitive; leave blank for Fixed
|
windApi |
Mandatory for Dynamic scheduling type, single or dual value; leave blank for Fixed
|
commentsToOperator |
Optional, single value
|
To ingest a text file with a scheduling block, navigate to the OPT and activate (click) the program block or a scheduling block in the program block in which the new scheduling block should be placed. Select from the menu FILE → IMPORT SCHEDULING BLOCK. After providing a file name to import, a new scheduling block with the default name [New Scheduling Block] will be created if no predefined name is given in the first field of the SCHED-BLOCK line. Note that if FILE → IMPORT SCHEDULING BLOCK is grayed out, the wrong item in the project tree is selected (e.g., a scan).
Scheduling Block Preamble Examples
Version line and fixed-date observing specified in VLA LST day and time:
VERSION; 4;
SCHED-BLOCK; Orion Neb; Fixed; ; 72987; 13:45:30; ; ; ; ; ; ; ; Coord w/ HST;
Dynamic observing, with repeat, multiple LST start ranges, shadow calculations and weather settings for X band, and avoid sunset and sunrise with a comment to run with 20 antennas or more.
SCHED-BLOCK;Orion;Dynamic;3;2012-08-11;09:30-13:00,18:00-00:30;0;;180;45;y;y;X;>=20 antennas;
Absolute minimum specifies mandatory wind and API for Dynamic blocks with the receiver letter code only (but then one would be wise to edit the scheduling block name, etc., directly in the OPT).
SCHED-BLOCK;;;;;;;;;;;;Ka;;
Absolute minimum for a Fixed scheduling block includes a fixed starting time (here in LST) at the VLA.
SCHED-BLOCK; ; Fixed ; ; 72859 ; 08:45 ;;;;;;;;;
Connect with NRAO