Workflow
• Set the observing date in the Date field and press Set. This will populate the graph with the ephemerides for that night. By default, the page is pre-loaded for today's observing night (after noon) or for last night (before noon).
• Fill in the list of targets according to the rules given below (alternatively, the list of targets may be pre-filled by the OB generator if the page is accessed from there) and press Plot targets.
• Choose the scheduling and rendering options from the checkbox list and press Schedule observations.
The software will then attempt to schedule as many targets as possible, each at the best possible airmass, while taking into account all specified and implicit constraints.
• Once the night is scheduled, the visibility plot will be refreshed and the UTC range of observation for each target will be marked by a thick, coloured line.
• After scheduling the night, you can always click on the number corresponding to an object to see the details of the observation (UTC range, total observing time, etc.) and the finding chart (loaded automatically from Aladin).
It is also possible to Mark the object as observed, in which case it will be redrawn in green.
• After scheduling the night for the first time, the Schedule observations button will change into Update schedule. From that point onwards, any change to the input list of targets will update the schedule (e.g., targets marked as Observed remain observed and are no longer moved around or rescheduled) as opposed to completely resetting it.
If a complete reset of the schedule is desired, press first the Plot targets button, and then Schedule observations; be warned that this will result in all previous changes being lost (e.g., observed targets will be marked as unobserved).
• After the software has suggested an observing order, it is possible to reorder the targets manually, by dragging and dropping them on the right-hand side of the plot.
The program may then reschedule some or all of the other targets so that all of them continue to fit their respective constraints, in their new order. In rare cases, a manual reordering may results in one or few targets becoming de-scheduled, which normally means that with the new order it is not possible for all the targets to be observed according to their respective (UTC, airmass, altitude, etc.) constraints.
Input syntax
• [NAME] [RA]/[pmRA] [DEC]/[pmDEC] [EPOCH] [OBSTIME] [PROJECT] [CONSTRAINTS] [TYPE] [OBINFO] [SKYPA],
where:
• [NAME] is the object name, without spaces;
• [RA] is the right ascension, given either with spaces (23 34 34.7) or with colons (23:34:34.7); optionally, one can append to it the proper motion given in arcsec/year [pmRA], which is otherwise assumed to be 0.0; if provided, [pmRA] must already include the cosine of declination;
• [DEC] is the declination, given in the same format as the RA; optionally, one can append to it a proper motion given in arcsec/year [pmDEC], which is otherwise assumed to be 0.0;
• [EPOCH] is the epoch of the coordinates; the only valid options are 2000 (corresponding to J2000) and 1950 (corresponding to B1950);
• [OBSTIME] is the total observing time (including overheads) in seconds;
Alternatively, [OBSTIME] can be * if [CONSTRAINTS] is a UTC/LST range, in which case the object will be scheduled with absolute priority for the entire time interval (useful for, e.g., time-critical monitoring);
• [PROJECT] is the project number (used for accounting purposes, but also for priority-based scheduling);
• [CONSTRAINTS] are the observing constraints, either airmass (a float, e.g., 2.0), a UTC range (UTC[20:00-23:30]) or an LST range (LST[2-4:30]); integers, floats, HH:MM syntax, or a mix of them are all allowed for the range components (e.g., LST[2:00-4.5];
• [TYPE] is the type of observation, and can be one of the following: Monitor, ToO, SoftToO, Payback, Fast-Track, Service, CATService, Visitor, and Staff.
Iff [TYPE] is set to Staff, it is allowed to add a slash and 2-3 initials to identify for which member of the staff the observations are taken (e.g., Staff/JHT, Staff/TP, etc.).
• [OBINFO] is information passed automatically when the page is loaded from an OB queue; it allows Visplot to generate backlinks to the OB queue, as well as show additional information about each target. At the moment the system is only integrated with the NOT OB queue. Alternatively, one can pass an instrument name in this field (e.g., GCMS). In all other cases, the value should be default.
• [SKYPA] is the Sky Position Angle in degrees, with 0=North up, 90=East up, etc. Used for the orientation of the finding chart only.
Note: The fields [EPOCH], [OBSTIME], [PROJECT], [CONSTRAINTS], [TYPE], [OBINFO] and [SKYPA] are optional, and will be filled with default values (i.e., 2000 600 54-199 2.0 Staff default 0) if missing.
Examples of valid input formats:
•
EQPsc 23 34 34 -01 19 36
This will fill the extra fields with the default values.
•
EQPsc 23 34 34.70 -01 19 36.01 2000 2600 54-321 2.0 Monitor default
This is the most frequent way of filling the input field, and is also used by the OB generator.
•
EQPsc 23:34:34.70 -01:19:36.01 2000 2600 54-321 2.0 Monitor default
Sometimes, observers prefer to use colon-separated RA and Dec, which is fine.
•
HD84937 09 46 12.06/0.373 13 59 17.44/-0.774 1950 414 54-501 1.5 ToO
For this object the proper motion is appended to the RA and Dec values, and the coordinate epoch is given as B1950.
•
EQPsc 23 34 34.70 -01 19 36.01 2000 1800 54-321 UTC[22:00-24:00] Staff
In this case the program will schedule EQPsc for 30 min between UTC 22 and 24.
•
EQPsc 23:34:34.70 -01:19:36.01 2000 * 54-321 UTC[20:00-20:30] Staff default
In this case EQPsc will be scheduled for the entire half hour between UTC 20:00 and 20:30. Highest priority.
Note: It is possible to separate groups of targets by blank lines, which will be ignored by the software.
Note: It is also possible to comment out a target by adding a hashtag (
#) at the beginning of the line. In this case, the software will not plot or schedule that target. The line can always be uncommented later on.
Alternative (TCS catalogue) syntax
The software accepts the NOT TCS catalogue syntax as input format (Name RA DEC Epoch pmRA pmDec Mag; see the
Enter-Object entry on the
TCS commands page), but it will automatically convert it to the Visplot format described above, and the magnitude value will be lost (since at the moment it is not used by Visplot).
Because this compatibility is built into Visplot, a valid Visplot target list can be exported to a TCS source catalogue using the
TCS format button, and can then be loaded to the NOT system
here.
Alternative syntax for non-schedulable time
The software can avoid scheduling observations in a given interval (e.g., when the telescope is offline due to bad weather or technical problems, or for the visitor's half of a shared night, etc.).
The syntax to add an offline period is:
•
Offline UT[20:30-22:30]
•
Offline LST[23-3.5]
In this example, the system will not schedule any observations in the given UTC or LST range. One can define as many such intervals as desired.
SkyCam
The button
Show SkyCam will open a lightbox window showing SkyCam and the current UTC and LST (these refresh automatically).
If a valid list of targets is loaded (i.e., the
Plot button has been pressed), the targets will be shown on SkyCam, and their positions will be automatically refreshed every few seconds.
It is particularly advisable to use this feature when the sky is partially cloudy, as it will allow the observer to schedule observations through patches of clear sky.
Save/Load
The
Save feature can be used to download a compressed file of all the data currently loaded in Visplot, including the list of targets, the current schedule, and the user-defined settings.
This file can then be loaded again using the
Load feature (even on a different computer), which will restore the state of Visplot and allow the user to resume the work at a later time (e.g., make a preliminary schedule at home and load it at the telescope before the observing night starts).
Note: Since at the moment
Visplot is being updated at very high cadence, it may happen that old files will cease to be compatible with the program in the near future, although we are trying to avoid that situation as much as possible. Once Visplot will become stable and fully functional, the Visplot file format will (hopefully) remain unchanged.
