README web version of /home/usg/OPS/MTS/readme_xml/readme_80018900

Principal Investigator Email Address

• nuno@astro.up.pt

Estimated Total Execution Time (hours, including overheads)

• 5

General Description

• This program aims at trying to measure a possible photometric transit
   of
  a previously detected radial-velocity brown-dwarf companion to HD41004B (M2 dwarf).
  HD41004A, a brighter K dwarf, is located just 0.5'' from HD41004B.
  
  HD41004A will be used as AO reference, since its V magnitude
  difference to HD41004B is very high in optical wavelengths.
  We are using WFS in VIS and observations in K-band.
  
  All OBs for this program have to be executed in a row (5h in a row),
  in the sequence: "HD27209_first" -> "HD41004_1" -> "PSF_HD68607"
  
  Please note that the ephemeris for transits listed in the "Time-Critical Aspects"
   section 
  below list the UT TIME TO START THE FIRST OB ("HD27209_first").
  
  The magnitudes of the three stars are (all K dwarfs):
  
  HD41004: V=8.65; K~6.43 (main science target)
  HD27209: V=8.92; K~6.96
  HD68607: V=8.83; K~6.82
  
  HD41004A will be used as photometric reference for the photometric measurements
  of HD41004B. Two PSF standards will be observed, before and after HD41004.
  
  Rem: after some iteraction we decided that the best way to
  perform the observations is to observe HD27209 without the PSF ticker (although
   it
  is indded supposed to be a PSF standard), and then to follow with 
  observations of HD41004 and HD68607 (both) with the PSF ticker on. This means
  we will certainly keep the same NACO configuration for all stars.

Waiver Requests

• Waiver requests were submited and granted to:
  
  - Observe the several OBs in a row (5 hours in a row), and have one OB
    4.3 hours long (HD41004_1): this is necessary to well cover the transit 
    curve and to observe the PSF standards just before and after the observations
    on the main target
  - Not include finding charts (targets are bright, isolated, and saturate 
    DSS image)

Critical Observing Condition Constraints

• Seeing better than 1'' and airmass below 1.6. This latter constraint is
  taken into account using the time-critical aspects mentioned below.

Time-Critical Aspects

• The measurements should be STARTED (first OB executed) in the dates/hours
   
  mentioned in the table below.
  
  The time to START the observations refers to the start of the 
  FIRST OB (HD27209_first, ~20 minutes long). All the OBs should 
  be observed in the sequence: 
  \"HD27209_first\" -> \"HD41004_1\" -> \"PSF_HD68607\".
  
  column 1: date
  column 2: best UT time to start of observations
  column 3: UT time interval to start the observations
  
  10 11 2008	3h50	3h50 - 4h00
  14 11 2008	3h50	3h30 - 3h50
  18 11 2008	3h50	3h00 - 3h50
  22 11 2008	3h50	2h40 - 3h50
  26 11 2008	3h50	2h20 - 4h00
  30 11 2008	3h10	2h00 - 4h20
  04 12 2008	2h50	1h40 - 4h00
  08 12 2008	2h30	1h20 - 3h40
  12 12 2008	2h00	0h50 - 3h10
  16 12 2008	1h50	0h30 - 2h50
  20 12 2008	1h30	0h10 - 2h30
  24 12 2008	1h10	0h10 - 2h10
  28 12 2008	0h50	0h10 - 1h50
  01 01 2009	0h10	0h10 - 1h20
  05 01 2009	0h10	0h10 - 1h00
  09 01 2009	0h10	0h10 - 0h40
  13 01 2009	0h10	0h10 - 0h20
  
  Rem: since the time interval field of the OB only contains 5 entries, we did not
  include the transit times there.

Special Execution Requirements

• OBs should be executed in the following order (and one after the other):
  
  1) HD27209_first
  2) HD41004_1
  3) PSF_HD68607
  
  All OBs should be executed in a row.

Special Calibration Information

• We need FF with high S/N: the goal of the observations is to obtain accurate
   photometric measurements of HD41004B (at a 1% precision or better)

ToO Information

• This is not a ToO program

ToO Activators List

• ---(Empty)---

Is this a Pre-imaging run ?

• false

Pre-imaging Requirements

• ---(Empty)---

Source(s) of Pre-imaging

• ---(Empty)---

Pre-imaging sources not listed above

• ---(Empty)---

Do all your OBs comply with the instrument-specific requirements listed
 on the instrument-specific Phase 2 web page ?

• YES

If this is a pre-imaging run, did you select PRE-IMAGING for the Observing
 Category for each Observing Template ?

• N/A

Do all your finding charts comply with both the general and instrument-specific
 Phase 2 Web Pages ?

• N/A

If you submitted OBs for standard stars, did you specify the magnitude
 and spectral type of all standard stars in the OBs ?

• N/A

Have you included OBs for any calibrations that you need but which are
 not part of the Calibration Plan ?

• N/A

If you are observing Moving Targets, have you attached suitable ephemeris
 files to your OBs?

• N/A

If you have preferences which OBs should be executed first, did you make
 use of the User Priority field in the OBs ?

• N/A

If this is a run that requires coordinated observations with other facilities,
 did you give proper instructions in the Time-Critical Aspects Section ?

• N/A

If you have PSF reference star OBs, do the names of those OBs begin with
 PSF_ ?

• YES

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

• N/A

Have you clearly marked and labelled your wavefront reference objects
 R1, R2, R3, ... (as specified in the NAOS Preparation Software) on your Finding
 Charts ?

• N/A

Have you specified the magnitude of the brightest object in the field-of-view
 for each OB ?

• N/A

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
 ?

• NO

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 ?

• N/A