README web version of /home/usg/OPS/MTS/readme_xml/readme_77500500
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
This program deals with the discovery and monitoring of the variable IR
counterpart of the magnetar candidate SGR1900+14. The run is devided into two epochs,
each one being 1.5hr long. The OBs of the first epoch (*1stepoch*) have to be carried
out as soon as the sky costraints will be met.
The second epoch OBs (*2ndepoch*) have to be executed after 1-2 months apart from
the 1st one.
Bright Sources
--------------
OBs IR magnitudes
within S27
--------------------------------------------
SGR1900* H = 7 Ref1
Waiver Requests
Critical Observing Condition Constraints
Time-Critical Aspects
Special Execution Requirements
the target has been already observed by NACO on 31st March 2006. The astronomer
on duty had a number of problems due to two bright objects a 10 arcsec from the
target. We modified the OBs following the successful strategy of the astronomer
on duty. Below is his original night log
-- There was no flux on the VIS WFS to close the loop. Hence, we switched to the
IR WFS (mode 2-1) using dichro N20C80. Then, a high flux level was obtained, and
we could close the loop with very good and stable correction (SR around 50%).
Furhtermore, to avoid strong artefacts through the high saturation of the
two extremely bright stars at the very left side of the detector, we moved these
stars completely out of the FOV. Hence, the SGR is not centered anymore, but shifted
to the left. To avoid that the SGR is shifted close to the border of the FOV. And
to avoid that one of the bright stars enters the FOV, the jitter width was adjusted
from 7'' to 3''. The modified setup should ensure that the science goals can be
achieved. Note that despite all this improvements still two strong ghosts (from
the two extremely bright stars) are visible a bit south of the SGR....... ---
NOTE THAT THE MINIMUM JITTERING WIDTH ACCEPTED BY P2PP IS 4 ARCSEC. IF NEEDED WE
ASK TO MODIFY THE OB JITTER FROM 4 TO 3 ARCSEC .
FINALLY, WE REQUEST TO DOWNLOAD THE SCIENTIFIC AND CALIBRATION FILES THROGH THE
FTP SERVER IN PARANAL AT THE END OF THE NIGHTS DURING WHICH OBS ARE EXECUTED.
Special Calibration Information
ToO Information
ToO Activators List
Is this a Pre-imaging run ?
Pre-imaging Requirements
Source(s) of Pre-imaging
Pre-imaging sources not listed above
Do all your OBs comply with the instrument-specific requirements listed
on the instrument-specific Phase 2 web page ?
If this is a pre-imaging run, did you select PRE-IMAGING for the Observing
Category for each Observing Template ?
Do all your finding charts comply with both the general and instrument-specific
Phase 2 Web Pages ?
If you submitted OBs for standard stars, did you specify the magnitude
and spectral type of all standard stars in the OBs ?
Have you included OBs for any calibrations that you need but which are
not part of the Calibration Plan ?
If you are observing Moving Targets, have you attached suitable ephemeris
files to your OBs?
If you have preferences which OBs should be executed first, did you make
use of the User Priority field in the OBs ?
If this is a run that requires coordinated observations with other facilities,
did you give proper instructions in the Time-Critical Aspects Section ?
If you have PSF reference star OBs, do the names of those OBs begin with
PSF_ ?
If there are Finding Charts attached to your OBs, is the field-of-view
of at least one of these charts 2' x 2' (with clearly labelled field orientation)
?
Have you clearly marked and labelled your wavefront reference objects
R1, R2, R3, ... (as specified in the NAOS Preparation Software) on your Finding
Charts ?
Have you specified the magnitude of the brightest object in the field-of-view
for each OB ?
Are there objects in any of your fields (including standard stars) which
are brighter than the limits specified in the User Manual and on NACO web Pages
?
If the previous answer is yes, have you given a list of OBs and a justification
for the brightness limit violation in the general description field ?
Last creation of page: Tue Oct 6 15:40:14 2009
If you have comments, please contact usd-help@eso.org