Since the end of 2023, INAF has been responsible for providing a daily execution sequence, which is carried out by ESO colleagues [1], thanks to the use of the VST scheduler
Additional Guidelines to help complete your targets:
Relax constraints as much as possible to improve scheduling chances (e.g., an OB with airmass = 1.8 is more likely to be executed than one with airmass = 1.2)
Use simple naming conventions:
You have to fill three fields:
- Name (field close to the OB ID number),
- Observing description name (in OBs. Description tab)
- Target name (in Target tab).
Never leave these fields empty. It helps the scheduling (see below: Prioritization).
Example created using the P2 Demo
The Name and Observing Description Name fields should be identical and may include information on the band, rotation, etc., while the Target Name field should contain only the index and actual name of the target (see “Prioritization” below).
Moving targets: the OB name must begin with the prefix MOV_
Prioritization: Users cannot manually set target priority, but targets are prioritized as follows:
Observed fraction: preference is given to targets with the highest observed fraction (based on target name) to maximize completeness.
Alphabetical order: if observed fractions are equal, and targets are visible at the same time, then they are sorted alphabetically.
NOTE: in general, OBs for the same targets (same target name) that require a lower FLI will be prioritized over those with higher FLI, in order to maximize the use of dark time.
For Name and observing description name, you may use the following naming convention :
<INDEX>_<TARGETNAME>_<BAND>_<ROTATION>_<EPOCH>_<NUMBER> ..
while the corresponding target name is a shorther version, such as:
<INDEX>_<TARGETNAME>
(Not all fields are required, but the INDEX is essential to increase the chances of correct prioritization)
Examples to improve the chances of correct prioritization:
Maximize the changes to prioritize a target over others:
Name/observing description name:
00_NGCGalaxy_gband, 01_ESOGalaxy_gband.
MOV_00_HRstar, MOV_01_HIPstar.
target name:
set 00_NGCGalaxy as target name for 00_NGCGalaxy_gband
set 01_ESOGalaxy as target name for 01_ESOGalaxy_gband
set 00_HRstar as target name for MOV_00_HRstar
set 01_HIPstar as target name for MOV_01_HIPstar
Result:
00_NGCGalaxy_gband will be prioritized over 01_ESOGalaxy_gband.
MOV_00_HRstar will be prioritized over MOV_01_HIPstar.
Maximize the changes to prioritize a band:
if you want to complete the same band for multiple targets rather than collect data for different bands of the same targets, you might name as follows:
Name/observing description name:
00_GalaxyA_iband, 00_GalaxyB_iband, 00_GalaxyC_iband
01_GalaxyA_gband, 01_GalaxyB_gband, 01_GalaxyC_gband.
target name:
set 00_Galaxy_i as target name for 00_GalaxyA_iband, 00_GalaxyB_iband, and 00_GalaxyC_iband
set 01_Galaxy_g as target name for 01_GalaxyA_gband, 01_GalaxyB_gband, and 01_GalaxyC_gband
Result:
All i-band observations (index 00) of different targets will be prioritized before g-band observations (index 01), even if the i-band could be observed with a higher FLI.
Time intervals: If your run requires a cadence in time, include the time intervals in the relevant tab into the P2.
Create one OB for each time interval (e.g., if a target should be observed twice in two different time windows, create two OBs, each with its own time interval).
Note:
[1] We remind users that the execution of an OB included in the execution sequence is not guaranteed. It depends on several factors, such as weather conditions, technical issues, operational delays, or laser collision avoidance events involving the laser guide star facility on UT4.