The purpose of the of the WEAVE Open Time (OT) programme is the preparation of a FITS catalogue containing fibre positions on sky, and observing blocks (OB) written in XML describing the necessary observations. For more information, read the WEAVE OT phase 2 page. The FITS catalogue and the XML OBs are uploaded and validated on the WEAVE Automated Submission Platform (WASP), maintained by CASU in Cambrige (IoA). At the beginning of every trimester, the uploaded, validated and selected OBs are ingested into the observing queue at the WHT. Below you will find a short phase-2 guide. We also provide a more extensive phase-2 guide.
WEAVE Open Time submissions follow this calendar. Check the WEAVE OT time allocations for the current semester, and in particular the allocated time and the trimesters your programme will be on the observing queue.
WASP automatically emails the principal investigators (PIs) of the active programmes with submission deadlines, validation acknowledgements and any other important information concerning the preparation of phase 2 every time a new OB trimester submission window opens for that programme (see the programme lifecycle lenght, given as a trimester range, in the allocations page).
At the beginning of phase 2, the PI will receive an email with the credentials for logging on WASP, along with some other instructions. Subject line is:
Subject: [WEAVE] Account created for WEAVE observation preparation
After that, the PI will receive an email about the building of a catalogue template on WASP. For LIFU observations, you can skip this step (a standard catalogue template is automatically generated on WASP for your programme when the template catalogue preparation deadline is passed).
Next it is the making of a FITS catalogue and the respective XML OBs. This process is simple: we expect that the PI emails a CSV catalog containing some basic information to:
including the credentials emailed to the PI from WASP, so ING can proceed with the preparation, upload and validation of the FITS catalogue and the XML OBs on behalf of the PI. Note that the maximun number of OBs accepted per trimester submission window is 100 per programme.
We strongly recommend that all the OBs are submitted in the first trimester available OB submission window of the observing period. In certain cases, however, the PIs may prefer submitting some of the OBs in the second trimester window, or in any subsequent windows, in the case of Band A proposals.
Below we provide an example of a CSV catalogue. It describes a simple OB which consists of 3 exposures of 1020s each, following a 3-point dithering pattern in LIFU low-resolution mode and arbitrary position angle:
CSV catalog:
TARGID,TARGNAME,GAIA_RA,GAIA_DEC,PROGTEMP,OBSTEMP,IFU_DITHER |
TARGID, TARGNAME: these are identifiers of your observations. TARGNAME is used to stack exposures, read more on TARGID, TARGNAME. Please do not use dashes in TARGID or TARGNAME.
GAIA_RA,GAIA_DEC: RA and DEC of your target. Please note that certain restrictions apply.
PROGTEMP, OBSTEMP: use the OBSTEMP and the PROGTEMP builders. For custom dithering and/or exposure times, please contact:
IFU_DITHER: it is set to 0 if not specified (no dithering). Standard dithering patterns for 3, 4, 5 and 6 points are available for selection (read more information on IFU_DITHER).
POSITION ANGLE: the position angle (PA, as measured from North to East) is automatically set to 180º, for declinations North to 28.7º, and to 0º, for declinations South to 28.7º. Note that these PAs could be slightly different to allow for finding a suitable acquisition and guiding star. If you request a specific PA, please read the information on requested PA. Please note that not all values of PA are possible given the rotator limits, and similarly to the above, it could also change automatically for finding a suitable acquisition and guiding star.
CALIBRATIONS:
Lamp flats and arcs are automatically added to every OB. Regarding other calibrations:
ING takes biases every night and twilight sky flats regularly. If you need these sets of calibrations when working with your data, please contact ING.
A flux calibration is provided in L1 products. However, if the PI plans to flux calibrate the data, then we expect the submission of OBs for observing any flux standards. Note that we can’t repeat OBs that have been observed previously so provide enough OBs (for instance, if you have 6 targets, then we expect 6 OBs for flux standards submitted).
Please contact for more information on the above extra calibrations:
Just for your information, and following the example above, we provide here the FITS catalogue generated by ING using the IFU workflow software package and validated on WASP:
Example of a validated FITS catalog on WASP: WS2022A2-002.fits
The XML OB file contains the instructions on how to execute the observations: instrument setup, telescope pointing, guiding star, dithering, exposure times, observing constraints and calibrations (one lamp flat and two arcs, before and after the science exposures). The following is an example of the XML code of an OB with comments for users, before uploading to WASP:
Example of the XML code of an OB: WC_2023A1-lifu_01-tgcs.xml.
And below it is the XML OB generated from the former example, and validated on WASP:
Example of a validated XML OB on WASP and ready for ingestion into the observing queue: 1713807920_1.xml
The XML OBs are ingested into the observing queue of the WHT after phase 2 is complted and at the beginning of the following trimester. Below it is the log entries of the execution of the example OB. Note that the target coordinates correspond to the center of the field of view, not the centre of the LIFU array.
The OBs will be attempted according to the priority band of the programmes and the observing conditions. Please contact the ING weave support email for any particular time constrains.
Every observed OB is automatically reduced and calibrated using the automatic pipelines at CASU (IoA, Cambridge). The data are made available in a few days after the observations on the WEAVE Operational Repository (OR) platform (same login credentials as on WASP). Once the reduction becomes stable, then the data will be transferred to the WEAVE Archive System (WAS) and the PI will be emailed about it.