README web version of /home/usg/OPS/MTS/readme_xml/readme_76041000
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
These observations will provide high-contrast, high-spatial resolution
imaging to look for substellar companions (Giant Planets or Brown Dwarfs) and very
low mass stars orbiting nearby WDs. The WDs were selected from a sample of WDs up
to 20 pc, where almost all have high proper motion. It will be usefull to confirm
candidates by observing them in a second epoch. The observations consists of simple
imaging in J-band with repeated jitters in a WD position in very large exposure
(& execution) times, to reach the required detection limit of giant planets
and/or low mass brown dwarfs.
IMPORTANT: Most of the targets OBs have two different NACO_img_obs_Autojitter templates,
because of their high brighteness. The first NACO_img_obs_Autojitter template within
an OB has DIT avoiding the non-linearity range, and it is necessary for PSF calibration,
WD astrometry and photometry, while the second template with DIT near to the saturation
limit is necessary to reach the required depth to detect a giant planet with reasonable
execution times (to lessen overheads). Both templates are very important for the
success of our project. Targets that have only one NACO_img_obs_Autojitter template
have DITs that don't saturate the primary (WD), this is possible because the primary
is not too bright. We avoided that any star in the FOV over-saturates the detector
(i.e., with less than 1.3 times of the number of counts of the saturation limit).
We have calculated the DIT for each OB using the NACO ETC with a seeing of 0.6''
so that in the first NACO_img_obs_Autojitter template the targets are very near
to the non-linearity limit but under this (and the brighter object in FOV doesn't
over-saturate) and in the second NACO_img_obs_Autojitter template the targets or
the brighter objects in the FOV are approximately on the saturation limit, but taking
care of not over-saturating ,so that over-saturation could leave residuals images
in the detector. For the second template we want the longest DIT than it is possible
without over-saturation and without exceeding the 60s. **We required that these
points at the time of making the observations are taken into account**.
NB: ** IMPORTANT ** Coordinates in the OBs are given in equinox J2000, but for the
epoch 2005.9 (not 2000.0), i.e., the coordinates have been corrected for the WDs
PM to epoch 2005.9. We could not edit (change) the epoch in the OBs, and it still
says 2000.0 while it is really 2005.9. For completeness we included the PMs in RA
and DEC.
Waiver Requests
Critical Observing Condition Constraints
It is necesary to make observations with very good seeing (0.6'') to reach
to detect very faint objects (24 mag in J-band). Also it is required to carry out
the observations in smaller airmass as this were possible, to lessen differential
color difraction and to obtain a better FWHM of the objects. The best period are
indicated in each OB, in Calibration Requeriments.
Time-Critical Aspects
Special Execution Requirements
We have calculated the DIT for each OB using the NACO ETC with a seeing
of 0.6'' so that in the first NACO_img_obs_Autojitter template the targets are very
near to the non-linearity limit but under this (and the brighter object in FOV doesn't
over-saturate) and in the second NACO_img_obs_Autojitter template the targets or
the brighter objects in the FOV are approximately on the saturation limit, but taking
care of not over-saturating ,so that over-saturation could leave residuals images
in the detector. For the second template we want the longest DIT than it is possible
without over-saturation and without exceeding the 60s. **We required that these
points at the time of making the observations are taken into account**.
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:10 2009
If you have comments, please contact usd-help@eso.org