|
|
Triggering the NOT
What do I do?
-
If the object is visible, call immediately the observing room of the NOT telescope
- Use one of the following email templates to execute the observation and modify the
bold printed tags:
To: staff@not.iac.es, observer@not.iac.es, grb@dark-cosmology.dk
Subject: Activation of the ToO program (51-504) of P. Jakobsson for GRB ??????
Email content:
Dear NOT observer and staff.
This is a trigger of the GRB ToO programme (PI: Palli Jakobsson).
For further details, please see:
http://www.not.iac.es/observing/too/P51/P51-504/
Please reply to grb@dark-cosmology.dk to acknowledge the reception
of this request. The target information and the observing strategy
are reported below.
Please let us know if you carry out time-critical observations.
For any questions please do not hesitate to contact me on my mobile
phone <***** insert your phone# *****>.
Thank you for your collaboration,
<***** insert your name *****> (on behalf of the Nordic GRB team)
------------
The purpose of the observation is to monitor [search for] the optical
afterglow of GRB ??????. Please execute these observations as soon as
possible. [Please execute these observations around ?? UT when
the object becomes visible at the NOT.]
Target information, including a link to a La Palma visibility plot and
a finding chart (note that the GRB afterglow is a new object in the
field, and therefore does not appear on the chart):
< ***** insert the link to the correct webpage. Look at the
GRB alert email, click on "More finding charts" and then
on "GE" for the appropriate burst ***** >>
------------
The burst is localised to the following position:
RA(J2000) = < ***** COORDINATE ***** >
Dec(J2000) = < ***** COORDINATE ***** >
Current uncertainty radius = < ***** ERROR RADIUS ***** >
We ask for the following observations with ALFOSC [StanCam]:
- R band: 3 x 300 s
- I band: 5 x 400 s
The commands to run the scripts are [TRIGGER PERSON: add
GRB name, coordinates, and delete the appropriate instrument
command]:
Go to ~obs/scripts/51-504
And execute
tcs.enter-object GRB?????? hh mm ss ±deg mm ss 2000 0 0 0
[TRIGGER PERSON: for StanCam add]: tcs.setup-tel-stancam
./too-alfosc-photometry.sh GRB?????? R,300,3 I,400,5 dither=5-point:6
./too-stancam-photometry.sh GRB?????? R,300,3 I,400,5 dither=5-point:6
if the command is too long, write instead
./too-alfosc-photometry.sh GRB?????? U,360,5 B,300,5 V,360,5 \
R,300,5 I,300,5 Z_SDSS,300,5 dither=5-point:6
./too-stancam-photometry.sh GRB?????? U,360,5 B,300,5 V,360,5 \
R,300,5 I,300,5 Z_SDSS,300,5 dither=5-point:6
For more information on the various command options (e.g. dithering):
[TRIGGER PERSON: delete the appropriate link]
http://www.not.iac.es/observing/too/P51/P51-504/photo_stancam.html
http://www.not.iac.es/observing/too/P51/P51-504/photo_alfosc.html
------------
For calibration we request [TRIGGER PERSON: edit accordingly]:
Photometry:
- R-band twilight flats (remember to dither between exposures)
- I-band twilight flats (remember to dither between exposures)
- 10 bias frames
Please ensure that all the calibration data are transferred to
our FTP account by activating remsave before the calibration data
are obtained:
rempath /data/service/calib
remsave_on
When the calibration files have been acquired, please turn off remsave:
remsave_off
------------
This webpage was last updated on July 16, 2013. Please send comments or suggestions to
| |