WEAVE IFU Workflow

This is the lookup table used to translate an OBSTEMP code into attribute values populated into the element

This is the lookup table used to translate a PROGTEMP code into attribute values populated into the spectrograph and exposure elements

Stage 4 input files - this contains the 4 IFU XMLs at the point they are due to be submitted to Configure.

The underlying blank XML template.
All OBs are dervied from this master XML file, with specific elements updated throughout the workflow.

This code identifies which guide star(s) and WD calibration stars can be used for a given field, and inserts their XML data representations into the "proto-field" XMLs

Notes to accompany this workflow

Positions of viable guidestars within the proposed FOV of the protofield.

HEALPix'd decomposition of the Guidestar catalogue. This is based on Gaia DR2.

Definitions
documentation

Described in ICD-030

Example input IFU driver catalogue.
This contains the information required to produce WEAVE IFU observing blocks.
We provide 4 cases here, and these will evolve throughout the workflow:

1. LIFU with fixed dither pattern
2. LIFU with custom dither pattern
3. mIFU with 3-dither pattern
4. mIFU with 5-dither pattern

(3) and (4) are observations of the same targets.

This code takes the output of configure and converts each target (and associated metadata from the XML) into a FITS catalogue row. This includes writing the IFU position angles, spaxel IDs etc.

These are the individual input catalogues from the survey teams. They have been verified by the WASP and have CNAMES added to them.

Wait until OB
trimester submission

This code identifies the entries in the input driver and splits them into fields. It also converts the FITS file into XML.

This is the output from configure. In general, configure is non-determinative:
the files here might not represent end-user attempts to run configure, but should serve as illustrative of the process.

Fibre info
(TARGCLASS)
(TARGUSE)

XML<- FITS
populator
code

This is a FITS file containing all fibres for all IFU observations.

SWG workflow
for MOS XML
configure

If LIFU has an "apply_dither" = 3,5 then
the GuideStar module must ensure that the
*same* guidestar is visible within the fixed
dither pattern that Dave Terrett uses, or within
a displacement from origin.

Stage 5 input files - this contains the 4 IFU XMLs at the point they are due to be submitted to Configure.

If we decide to ever allow mixed-survey fields for mIFU (eg. filler-mode?),
then the surveys will need to split at this point for FITS - ie,
the survey-specfic FITS templates must be used, mapping XML target TARGSRVY to the relevant catalogue template.

From this point onwards, this workflow implies work done on just one of these surveys. In reality, both must be processed.

Survey
FITS
template

This is the input FITS template for a specific survey.
For PI-surveys, these templates can be generated at the WASP once end-users
receive their access credentials.