Facilities > VLA > Documentation > Manuals > OPT > Using the Observation Preparation Tool (OPT) > Checking and Submitting Your Scheduling Block

Checking and Submitting Your Scheduling Block

by Gustaaf Van Moorsel last modified Jul 18, 2018 by Lorant Sjouwerman

This tab-page summarizes your SB in three tables. The first table displays all unique resources used in this SB, the second shows all unique source-with-resource combinations, and the third table lists the sequence of scans with their details. Obviously, you should check these tables thoroughly for each tiny detail, e.g., whether you applied the reference pointing solutions ("Apply Ref. Ptg.") to the scans where this correction is useful. The table with the scan sequence will show loops (if any) initially in a collapsed form. It is strongly advised to click the expand-icon (xpnd) to show the scan details of the scans in the loop. You can expand all loops in the scan table at the same time using the expand button in the top left hand side corner of the table, and similarly collapse all loops in one go. After verification that all these scans are as intended, the loop may be collapsed again.

Figure 4.7: Web browser screen shot of the Validation and Submission page.

Printing the SB information

Note the "Use your browser's Print feature to print this report" in the upper left corner st the top of the Reports page. It tells use your browser's printing tool, e.g., CTRL-P, File-Pint, for a printout. Tou can also export the information as CSV-tables under the header for "Computed Summaries". If you are not printing to a PDF-file, you probably want to set the printing properties such that it shrinks the page to fit. You also would want to enable printing of background colors if you are interested to see the errors highlighted; offending values are also struck out to identify errors on your printed copy. Both the Reports page and the remaining error and warning messages from the interface feedback strip (if any) are printed. Loops in the scan listing are not automatically collapsed nor expanded; it will print as selected in the scan listing at the time of printing. To print the page with all loops expanded, use the expand-all icon in the header of the Scan List table.


Validation and submission

When you have created one or more SBs for this PB, go back to the PB page (click on the PB name in the tree of the SBs). In the table at the bottom you will find a summary of your SBs in this PB, with some accounting of the time each SB has consumed. You should check this before you submit your schedule, because your SBs will not be accepted for scheduling if they are using up more time than allocated for your project, or more than allocated for your fixed-date SB.

If the validation points out that the sunrise/sunset check boxes are ticked, see above how to address this before submitting.

Once everything is in order, when you are within your time limits and no errors remain, you can submit your SB schedule using the third tab on the SB page (click on the SB name and select the "Validation and Submission" tab page). Subsequently click "Validate" and, if the project passes validation, "Submit". It will send the information to the relevant places within VLA operations and show you a message to that effect. All you need to do now is keep your fingers crossed... Note that you do not send a (observe) file to an NRAO email address as you may have been used to, only press a button. The SB will turn read-only: the SB name will appear in slanted red font.

When you realize you have an error in your submitted SB, simply select the SB in the tree, and navigate to the "Validation and Submission" tab page. You can cancel your SB submission, which allows you to edit the SB and submit it with your corrections.

Initially, the status of your submitted SB will appear as "SUBMITTED" on the PB information page (accessible by clicking the name of the PB in the left hand side bar). Your submission will actually put your schedule in a queue that currently is on hold. After we have received your schedule we will check it for technical errors (i.e., for resource settings, elevation requirements, etc.) and release it to the observing queue when it is found to be valid. At this time, its status will change to "SCHEDULABLE", meaning that it is ready for observing.