next up previous contents index
Next: Validation During Submission Up: Project Validation Previous: Basic Validation   Contents   Index

The Validation Tool

A higher level of validation is offered by the Validator Tool. Themain purpose of this validation is to check that the input provided bythe user is complete and consistent. Also, the validator ensures thecompliance of the project with a rather extensive set of rules thatusers need to follow so that observations can be scheduled. Anexample of the first category is the check that the central observingfrequency and the bandwidth falls within the receiver band. An exampleof the second category is the check that the duration of the SB doesnot exceed a certain limit imposed by the needs of flexiblescheduling.

The Validation Tool can run anytime during the preparation of theproject. Hence, when preparing a project the user can immediately makesure that the parameter space is filled correctly and that the projectcomplies with the observatory's procedures. Validation is performed byselecting File $\rightarrow$ Validate or by clicking on theValidate icon in the OT Tool Bar. An example of the information the OTprovides after running the Validator Tool is shown inFigure  11.2 .

Figure 11.2: Display of the SB in the Project Structure pane, and the content of the Problems tab in the Feedback pane after validating an (invalid) project. Note that the invalid SB components are marked in the project tree.
\resizebox{10cm}{!}{\includegraphics{images/ProjectValidation.eps}}

Errors resulting from wrong or problematic parameter input should befixed as they may affect proper execution and will prevent yourproject from being submitted to the ALMA Archive. The errors arerecorded in a log that can be displayed via the Log tab in theFeedback pane of the OT. The log file runs in append mode and henceall errors and warnings will be added at the end of the listing. Eachof the messages in the log file is provided with an indication of itsseverity. When clicking on the $>>$ link preceding the message, thetext is expanded providing detailed information and advice how tocorrect. Warning messages are intended to call your attention torather unusual setups to confirm that they are really wanted.

The Problems tab in the Feedback pane provides a listing of the existing problems with the current input parameters, where they occur and suggestions to how these problems can be resolved. The Problems tab will display errors (red) as well as warnings (yellow). When errors or warnings occur the corresponding element(s) in the project tree get marked visually as follows:

When double clicking on an entry in the Problems listing, the OT willautomatically display the relevant form of the observing project inthe Editors pane. Hence, searching for the problem in your observingproject and correcting it is relatively simple. After reportedproblems have been corrected and after re-executing the validation,the problem list will get shorter. To make sure that your project(Phase 1 proposal or Phase 2 program) will pass validation, theProblems tab should be empty or contain warnings only. Note that thewidth of the columns can be adjusted by positioning the cursor at theboundaries of description cells at the top of the columns.

Note that in the current version of the OT, the Log tab contains all output information the OT produces. The future goal is to produce a separate validation report as a saveable/printable file. In addition to validation information on technical errors, future validation will also show error and warning messages related to scheduling policies.


next up previous contents index
Next: Validation During Submission Up: Project Validation Previous: Basic Validation   Contents   Index
The ALMA OT Team, 2011 May 20