...
WEAVE Open-Time Phase 2. Instructions for Applicants
Summary of actions
GREEN: Actions by the PI |
PURPLE: Actions by the PI if familiarised with the package "IFU Workflow", or by ING on behalf of the PI, if assistance is requested by the PI to weave_open_time_support@ing.iac.es |
Step | Action |
|---|---|
1 | Download of catalogue template from WASP (optional) |
2 | Fill out the catalogue template with targets following instructions on this page |
3 | Process the populated catalogue using the IFU workflow |
4 | Upload the processed catalogue to WASP |
5 | Download the validated catalogue from WASP |
6 | Generate the XML files (OBs) using the IFU workflow |
7 | Upload OBs to WASP |
8 | Select OBs on WASP for observing |
The instructions below are mainly aimed at PIs who will request assistance to:
weave_open_time_support@ing.iac.es |
Communication with the PI
...
General assistance can be provided at the following email:
weave_open_time_support@ing.iac.es |
Purpose of the phase 2
The purpose of the phase 2 is the upload of a FITS catalog containing fiber positions on sky, and observing blocks (OB) written in XML describing the necessary observations to the 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.
...
An XML OB contains the instructions 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: WC_2023A1-lifu_01-tgcs.xml.
Every observed OB is reduced and calibrated using automatic pipelines at CASU (IoA, Cambridge). Data is flux calibrated using a standard sens functions. However, applicant scan submit their own OBs for observing flux standards along with the science OBs. Every trimester we accept a maximum of 100 OBs per programme.
Below we provide an example of real observations made from a simple OB which consists of 3 exposures 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 |
Validated FITS catalog on WASP: WS2022A2-002.fits
Validated XML OB on WASP and ready for ingestion into the observing queue: 1713807920_1.xml
Log entry as a result fo the execution of the above OB. Note that the target coordinates correspond to the center of the field of view, not the centre of the LIFU array.
...
WASP sets limits to allowed target RA and Dec, and it will not validate your OB if your target coordinates lie outside the limits for that trimester. See below the allowed RAs for each trimester.
Trimester A1 |
2h (30º) → 20h (300º) Expanded range: |
Trimester A2 |
9h (135º) → 2h (30º) Expanded range: |
Trimester B1 |
|---|
15h (225º) → 9h (135º) Expanded RA range: |
Trimester B2 |
20h (300º) → 16h (240º) Expanded RA range: |
Total requested time
The total length (counted as science exposure time) of all the submitted OBs can't exceed the science time allocation of your proposal (see the time allocations).
...
3. Filling in a simplified CSV version of the catalogue template. Below it's an example of this simplified template and 4 catalogue rows that each describe an OB definition:
<filename: WS2023B2-001_target_list.csv> TARGID,TARGNAME,GAIA_RA,GAIA_DEC,PROGTEMP,OBSTEMP,IFU_DITHER |
Filling out the catalogue template with targets
...
TARGPROG (optional)
TARGID
TARGNAME
GAIA_ID (if available)
GAIA_DR (optional)
GAIA_RA
GAIA_DEC
GAIA_EPOCH (optional)
GAIA_PMRA (if available)
GAIA_PMDEC (if available)
GAIA_PARAL (if available)
PROGTEMP
OBSTEMP
IFU_DITHER
IFU_PA_REQUEST (if necessary)
TARGPROG
TARGPROG is an optional column, to be filled out at the discretion of the catalogue creator.
TARGID and TARGNAME
This parameter is used to group IFU observations of the same target, in cases where stacks are required. This helps the Core Processing System (CPS) responsible for obtaining the data, to identify cases where the same astrophysical target is observed but the OBs executed were not related (via for example the "chained" directive).
...
OB1: TARGNAME = “M33” TARGID = “M33 bulge”
OB2: TARGNAME = “M33” TARGID = “M33 disc NE”
OB3: TARGNAME = “M33” TARGID = “M33 disc NW”
PROGTEMP
The PROGTEMP code is an integral part of describing how the instrument is configured. This parameter encodes the requested instrument configuration, OB length, exposure time, spectral binning, cloning requirements and probabilistic connection between these clones. We refer registered WASP users to the PROGTEMP form: http://wasp.ast.cam.ac.uk/progtemp(there is also a copy at ING: https://a.ing.iac.es/weave/progtemp.php ).
...
Check first what instrument modes are available in the ING announcement of opportunity.
OB length
This PROGTEMP component specifies the overall OB length (inclusive of overheads). Please be aware that not all OB lengths are available.
Arm exposures
It defines how the time within the OB that you wish to observe the target is divided up, by specifying the number of exposures and exposure time within the stipulated OB length. The listed options of exposure time splits correspond to science open-shutter times (note that every exposure incur a 3-minute overhead).
IMPORTANT: It is not recommended unlocking the arms. Note that different exposure splits (unlocking the arms) in the red and the blue arms will have two consequences: firstly, no dithering will be possible, and secondly, OB length will increase as the observing system cannot execute different exposure splits simultaneously but one only exposure in both arms at a time. For example, requesting one exposure in red, and 12 in blue would cause a significant mismatch in overheads between the two arms. |
Binning in the spectral direction
...
Furthermore, if PIs want to chain these OBs together, such that the observation of one of these clones increases the chance that the remaining OBs in this group are observed, then a "+" will be added to the end of PROGTEMP. The "+" instructs the WEAVE scheduler to increase the (internal, programme-specific) weight of all OBs in this group. This provides a mechanism to ensure that once a series of observations are started, completion of the chain becomes a progressively higher priority above other OBs from this programme.
OBSTEMP
Whilst PROGTEMP deals with “how” a target is observed, OBSTEMP deals with “when” a target is observed – namely setting the observational constraints required to optimally extract scientific information from the observation.
...
An instrument-wide lower limit of 30 degrees ensures sky brightness gradients and scattered light effects are kept to a minimum. This limit applies to any observations set with “0 degrees (no constraint)”.
Sky brightness
The maximum V-band surface brightness of the sky (mag / sq. arcsec) required to observe the target.
The dark-of-moon sky brightness varies by a few tenths of a mag depending on ecliptic and galactic latitude and phase of the solar cycle. With the moon up, the sky can be up to ~4 mag brighter than dark-of-moon, depending on lunar phase, elevation and angular distance from the target. Science observations are carried out mainly during astronomical night, but those OBs tolerating moonlit skies can also use the latest bit of evening twilight, or the earliest bit of morning twilight – the only relevant criterion is sky surface brightness. No observations will be carried out when the sky brightness exceeds that at full moon.
GAIA specific columns
We strongly urge PIs to use the DR3 reference epoch for WEAVE targets.
...
Information from Gaia is expected to be provided exactly as it is retrieved from the Gaia archive, so parameter definitions, data formats and units remain the same. Please consult the Gaia webpages to further understand their data model.
IFU_PA_REQUEST
IFU_PA_REQUEST allows the catalogue provider to specify a rotation angle (position angle) of the LIFU, if this is required. Any dithering requested for the field is applied to the rotated LIFU frame. If a specific PA value is not requested, then the following defaults are applied: IFU_PA=0° (for declinations lower than 28.7°) and IFU_PA=180° (for declinations higher than 28.7°). Note that the requested IFU_PA could be changed by the IFU workflow software if a suitable guiding star cannot be found at the requested PA. Below it's a plot which shows how the PA is changed to find a suitable guiding star.
IMPORTANT: During the IFU observation preparation using the IFU workflow software, an analysis is performed on putative LIFU pointings to determine if a rotation is required and provides the optimal value IFU_PA should take. Rotation is generally used in cases where the default or requested PA results in no viable guide stars falling within the autoguider field of view, or when the rotation during an exposure is likely to exceed the angular limits of the rotator. This means that it's not always possible that the IFU workflow software can provide the IFU_PA_REQUEST value in the catalogue. The table below shows the allowed IFU_PA_REQUEST (=PA in the table) ranges PIs can safely apply for. Maximum value of PA is 360º. |
h_min=50.28 (X=1.3) | h_min=45.58 (X=1.4) | h_min=41.81 (X=1.5) | h_min=38.68 (X=1.6) | h_min=33.75 (X=1.8) | h_min=25.00 (X=2.4) | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Dec (°) | PA range (°) | PA range (°) | PA range (°) | PA range (°) | PA range (°) | PA range (°) | ||||||
-25 | 225<PA<135 | -135 → 0 → +135 | 245<PA<115 | -115 → 0 → +115 | ||||||||
-10 | 220<PA<140 | -140 → 0 → +140 | 235<PA<125 | -125 → 0 → +125 | 245<PA<115 | -115 → 0 → +115 | 245<PA<115 | -115 → 0 → +115 | 250<PA<110 | -110 → 0 → +110 | 260<PA<100 | -100 → 0 → +100 |
0 | 250<PA<110 | -110 → 0 → +110 | 255<PA<105 | -105 → 0 → +105 | 255<PA<105 | -105 → 0 → +105 | 260<PA<100 | -100 → 0 → +100 | 260<PA<100 | -100 → 0 → +100 | 270<PA<90 | -90 → 0 → +90 |
+15 | 270<PA<90 | -90 → 0 → +90 | 270<PA<90 | -90 → 0 → +90 | 270<PA<90 | -90 → 0 → +90 | 270<PA<90 | -90 → 0 → +90 | 275<PA<85 | -85 → 0 → +85 | 275<PA<85 | -85 → 0 → +85 |
+28.70 | 295<PA<65 | -65 → 0 → +65 | 295<PA<65 | -65 → 0 → +65 | 295<PA<65 | -65 → 0 → +65 | 295<PA<65 | -65 → 0 → +65 | 295<PA<65 | -65 → 0 → +65 | 295<PA<65 | -65 → 0 → +65 |
+30 | 130<PA<230 | -130→ 180 → +130 | 130<PA<230 | -130 → 180 → +130 | 130<PA<230 | -130 → 180 → +130 | 130<PA<230 | -130 → 180 → +130 | 135<PA<225 | -135 → 180 → +135 | 135<PA<225 | -135 → 180 → +135 |
+40 | 115<PA<245 | -115 → 180 → +115 | 120<PA<240 | -120 → 180 → +120 | 120<PA<240 | -125 → 180 → +125 | 120<PA<240 | -125 → 180 → +125 | 130<PA<230 | -130 → 180 → +130 | 135<PA<225 | -135 → 180 → +135 |
+50 | 105<PA<255 | -105 → 180 → +105 | 100<PA<260 | -100 → 180 → +100 | 115<PA<245 | -115 → 180 → +115 | 120<PA<240 | -120 → 180 → +120 | 120<PA<240 | -125 → 180 → +125 | 135<PA<225 | -135 → 180 → +135 |
+60 | 80<PA<280 | -80 → 180 → +80 | 95<PA<265 | -95 → 180 → +95 | 105<PA<255 | -105 → 180 → +105 | 110<PA<250 | -110 → 180 → +110 | 120<PA<240 | -120 → 180 → +120 | 130<PA<230 | -130 → 180 → +130 |
+70 | 65<PA<295 | -65 → 180 → +65 | 85<PA<275 | -85 → 180 → +85 | 95<PA<265 | -95 → 180 → +95 | 110<PA<250 | -110 → 180 → +110 | 120<PA<240 | -125 → 180 → +125 | ||
+80 | 35<PA<325 | -35 → 180 → +35 | 90<PA<270 | -90 → 180 → +90 | 140<PA<220 | -140 → 180 → +140 | ||||||
IFU_DITHER
IFU_DITHER allows the PI to specify the dithering strategy for their observations, but may alternatively request not to dither their observations, with the understanding that this will not provide full spatial coverage of their requested field. PIs may request the preset -3, 3, 4, 5 and 6-dither patterns. The LIFU preset patterns will be properly rotated according to the position angle of the observation.
IMPORTANT: Exposure options for which fixed dither patterns are available in IFU modes are 3x, 4x, 5x, 6x. |
...
For custom dither patterns, constraints on the dither step size are imposed by the WASP to ensure that the guide star remains within the guiding camera field of view. From the perspective of IFU users, careful consideration of the dithering options should be made. Below it's an example of custom dithering. Note that pointings are provided for each dither, rather than the dither pointings from an initial position. The three pointings provided in the example below would be executed as part of one only OB.
# A custom 3-dither pattern LIFU pointing |
Summary of table columns and examples
Column | Description | Format | Length | Value(s) | Units | Example |
|---|---|---|---|---|---|---|
TARGPRO | Optional description of programme | ASCII | ≤40 | WS2023B2-010_001 | ||
TARGNAME | The target name | ASCII | ≤30 | M33 | ||
TARGID | The identifier of the target assigned for this programme | ASCII | ≤30 | M33_NE | ||
PROGTEMP | Observing Programme Template | ASCII | 8 (fixed) | 41331.3+ | ||
OBSTEMP | Observing Constraints Template | ASCII | 5 (fixed) | FAACA | ||
GAIA_ID | GAIA Source Identifier | ASCII | 19 | 1463976195968535680 | ||
GAIA_DR | GAIA Data Release version | I1 | 2, 3 | 3 | ||
GAIA_RA | Gaia RA of target | F11.7 | 0...360 | degrees | 178.221875 | |
GAIA_DEC | Gaia Dec of target | F11.7 | -90...90 | degrees | 44.123919 | |
GAIA_EPOCH | Gaia Epoch of target | F6.1 | 2015.5 (DR2), 2016.0 (DR3) | Julian year | 2016.0 | |
GAIA_PMRA | Gaia Proper Motion of target in RA | F11.3 | mas/yr | 12.1 | ||
GAIA_PMDEC | Gaia Proper Motion of target in Dec | F11.3 | mas/yr | 0.01 | ||
GAIA_PARAL | Gaia Parallax of target | F10.3 | mas | 0.002 | ||
IFU_PA_REQUEST | Position Angle of IFU bundle | F11.7 | -180...180 | degrees | 106.701 | |
IFU_DITHER | IFU dither pattern code | I2 | -3, -1, 0, 3, 4, 5, 6 | 3 |
Aladin overlays of the LIFU footprints
...
Download the vot files linked below.
Open Aladin and enter an object name in the command field, ex. 'M51'.
File → Load instrument FoV.
In the emerging window, click on 'File' and browse for a suitable vot file.
Click to submit. The vot file will load as a layer with a given colour.
Description and VOT file | LIFU FoV and sky bundles | LIFU FoV |
|---|---|---|
Photo of a real view of the LIFU unit using fibre back illumination. |
 |
 |
