0Assigned ID: 731
----- Attempting Submission 1 (Fri Apr 11 19:49:33 GMT 2014) -----
HST Phase I Proposal 731 (gd394.apt) successfully submitted.
----- Attempting Submission 2 (Fri Apr 11 21:04:27 GMT 2014) -----Dear Miranda,
apologies, yes, there was a problem in defining the phase ranges for the visits 2,3,4,6,7,8,
which should all have a phase width of 0.03. We fixed that in this resubmission.
We used the "group within" timing requirement at visit level to get all 8 visits done
within 5 days, which will prevent excessive phase slippage due to the limited accuracy
of the WD rotation period - is this the right way to force all 8 visits to be done within
a 5 day window?
Best regards,
David & Boris-401424304----- Attempting Submission 1 (Fri Jul 18 09:38:35 GMT 2014) -----
----- Attempting Submission 2 (Mon Oct 13 11:17:45 GMT 2014) -----Accretion of planetary debris onto the unique white dwarf GD394It is now undisputed that metal-pollution of the H or He atmospheres observed in a substantial fraction of white dwarfs is due to accretion of planetary debris. While significant progress has been made in establishing the frequency of such evolved planetary systems, and statistics on the abundances of the debris material are beginning to emerge, very little is known regarding the delivery mechanism of the debris. Given that the red giant progenitors of the metal-polluted white dwarfs evaporated all planetary material within >1 AU, the debris found at many white dwarfs must originate originally from a substantial distance of the star. The canonical model is that remaining planets perturb the orbits of astroids, sending them onto a white dwarf grazing course, where the extreme gravity will result in their tidal disruption. The debris then must undergo complex dynamical evolution, and eventually fall into the white dwarf atmosphere.
EUV light curves of GD394, an extremely metal-polluted white dwarf, suggest a strong variation of the metal abundances over the stellar surface. We propose to obtain spin-phase resolved high-resolution spectroscopy of GD394 over its 1.15d rotation period to resolve the abundance pattern on its surface from variations in the photospheric metal lines, and thereby probe the geometry of the circumstellar debris. Line profile variations can be used to reconstruct the surface distribution of the metals using Roche tomography. In addition, comparison to a single archive HST/GHRS observation from 1992 will place tight constraints on the long-term variation of the accretion rate, and the life time of the circumstellar debris.The target of this program is a young hydrogen-atmosphere white dwarf that has a rotational period of 1.150+-0.003d, and shows photospheric contamination by metals in the HST and FUSE spectra. The aim of the STIS/E140M observations is to obtain spin-phase resolved high-resolution FUV spectroscopy sampling the entire rotation cycle, to probe for variations in the photospheric abundances.
Each individual 8 phase visits is one STIS orbit, centred on phases 0.0, 0.125, 0.25, 0.375, 0.5, 0.625, 0.75, 0.875. We allow for a 0.03 phase uncertainty to ease the scheduling, however, given that the period is not extremely accurately known, we group all 8 visits to be scheduled within 5 days to avoid the additional accumulation of phase error.HOT STARS12RegularfalsefalsefalsefalsefalseSUPPORTEDSTARDAGD 394 is a DA white dwarf with Teff=39660+-636K, log g=7.88+-0.05 (Gianninas et al. 2011ApJ...743..138G). It has a well-established and stable FUV flux, based on observations with IUE (swp41457, swp14296), HST/STIS (Z0YE0A0CM,
Z0YE0A0AM, Z0YE0A08M). F(1300A)=3e-12 erg/cm2/s/A.J2000J2000STIS/FUV-MAMASpectroscopicNoNoE140M1425STIS/FUV-MAMASpectroscopicNoNoE140M1425STIS/FUV-MAMASpectroscopicNoNoE140M1425STIS/FUV-MAMASpectroscopicNoNoE140M1425STIS/FUV-MAMASpectroscopicNoNoE140M1425STIS/FUV-MAMASpectroscopicNoNoE140M1425STIS/FUV-MAMASpectroscopicNoNoE140M1425STIS/FUV-MAMASpectroscopicNoNoE140M1425Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08) Within 5.0 days])The scheduling data was generated by CASM 23.0.CASM was run in Phase II mode./private/var/folders/ny/y2rfgxpn4k37g754z2ph3gd00001bc/T/OPVisit6994886655081979181.xml(Tic-Visit
:proposal-id 13719
:visit-id "01"
:proposal-version -1
:trans-version "20150417"
:date "14-May-2015 12:25:10.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 1913984
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13719
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13719
:visit-id "01"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 3076
:al-overhead-at-end 0
:internal-dur-at-end 578
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3409
:pcs-gap 0
)true10The ETC simulation STIS.sp.622199 gives a "Count rate entire detector" of 14300 cts/s, i.e. a buffer time of 133sec. To be on the safe side, I opted for a margin of ~30%, and use the shortest possible buffer time (99sec).Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08) Within 5.0 days])The scheduling data was generated by CASM 23.0.CASM was run in Phase II mode./private/var/folders/ny/y2rfgxpn4k37g754z2ph3gd00001bc/T/OPVisit7005399048430979519.xml(Tic-Visit
:proposal-id 13719
:visit-id "02"
:proposal-version -1
:trans-version "20150417"
:date "14-May-2015 12:25:12.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 1913984
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13719
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13719
:visit-id "02"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 3076
:al-overhead-at-end 0
:internal-dur-at-end 578
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3409
:pcs-gap 0
)true10The ETC simulation STIS.sp.622199 gives a "Count rate entire detector" of 14300 cts/s, i.e. a buffer time of 133sec. To be on the safe side, I opted for a margin of ~30%, and use the shortest possible buffer time (99sec).Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08) Within 5.0 days])The scheduling data was generated by CASM 23.0.CASM was run in Phase II mode./private/var/folders/ny/y2rfgxpn4k37g754z2ph3gd00001bc/T/OPVisit4614560440875580275.xml(Tic-Visit
:proposal-id 13719
:visit-id "03"
:proposal-version -1
:trans-version "20150417"
:date "14-May-2015 12:25:14.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 1913984
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13719
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13719
:visit-id "03"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 3076
:al-overhead-at-end 0
:internal-dur-at-end 578
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3409
:pcs-gap 0
)true10The ETC simulation STIS.sp.622199 gives a "Count rate entire detector" of 14300 cts/s, i.e. a buffer time of 133sec. To be on the safe side, I opted for a margin of ~30%, and use the shortest possible buffer time (99sec).Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08) Within 5.0 days])The scheduling data was generated by CASM 23.0.CASM was run in Phase II mode./private/var/folders/ny/y2rfgxpn4k37g754z2ph3gd00001bc/T/OPVisit1828465575742598066.xml(Tic-Visit
:proposal-id 13719
:visit-id "04"
:proposal-version -1
:trans-version "20150417"
:date "14-May-2015 12:25:16.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 1913984
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13719
:visit-id "04"
:obset-id "04"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13719
:visit-id "04"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 3076
:al-overhead-at-end 0
:internal-dur-at-end 578
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3409
:pcs-gap 0
)true10The ETC simulation STIS.sp.622199 gives a "Count rate entire detector" of 14300 cts/s, i.e. a buffer time of 133sec. To be on the safe side, I opted for a margin of ~30%, and use the shortest possible buffer time (99sec).Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08) Within 5.0 days])The scheduling data was generated by CASM 23.0.CASM was run in Phase II mode./private/var/folders/ny/y2rfgxpn4k37g754z2ph3gd00001bc/T/OPVisit6287161607254134516.xml(Tic-Visit
:proposal-id 13719
:visit-id "05"
:proposal-version -1
:trans-version "20150417"
:date "14-May-2015 12:25:18.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 1913984
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13719
:visit-id "05"
:obset-id "05"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13719
:visit-id "05"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 3076
:al-overhead-at-end 0
:internal-dur-at-end 578
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3409
:pcs-gap 0
)true10The ETC simulation STIS.sp.622199 gives a "Count rate entire detector" of 14300 cts/s, i.e. a buffer time of 133sec. To be on the safe side, I opted for a margin of ~30%, and use the shortest possible buffer time (99sec).Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08) Within 5.0 days])The scheduling data was generated by CASM 23.0.CASM was run in Phase II mode./private/var/folders/ny/y2rfgxpn4k37g754z2ph3gd00001bc/T/OPVisit9123901303903988545.xml(Tic-Visit
:proposal-id 13719
:visit-id "06"
:proposal-version -1
:trans-version "20150417"
:date "14-May-2015 12:25:20.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 1913984
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13719
:visit-id "06"
:obset-id "06"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13719
:visit-id "06"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 3076
:al-overhead-at-end 0
:internal-dur-at-end 578
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3409
:pcs-gap 0
)true10The ETC simulation STIS.sp.622199 gives a "Count rate entire detector" of 14300 cts/s, i.e. a buffer time of 133sec. To be on the safe side, I opted for a margin of ~30%, and use the shortest possible buffer time (99sec).Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08) Within 5.0 days])The scheduling data was generated by CASM 23.0.CASM was run in Phase II mode./private/var/folders/ny/y2rfgxpn4k37g754z2ph3gd00001bc/T/OPVisit1535565131913140386.xml(Tic-Visit
:proposal-id 13719
:visit-id "07"
:proposal-version -1
:trans-version "20150417"
:date "14-May-2015 12:25:22.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 1913984
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13719
:visit-id "07"
:obset-id "07"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13719
:visit-id "07"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 3076
:al-overhead-at-end 0
:internal-dur-at-end 578
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3409
:pcs-gap 0
)true10The ETC simulation STIS.sp.622199 gives a "Count rate entire detector" of 14300 cts/s, i.e. a buffer time of 133sec. To be on the safe side, I opted for a margin of ~30%, and use the shortest possible buffer time (99sec).Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08) Within 5.0 days])The scheduling data was generated by CASM 23.0.CASM was run in Phase II mode./private/var/folders/ny/y2rfgxpn4k37g754z2ph3gd00001bc/T/OPVisit8425436163849707127.xml(Tic-Visit
:proposal-id 13719
:visit-id "08"
:proposal-version -1
:trans-version "20150417"
:date "14-May-2015 12:25:23.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 1913984
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13719
:visit-id "08"
:obset-id "08"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13719
:visit-id "08"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 3076
:al-overhead-at-end 0
:internal-dur-at-end 578
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3409
:pcs-gap 0
)true10The ETC simulation STIS.sp.622199 gives a "Count rate entire detector" of 14300 cts/s, i.e. a buffer time of 133sec. To be on the safe side, I opted for a margin of ~30%, and use the shortest possible buffer time (99sec).