How to triggerStep 1: Prepare a CSV catalogue
See instructions on how to prepare a CSV catalogue at WEAVE Open-Time Phase 2: The Short Guide. An example of a CSV catalogue follows.
filename: [eg: WS2026A2-010_target_list.csv]
TARGID,TARGNAME,GAIA_RA,GAIA_DEC,PROGTEMP,OBSTEMP,IFU_DITHER,IFU_PA_REQUEST
NGC3158,NGC3158,153.460497,38.764898,41331,NBCEB,3,180
|
Use PROGTEMP and OBSTEMP builders. IFU_DITHER can be 0 for no dithering or 3,4,5 or 6 for point ditehring. Note that number of exposures per OB and dithering points must match. We can only provide the standard values for position angle, ie. 0° for declinations south of +28.7° and 180° for north of +28.7°.
Step 2: Fill out the template below, attach CSV catalogue and email
Follow instructions in square brackets.
TO: trigger ing.iac.es
SUBJECT: "Override request"
ATTACHMENT: WS2026A2-010_target_list.csv
Programme: [eg: WS2026A2-010]
Triggered by: [eg: John Smith (john.smith@astro.com)]
Response time scale: [eg: immediately, not later than 30 minutes, or on a more relaxed timeline;
include age of the burst if a GRB; specify night if triggered well before observations are
requested;
unless specifically required, say if twilight can be acceptable]
Comments: [comment on observing constraints (seeing, airmass, etc.),
if requesting the raw data the soonest possible, etc.]
|
Step 3: Preparation of OBs and observing
The ING trigger team will make the requested OBs and ingest into the observing queue. Observations will be attempted at the earliest opportunity, following the provided instructions. Data retrieval Allow for a one or few days before the data are reduced and L1 products are made available on the WEAVE Operational Repository (login with the programme's credentials). If urgent assessment of the data is requested, then the observers will upload the data to the ING ftp server. Conflict resolutionIf multiple programmes trigger on the same night, unless precedence rules have been set, then the programme which was triggered first takes priority. Triggers are limited to a maximum of two hours' duration per night including all overheads, unless . If competing teams trigger for the same target and instrument setup, the observations will be attempted for the team whose request was received first. However, in these circumstances the teams may elect to share the data. In this event, the time used will be accounted on a 50% basis to the teams involved, and the duration of the override will be limited to two hours, including overheads.
|