No dithering (as seen in Aladin) Download VOT file: |
 | ||
3-pointing dithering (as seen in Aladin) Download VOT file: |
 |
6-pointing dithering (as seen in Aladin) Download VOT file: |
 |
 |
Catalogue upload to WASP
The edited catalogue must go through the IFU workflow, a set of scripts which will make a version of the FITS catalogue suitable for uploading to WASP (http://wasp.ast.cam.ac.uk/catsubmit/upload) for validation. First log on using the provided credentials (the ones emailed from WASP), note that you need to register your IP at http://wasp.ast.cam.ac.uk/ipsubmit/upload first. See below the tab used for uploading the catalogue.
...
At ING, we can provide assistance in guiding you through the different stages of the IFU workflow package, or we can even process your catalogue provided in any of the formats described above, on your behalf. In this latter case, simply email your catalogue to the contact below:
weave_open_time_support@ing.iac.es |
LIFU mode: OB preparation
...
At ING, we can provide assistance in generating the OBs from the CNAMEd catalogue, please contact:
weave_open_time_support@ing.iac.es |
OB upload to WASP
The processed OBs can be then uploaded, as a tar file if many, to http://wasp.ast.cam.ac.uk/xmlsubmit/upload (see below). Remember to log on first.
...
In the figure below we show an example of 6 OBs uploaded whose validation failed (the generated report will tell you why). The "Submission Management" button gives access you to all the catalogue and OB uploads made by the user. Note that if you have requested OB repetitions (for instance, PROGTEMP=41331.5, or 5 OB copies), then only one OB is validated on WASP (not 5 OBs following the example). The OB copies are actually made at the time they are ingested into the observing queue according to the information encoded in PROGTEMP.
IMPORTANT: Don't forget to select the right OBs in the submission maganement! Otherwise, they won't be queued. |
...
Observations and follow up
...