INEFFICIENT ORDERING OF FP-POS POSITIONS
INEFFICIENT ORDERING OF FP-POS POSITIONS
INEFFICIENT ORDERING OF FP-POS POSITIONS
INEFFICIENT ORDERING OF FP-POS POSITIONS
A target acquisition should probably be performed before doing
spectroscopy or coronography with STIS or COS.
INEFFICIENT ORDERING OF FP-POS POSITIONS
INEFFICIENT ORDERING OF FP-POS POSITIONS
INEFFICIENT ORDERING OF FP-POS POSITIONS
INEFFICIENT ORDERING OF FP-POS POSITIONSLatest version. Main modifications are
-- using FP-POS=ALL for all FUV visits, except for orbit 1 in each of these visits;
-- using FP-POS=3 for orbit 1 in the FUV visits (there isn't enough visibility time for a full FP-POS cycle)
-- fixed visibility overruns (now using latest version of APT)
-- added comments about scheduling constraints as visit-level comments, but no explicit linking of visits now-455545784----- Attempting Submission 3 (Wed Jun 24 13:45:31 GMT 2015) -----The remaining errors seem benign or wrong. Most are associated with the use of FP-POS=3 in the first orbit of the FUV visits, which is something we're doing intentionally (as explained in the submission comments). There are also warnings about target acqs not happening, even though they seem to be explicitly there.Ultraviolet Spectroscopy of the Black Hole Transient V404 Cygni in OutburstOn June 15, the accreting black hole (BH) X-ray binary V404 Cyg underwent one of its rare transitions into a high-luminosity state. There are only about 20 dynamically confirmed accreting BH systems, and V404 Cyg is one of the brightest and closest of these. Its last outburst occurred more than 25 years ago, in late May 1989, so the current eruption is being intensely monitored across the electromagnetic spectrum. However, in spite of its astrophysical importance, the far-ultraviolet (FUV) waveband is so far entirely missing from this multi-wavelength campaign. Here, we propose to rectify this omission by obtaining UV spectroscopy of V404 Cyg during the next HST visibility period (July 4 - 13). The resulting data set will allow us to (i) detect and characterize any accretion disk wind in the system; (ii) determine the broad-band SED of the outer accretion disk, which is expected to peak in the UV region; (iii) determine the evolutionary history of the system from the N and C line strengths; (iv) detect and characterize the UV variability properties and search for wavelength-dependent reprocessing lags; (v) determine the extinction towards the system, and hence its luminosity and accretion rate. Since the decay time-scale of the outburst is expected to be about 30 days, this is likely to be the only opportunity to obtain these critical UV observations.We will visit V404 Cyg three times with HST. The first and third visit will each consist of 5 consecutive HST orbits, during which we will carry out time-resolved far-UV spectroscopy with the COS/G140L instrument/grating combination. We will use the 1105 A setting for all of these observations to achieve continuous wavelength coverage between 1121 A and 2148 A. The TIME-TAG mode of COS will provide sufficient time resolution to capture variability on the dynamical time-scale within the accretion disk. COS is preferred to STIS in the far-UV despite due to its much higher sensitivity in this waveband.
The second visit will consist of 2 consecutive HST orbits, during which we will obtain time-resolved near-UV spectroscopy with the STIS/NUV-MAMA/G230L instruments/detector/grating combination. This gives continuous wavelength coverage between 1570 A and 3180 A, again at a time resolution sufficient to resolve fast flickering.
Recent near-UV photometry obtained by Swift/UVOT shows that F_lambda,NUV ~ 1-5 x 1e-16 erg/cm^2/ s/A. (Motta et al. 2015b), where the near-UV measurement corresponds to the UVW1 or UVW2 filters, which have central wavelength of 2600 A and 1900 A, respectively. Since the intrinsic SED is likely to be blue, but subject to considerable reddening, far-UV and near-UV fluxes will probably be comparable. Based on these numbers, and allowing for overheads, we then estimate that 10 HST orbits of far-UV spectroscopy will yield a combined spectrum with S/N ~ 5-15 per resolution element at 1500 A. Similarly, our 2 orbits of near-UV spectroscopy will yield a combined spectrum with S/N ~ 5-15 per resolution element at 2800 A.
There are no safety concerns for the COS or STIS detectors. In the near-UV, the existing Swift/UVOT observations show that the system is nowhere near bright enough to threaten detector damage. No empirical data exists so far in the far-UV, but even the most extreme plausible extrapolation from the near-UV to the far-UV -- assuming that both near-UV and far-UV emission lie on the Rayleigh-Jeans tail of the disk spectrum (F_lambda ~ lambda^{-4}) -- yields local and global count rates that remain well below the bright object limits.
We will use an imaging target acquisition with Mirror B as the best compromise between efficiency and instrument safety. With this set-up, a 1 min ACQ/IMAGE target acquisition exposure yields S/N ~ 30-60 depending on the detailed SED shape, and the count rate in the brightest pixel never exceeds 8 c/s, well below the bright object limit.
The observations should ideally take place as soon as possible, in order to ensure that we catch the system before it decays too much. We therefore request that the observations should be scheduled in the next available scheduling window (July 4-13) and preferably near the start of this window.
We also request that the near-UV visit should take place between the two far-UV visits and that all three visits should take place as close in time as possible. This will allow us to construct a near-simultaneous global SED.
Several of us are leaders/members of ongoing monitoring campaigns at other wavelengths, so we can rely on existing/approved programs to obtain (near-)simultaneous coverage across the entire frequency range. In order to facilitate the scheduling of the HST program, we are not requesting any of these auxiliary observations to be formally linked to the HST observations. Instead, we will simply make a best effort to achieve obtain the widest possible range of auxiliary observations as close as possible to the time of the HST observations.
We finally note that, given the strong variability currently seen at all wavelengths and on all time-scales (e.g. Ferrigno et al. 2015; Motte et al. 2015ab; Hynes et al. 2015; Hardy et al. 2015; Tetarenko et al. 2015), it is impossible to predict with certainty whether the system is likely to be detectable in the far-UV in early July. We are therefore happy to work with STScI to mitigate the risk of a non-detection. For example, it may be possible to implement a ``dead-man's switch'', whereby the HST observations will only be executed if Swift/UVOT near-UV photometry closer to the HST scheduling window indicates a significant likelihood of success.HOT STARS0AVAILABLESTARACCRETION DISKWINDX-RAY NOVAEX-RAY TRANSIENTNOPosition, proper motion and parallax are from Miller-Jones et al. (2009). They are all based on radio/VLBI measurements and should be on the ICRF.J2000J2000UNIDENTIFIEDBLANK FIELDNOThis target is a blank piece of sky which is the bright object safe pointing and is 9.755 arcseconds away at a PA 283.8 degrees from V-V404-CYG.J2000COS/FUVSpectroscopicNoNoG140L1105STIS/NUV-MAMASpectroscopicNoNoG230L2376COS/FUVSpectroscopicNoNoG140L1105The scheduling data was generated by CASM 23.2.CASM was run in Phase II mode.This should be scheduled in evening-local time. Flags need to be cleared during the work day.
As discussed with Beth Perriello, we have not explicitly linked our 3 visits in order to provide maximum scheduling flexibility. However, we do have some important preferences/constraints:
1) it is not necessary to schedule all 3 visits as closely as possible, but the NUV visit should be spaced as closely as possible to *one* of the FUV visits;
2) the remaining FUV visit should be executed as early as possible in the visibility window;
3) the FUV+NUV set should also execute as early as possible, to the extent permitted by (1) above.(Tic-Visit
:proposal-id 14065
:visit-id "01"
:proposal-version -1
:trans-version "20150609"
:date "25-Jun-2015 16:41:05.0"
:trans-errors '(:WARNINGS 3 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 5
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 296256
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 14065
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14065
:visit-id "01"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2472
:al-overhead-at-end 0
:internal-dur-at-end 56
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3245
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 14065
:visit-id "01"
:orbit-number 2
:pcs-time 222
:si-vis-utilization 3023
:al-overhead-at-end 0
:internal-dur-at-end 48
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3245
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 14065
:visit-id "01"
:orbit-number 3
:pcs-time 222
:si-vis-utilization 3021
:al-overhead-at-end 0
:internal-dur-at-end 48
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3245
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 14065
:visit-id "01"
:orbit-number 4
:pcs-time 222
:si-vis-utilization 3021
:al-overhead-at-end 0
:internal-dur-at-end 48
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3245
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 14065
:visit-id "01"
:orbit-number 5
:pcs-time 222
:si-vis-utilization 3021
:al-overhead-at-end 0
:internal-dur-at-end 341
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3245
:pcs-gap 0
)false50This visit is for BOP checking the safe target only and should not execute onboard HST.(Tic-Visit
:proposal-id 14065
:visit-id "01"
:proposal-version -1
:trans-version "20150609"
:date "24-Jun-2015 14:36:51.0"
:trans-errors '(:WARNINGS 4 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 5
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 304992
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 14065
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14065
:visit-id "01"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2912
:al-overhead-at-end 0
:internal-dur-at-end 38
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3245
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 14065
:visit-id "01"
:orbit-number 2
:pcs-time 222
:si-vis-utilization 3021
:al-overhead-at-end 0
:internal-dur-at-end 48
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3245
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 14065
:visit-id "01"
:orbit-number 3
:pcs-time 222
:si-vis-utilization 3021
:al-overhead-at-end 0
:internal-dur-at-end 48
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3245
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 14065
:visit-id "01"
:orbit-number 4
:pcs-time 222
:si-vis-utilization 3021
:al-overhead-at-end 0
:internal-dur-at-end 48
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3245
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 14065
:visit-id "01"
:orbit-number 5
:pcs-time 222
:si-vis-utilization 3021
:al-overhead-at-end 0
:internal-dur-at-end 341
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3245
:pcs-gap 0
)false50The scheduling data was generated by CASM 23.2.CASM was run in Phase II mode.As discussed with Beth Perriello, we have not explicitly linked our 3 visits in order to provide maximum scheduling flexibility. However, we do have some important preferences/constraints:
1) it is not necessary to schedule all 3 visits as closely as possible, but the NUV visit should be spaced as closely as possible to *one* of the FUV visits;
2) the remaining FUV visit should be executed as early as possible in the visibility window;
3) the FUV+NUV set should also execute as early as possible, to the extent permitted by (1) above.(Tic-Visit
:proposal-id 14065
:visit-id "02"
:proposal-version -1
:trans-version "20150609"
:date "25-Jun-2015 08:07:06.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 2
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 800592
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 14065
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14065
:visit-id "02"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2912
:al-overhead-at-end 0
:internal-dur-at-end 178
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3245
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 14065
:visit-id "02"
:orbit-number 2
:pcs-time 222
:si-vis-utilization 3023
:al-overhead-at-end 0
:internal-dur-at-end 582
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3245
:pcs-gap 0
)true20The scheduling data was generated by CASM 23.2.CASM was run in Phase II mode.This should be scheduled in evening-local time. Flags need to be cleared during the work day.
As discussed with Beth Perriello, we have not explicitly linked our 3 visits in order to provide maximum scheduling flexibility. However, we do have some important preferences/constraints:
1) it is not necessary to schedule all 3 visits as closely as possible, but the NUV visit should be spaced as closely as possible to *one* of the FUV visits;
2) the remaining FUV visit should be executed as early as possible in the visibility window;
3) the FUV+NUV set should also execute as early as possible, to the extent permitted by (1) above.(Tic-Visit
:proposal-id 14065
:visit-id "03"
:proposal-version -1
:trans-version "20150609"
:date "25-Jun-2015 16:41:26.0"
:trans-errors '(:WARNINGS 3 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 5
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 296256
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 14065
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14065
:visit-id "03"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2472
:al-overhead-at-end 0
:internal-dur-at-end 56
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3245
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 14065
:visit-id "03"
:orbit-number 2
:pcs-time 222
:si-vis-utilization 3023
:al-overhead-at-end 0
:internal-dur-at-end 48
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3245
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 14065
:visit-id "03"
:orbit-number 3
:pcs-time 222
:si-vis-utilization 3021
:al-overhead-at-end 0
:internal-dur-at-end 48
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3245
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 14065
:visit-id "03"
:orbit-number 4
:pcs-time 222
:si-vis-utilization 3021
:al-overhead-at-end 0
:internal-dur-at-end 48
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3245
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 14065
:visit-id "03"
:orbit-number 5
:pcs-time 222
:si-vis-utilization 3021
:al-overhead-at-end 0
:internal-dur-at-end 341
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3245
:pcs-gap 0
)false50This visit allocates and sets up the safe position offset slot for visit 01 which will use that slot. This S/C visits should go earlier in the week while visit 01 will be at least 3 days later.1436243818000179.99990844726562false-1-1This visit allocates and sets up the safe position offset slot for visit 03 which will use that slot. This S/C visit should go earlier in the week while visit 03 will be at least 3 days later.1436426889000179.99990844726562false-1-1/private/var/folders/tc/ydsxjyy102b9cplf304tbl300005f2/T/OPVisit8981301571021572612.xmlThis visit will clear the slot.(Tic-Visit
:proposal-id 14065
:visit-id "CU"
:proposal-version -1
:trans-version "20150609"
:date "08-Jul-2015 14:11:03.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "11"
:si-bright-earth-limb-angle 20.0
:data-volume 0
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 14065
:visit-id "CU"
:obset-id "CU"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14065
:visit-id "CU"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 68
:al-overhead-at-end 0
:internal-dur-at-end 0
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3245
:pcs-gap 0
)false10