next up previous contents index
Next: Resources Up: Targets Previous: Add a Calibration Target   Contents   Index


Observing Groups

The user has the ability to create an Observing Group for targets where they can be organised into an ordered list. Under the SchedBlock node in the Phase 2 programme tree, the user has the option to Add Observing Groups from the Edit menu or by right clicking on the node and choosing the option from the context menu. A new Observing Group folder will appear in the project tree. Clicking on the folder displays the Observing Group form in the Editors pane.

Figure 8.6: The Observing Group panel in the Editors pane for handing an Observing Group. On the left are all available Targets. The table on the right lists the Targets in the Observing Group.
\resizebox{12cm}{!}{\includegraphics{images/ObservingGroups.eps}}

At the top of the form the user can enter a name for the Observing Group. The default name for newly created Observing Group folder is Observing Group N where N is a sequential creation number for that group. The user can also change the name of the Observing Group by right clicking on the folder in the project tree and selecting the Rename menu option from the context menu.

The Observing Group panel has two tables. The table on the left includes all of the Targets that have been created by the user as part of the parent SB. The table on the right shows the Targets that make up the Observing Group. The user can select Targets from the All Available Targets table and click on the right arrow button to add it to the Observing Group. Targets in the Observing Group Targets table can be deleted or moved up/down using the button below the table.

The ordering of the Observing Groups in SB and their names can be edited here. The user can click on the name columns and edit the observing groups name. Below the table are buttons for manipulating selected observing group rows in the table. These buttons carry out actions for deleting and moving the rows.

Note that Observing Groups cannot be dragged and dropped in the project tree as this caused unexpeted behaviour that could be interpreted as a bug.


next up previous contents index
Next: Resources Up: Targets Previous: Add a Calibration Target   Contents   Index
The ALMA OT Team, 2011 May 20