WEAVE Open-Time Phase 2 - Notes for PIs (semester

...

23B)

Catalogue template download

Log on to WASP with the username and password provided in an email you must have received from WASP. Go to "My survey" and click on "Download template".

Mandatory catalogue columns

These aremandatory columns. They must have a value set or otherwise they will be replaced by a default value:

...

Apart form the above, the catalogue table must also contain the columns:

TARGNAME
TARGID
TARGUSE

Any Only for semester 23B: any other columns are optional or not necessary to fill in for submitting the FITS target catalogue.

Column description and acceptable values

TARGSRVY

TheTARGSVY for Open Time proposals will beconstructed as follows:

...

Thus, for example,in the case ofTARGSRVY=WS2022B1-002 the corresponding catalogue filename would be:WS2022B1-002.fits.

TARGPROG

TARGPROG is an optional column, to be filled out at the discretion of the catalogue creator. If this column includes the entry “|BW”, however, then the target is assumed to be filler (bad-weather) target. In this case, any XML generated with this target will be given an overall priority of 0.1 rather than the default priority of 1.0, significantly reducing the probability of this OB being observed unless no other OB is available in the conditions specified by the OBSTEMP of the observation.

TARGNAME, TARGID

TARGNAME is mandatory for IFU observations. This parameter is used to group IFU observations of the same target, in cases where stacks arerequired. This helpsCPS identify cases where the same astrophysical target is observed but the OBs executed were not related.

...

• OB1: TARGNAME = “M33” TARGID = “M33 bulge”
• OB2: TARGNAME = “M33” TARGID = “M33 disc NE”
• OB3: TARGNAME = “M33” TARGID = “M33 disc NW”
• etc

TARGPRIO

TARGPRIO is used to provide a weight to the target for priority of observation selection for MOS targets. 1.0 is the lowest priority, 10.0 is highest priority. This corresponds to a positive weighting in Configure. The data type for TARGPRIO is float. The precision of TARGPRIO is to 1 decimal place (X.x).

For LIFU fibres within a single exposure, all have equal (and redundant) priority so this column should be filled with value 10.0.

TARGUSE

There are five uses for TARGUSE: T=target, S=sky, G=guide, C=calibration standard, R=random.

PROGTEMP

The PROGTEMP code is an integral part of describing a WEAVE target. This parameter encodes the requested instrument configuration, OB length, exposure time, spectral binning, cloning requirements and probabilistic connection between these clones. We refer registered WEAVE users to the PROGTEMP form in WASP: http://wasp.ast.cam.ac.uk/progtemp

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. We note that these constraints represent “worst-case” observing parameters – targets will be observed under these conditions or better. Observers should note that the probability of observing targets with highly restrictive OBSTEMP codes may be quite low. We  refer registered users to the OBSTEMP form in WASP: http://wasp.ast.cam.ac.uk/obstemp

GAIA specific columns

All input targets must be on the Gaia Reference Frame. WEAVE currently accepts either Gaia DR2 or DR3 data with reference epoch as 2015.5 or 2016.0 respectively . Thus in the catalogue binary table, GAIA_DR= ‘2’ or ‘3’ (do not include ‘DR’ in the string) and GAIA_EPOCH= 2015.5 or 2016.0 respectively. These two columns must be filled regardless of whether or not the object has been detected by Gaia. We strongly urge observers to use the DR3 reference epoch for WEAVE targets.

...

The Gaia magnitudes are currently provided on the Vega system. Please report them inthe GAIA_MAG columns as Vega. All other photometry sources must be reported on the  AB system.

IFU_PA_REQUEST, IFU_DITHER

IFU_PA allows the catalogue provider to specify a rotation angle of the LIFU if required. The default value is zero. Rotation is generally used in cases where the default PA results in no viable guide stars falling within the autoguider FOV or when the rotation during an exposure is likely to exceed the angular limits of the rotator. Any dithering requested for the field is applied to the rotated LIFU frame. During the IFU observation preparation workflow, an analysis is performed on putative LIFU pointings to determine if a rotation is required and provides the optimal value IFU_PA should take. Fibres within the same LIFU pointing must have the same IFU_PA.

...

The LIFU preset patterns will be properly rotated according to the position angle of the observation.

HA_RANGE

The Hour angle range for the observations. Set this parameter to 2.0.

TAC_ID

For WEAVE Open time surveys, the reference of the submitted proposal. Example: SW2023b02.

Summary table

Further information on columns

A detailed description of every table column can be found on the WASP document "WEAVE SPA  to SWG and QAG Interface COntrol Document (WEAVE-ICD-030)",  pages 17-51 (local copy). And also a full summary can be found on header 1 of the FITS Catalogue Template:

Aladin footprints

Examples

It follows some catalogues in CSV format:

...

WS2023A1-002,supernova,WS2023A1-002.fits,sn2017ein_north,sn2017ein,10.0,T,GALAXY,41331,JAFDC,,3,178.221875,44.123919,2016.0,0.0,nan,0.0,nan,0.0,nan,1474334355452,,106.7010178,3,2.8,

Further assistance

We can provide a pre-validation of a target catalogue previous to the upload to WASP, please email:   

...