Page History

Tiny link: https://a.ing.iac.es/s/?21dfdf

...

LIFU mode: catalogue preparation

Target declination and right ascension

...

limits

The current target declination limit is -25º. Objects with a declination lower than that cannot be observed. 

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. The declination limit is -25º. 

...

3. Filling in a simplified CSV version of the catalogue template. Below it's an example of this simplified template and one target4 catalogue rows that each describe an OB definition:

<filename: WS2023B2-001_target_list.csv>

TARGID,TARGNAME,GAIA_RA,GAIA_DEC,PROGTEMP,OBSTEMP,IFU_DITHER
IC768_1,IC768,76.7836980,18.1489034,61331.3,DAFEA,3
GHMon,GHMon_NW,32.591451,23.910124,60881,IADEE,4
SN2024gtp,SN2024gtp,102.644083,+68.252231,43331.3,DACEA,6
M101HIIregionC1,M101HIIregion,161.2533346,-11.7653604,51001.7+,AAAEA,0

...

Any of the three catalogue templates above (FITS, CSV, simplified CSV) can be filled in with targets. These are the requested columns (the rest are optional):TARGPROG (. If not specified, the data release version and epoch of the GAIA coordinates will be DR3 and 2016.0 respectively. 

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)

...

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 ).

Please use this exposure time calculator for your signal-to-noise calculations: https://a.ing.iac.es/signalWEAVE/. There is more information, including a downloadable version, at WEAVE Exposure Time Calculator .

Instrument configuration

Check first what instrument modes are available in the ING announcement of opportunity. 

...

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).

Binning in the spectral direction

Binning in the spectral direction

Only listed values are allowed, all other values are forbidden. As an aside, note that there is no facility to request spatial binning. Such a mode would compromise the spectral extraction performance and crosstalk characterisation within the L1 pipeline.

...

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.Please use this exposure time calculator for your signal-to-noise calculations: https://a.ing.iac.es/signalWEAVE/. There is more information, including a downloadable version, at WEAVE Exposure Time Calculator .

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 refer registered WASP users to the OBSTEMP form: http://wasp.ast.cam.ac.uk/obstemp . (there is also a copy at ING: https://a.ing.iac.es/weave/obstemp.php).

DIMM seeing

Seeing is provided by a DIMM monitor located nearby the WHT, and it is measured as the full-width half-maximum (FWHM) brightness profile of a star if located at airmass 1.00.  Note that IFU observations are more tolerant of poorer seeing (diameter of the fibres is 2.6"). An instrument-level limit of seeing <3” is adopted due to degradation of guiding quality in poorer seeing.

...

IFU_PA_REQUEST allows the catalogue provider to specify a rotation angle (position angle) of the LIFU, if this is required. Note that the default value is zero.  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.

Image Added  

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. 

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.

...

...

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. Submission management allows the user to manage all FITS and OB submissions and select the ones active.

Image Removed

...

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.

Image Added

Observations and follow up

...