README web version of /home/usg/OPS/MTS/readme_xml/readme_77046500
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
These OBs are for ToO observations of a black hole X-ray binary, V4641
Sgr with the HITI mode of FORS2/VLT. The main goal of this run is to obtain power
spectra of the optical emission from the target in outburst, which possibly comes
from a vicinity of a stellar mass black hole. Our team has a ToO time of the RXTE
satellite, which enables us to perform simultaneous observations of X-ray and optical
variations. In this project, we focus on a time-scale of 0.001-10 sec.
Our target, V4641 Sgr, has entered in outburst once per year in the last few
years (2002 May, 2003 Aug, 2004 Jul, and 2005 Jun). We can expect the next outburst
during this semester.
The prepared OBs are quite simple; there are 18 OBs, but all of them have same
configurations. For more information about the OBs, see "ToO information".
We rotate the field in order to put the target and another standard star simultaneously
on the slit. This is also indicated in the attached finding chart. See "Special
Execution Requirements".
Waiver Requests
Critical Observing Condition Constraints
Time-Critical Aspects
Special Execution Requirements
Please note that we rotate the field in order to put the target and another
comparison star simultaneously on the MOS slit. The position of the target, V4641
Sgr, is RA=18:19.21.58, Dec=-25:24:25.1. The neighbor comparison star, GSC2.2_S301231150215,
is at RA=18:10:22.701, Dec=-25:24:17.84. The rotation angle is calculated to be
-66.65 deg. (PA=66.65). The separation of them is about 18", so a longer MOS slit
(22") is preferable than a shorter one (20") for our observations. We attached
a finding chart, which may helpful for observers.
Special Calibration Information
ToO Information
These are ToO OBs. The ToO run will be triggered when the target is in
outburst.
Our target, V4641 Sgr, is V=13.8 at quiescence and V=12-10 during outbursts
(highly variable).
The most important point is a quick start of the run when we trigger the ToO.
In other words, the ToO observation should be peformed even under thin clouds or
bad seeings when it is triggered.
All prepared OBs are same; about 1 hour run with the HIT_OS3 mode. In total,
we have 18 hours for our ToO, hence, the number of the OBs is 18. It depends on
the situation how many OBs should be performed in one night, while we put the minimum
and maximum time, that is, 2 and 6 hours (2 and 6 OBs) in one night, respectively.
So, the range of run times is variable between 2 - 6 hours in one night, and the
number of nights for our ToO is also variable between 3 - 9 nights (18/6 - 18/2).
We will notify the number of OBs to be performed in one night, at the same time
that we trigger the ToO run.
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 prepared your finding charts with tools other than FIMS,
do they comply with the specifications on the FORS2 Phase 2 web page ?
Last creation of page: Tue Oct 6 15:40:13 2009
If you have comments, please contact usd-help@eso.org