I just noticed I forgot to check "UV Initiative".
Our proposal is for UV spectroscopy and clearly falls into this category.-261735944Assigned ID: 674
----- Attempting Submission 1 (Fri Apr 11 18:47:43 GMT 2014) -----
HST Phase I Proposal 674 (comet_too.apt) successfully submitted.
----- Attempting Submission 2 (Fri Apr 11 22:53:00 GMT 2014) -----
HST Phase I Proposal 674 (comet_too.apt) successfully submitted.
----- Attempting Submission 3 (Fri Apr 11 22:59:46 GMT 2014) -----
HST Phase I Proposal 674 (comet_too.apt) successfully submitted.
----- Attempting Submission 4 (Sat Apr 12 11:33:30 GMT 2014) -----Sensitive exposures should have an ETC run number provided.
Sensitive exposures should have an ETC run number provided.
For the best data quality, it is strongly recommended that all four FP-POS positions be used when observing at a given COS CENWAVE setting.
Sensitive exposures should have an ETC run number provided.
Sensitive exposures should have an ETC run number provided.
Sensitive exposures should have an ETC run number provided.
Sensitive exposures should have an ETC run number provided.
Sensitive exposures should have an ETC run number provided.
Sensitive exposures should have an ETC run number provided.
For the best data quality, it is strongly recommended that all four FP-POS positions be used when observing at a given COS CENWAVE setting.
Sensitive exposures should have an ETC run number provided.
Sensitive exposures should have an ETC run number provided.
Sensitive exposures should have an ETC run number provided.
Sensitive exposures should have an ETC run number provided.
Sensitive exposures should have an ETC run number provided.
Sensitive exposures should have an ETC run number provided.
For the best data quality, it is strongly recommended that all four FP-POS positions be used when observing at a given COS CENWAVE setting.
Sensitive exposures should have an ETC run number provided.
Sensitive exposures should have an ETC run number provided.
Sensitive exposures should have an ETC run number provided.
Sensitive exposures should have an ETC run number provided.
A target acquisition should probably be performed before doing
spectroscopy or coronography with STIS or COS.
Could not find ephemeris for target 13874-10-COMET-LOVEJOY-OFFSET
Sensitive exposures should have an ETC run number provided.This is a Target of Opportunity program that we're triggering on C/2014 Q2 (Lovejoy).
This version of the proposal used JPL ephemeris solution #18.
We ask that all visits be completed within 3 days because the comet may change
significantly if the program is stretched out over a longer period of time.
One important constraint, not explicitly indicated in the phase2, is that the
STIS E140H observations should *not* be made in consecutive orbits, or immediately
after an orbit when the MAMA-FUV detector was used. This detector has a
"hot splotch" of anomalously high noise as it warms up, so we'd like the E140H
observations to execute when the MAMA-FUV is relatively cold.
visits 2, 5, 8 exp. 2 was originally reduced from 1800s -> 1719s; if it fits, please bring these back to 1800s.
visit 10, exp. 1, reduced from 240 ->237 (longer adds another wavecal and it goes over).-524194912----- Attempting Submission 1 (Fri Jul 25 00:25:19 GMT 2014) -----
----- Attempting Submission 2 (Tue Jul 29 17:09:28 GMT 2014) -----
----- Attempting Submission 3 (Wed Jan 14 18:48:03 GMT 2015) -----For whatever reason, APT can't get an ephemeris for our OFFSET target (last visit).
All the other warnings are due to bogus complaints about not supplying an ETC number.Using Hubble to Measure Volatile Abundances and the D/H Ratio in a Bright ToO CometWe propose a 10-orbit program to observe any newly discovered bright comet
as a non-disruptive Target of Opportunity during cycle 22.
For a comet whose water production rate meets our basic ToO selection criterion,
Hubble observations can be used to measure abundances of three highly volatile
species (CO, CO2, and S2), providing critical information on the origin and evolution
of the comet's nucleus. If the comet additionally has geocentric and heliocentric
radial velocities in a favorable range, our Hubble observations will measure
atomic deuterium emission, from which we can derive the D/H ratio for comparison
to the values measured in other comets and Earth's water. The D/H ratio in cometary
water is a key indicator of the role played by comets in the delivery of volatiles
to the terrestrial planets. This is a non-disruptive ToO program because we
anticipate that execution of the proposed observations need not be scheduled
until at least 1 month after the triggering event. We have already identified
four potential targets (C/2013 V5 (Oukaimeden), C/2012 K1 (PanSTARRS),
C/2013 A1 (Siding Spring), C/2014 E2 (Jacques)), but it is still too early
to tell if any of these will meet our ToO selection criteria.We request 3 orbits using STIS/G230L with the 0.2 slit to measure CO Cameron, CS,
S2, and OH emissions at 13 A resolution. Although the CO Cameron bands should be
detectable with SNR>6 in 1 orbit for our minimal comet and a nominal CO2 abundance
(~5%), 3 orbits would permit a more robust detection (SNR>10). Furthermore,
if the comet is bright enough, measurements of CO Cameron emission in multiple orbits will
determine whether the CO2 abundance varies with time, as it did rather dramatically (by a
factor of ~2) during the EPOXI flyby of 103P/Hartley.
For the observations of D (assuming the comet satisfies the requirements discussed in the
proposal), we will use STIS/E140H with the 0.2 x 6 arcsecslit. This slit was used successfully
to detect D in C/NEAT and provides a five-fold improvement in sensitivity compared to the
standard 0.2 x 0.2 arcsec slit. We request 3 orbits to obtain a secure D/H detection, even for our
minimal comet.
We request a 1 orbit observation using E140H offset by a large distance from the nucleus,
so that we can measure the H Ly-alpha emission in a region of the coma where it is optically
thin. From these data we can derive a highly reliable H production rate, which is needed
for the D/H ratio. We can also compare QH2O derived from this offset measurement to the
values derived from the other orbits using OH emission.
COS/NUV ACQ/SEARCH and ACQ/IMAGE will be employed in each COS orbit to
accurately place the nucleus in the aperture (PSA). Similarly, a STIS/CCD ACQ will be
employed in each STIS orbit. We also plan to take at least a couple STIS/CCD F28x50LP
full-frame images during the course of our program to provide context for our spectroscopic
program (e.g., to provide information on jets and other coma asymmetries).
All the above orbits should be grouped within a 1-3 day period, so the comet's observing
circumstances won't change significantly during that time. As always, we'll work closely with
the program's PC to optimize the observing plan for our scientific objectives.SOLAR SYSTEMDefaultfalsetruefalsefalsefalseSUPPORTEDSOLAR SYSTEMUpdated on 1/14/2015 to use Comet C/2014 Q2 (Lovejoy) as the target.COMETComet-Lovejoy-2014Q2TYPE=COMET,Q=1.290354613349346,E=0.9977694972445712,I=80.30301629940526,O=94.97534212651479,W=12.39562582691785,T=30-JAN-2015:01:41:08,TTimeScale=TDB,EQUINOX=J2000,EPOCH=20-NOV-2014,EpochTimeScale=TDBEARTHSOLAR SYSTEMUpdated on 1/14/2015 to use Comet C/2014 Q2 (Lovejoy) as the target.COMETComet-Lovejoy-2014Q2-OFFSETTYPE=COMET,Q=1.290354613349346,E=0.9977694972445712,I=80.30301629940526,O=94.97534212651479,W=12.39562582691785,T=30-JAN-2015:01:41:08,TTimeScale=TDB,EQUINOX=J2000,EPOCH=20-NOV-2014,EpochTimeScale=TDBTYPE=POS_ANGLE,RAD=1500,ANG=0,REF=SUNEARTHCOS/FUVSpectroscopicNoNoG160M1589STIS/NUV-MAMASpectroscopicNoNoG230L2376STIS/FUV-MAMASpectroscopicNoNoE140H1234STIS/FUV-MAMASpectroscopicNoNoE140H1234Using ephemeris for target 13874-01-COMET-LOVEJOYephemeris data for target 13874-01-COMET-LOVEJOY does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 14.213 to 16.090. ephemeris interval: 14.365 to 17.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10) Within 3.0 days])The scheduling data was generated by CASM 22.2.CASM was run in Phase II mode./Users/weaveha1/Documents/Proposals/hst/cycle22/comet_too/phase2/OP-cache/13874_1-14-2015_v2-v01.xml(Tic-Visit
:proposal-id 13874
:visit-id "01"
:proposal-version -1
:trans-version "20140605"
:date "14-Jan-2015 13:32:51.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 87408
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13874
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13874
:visit-id "01"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2450
:al-overhead-at-end 0
:internal-dur-at-end 394
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2999
:pcs-gap 0
)true10Using ephemeris for target 13874-02-COMET-LOVEJOYephemeris data for target 13874-02-COMET-LOVEJOY does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 14.213 to 16.090. ephemeris interval: 14.365 to 17.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10) Within 3.0 days])The scheduling data was generated by CASM 22.2.CASM was run in Phase II mode./private/var/folders/tb/q3zsbl1j6d3gvdw7h3dn3qmj9fwgz5/T/OPVisit639707690889986239.xml(Tic-Visit
:proposal-id 13874
:visit-id "02"
:proposal-version -1
:trans-version "20140605"
:date "14-Jan-2015 13:33:08.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 124208
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13874
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13874
:visit-id "02"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2615
:al-overhead-at-end 0
:internal-dur-at-end 434
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2999
:pcs-gap 0
)true10Using ephemeris for target 13874-03-COMET-LOVEJOYephemeris data for target 13874-03-COMET-LOVEJOY does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 14.213 to 16.090. ephemeris interval: 14.365 to 17.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10) Within 3.0 days])The scheduling data was generated by CASM 22.2.CASM was run in Phase II mode./private/var/folders/tb/q3zsbl1j6d3gvdw7h3dn3qmj9fwgz5/T/OPVisit4977462411562975850.xml(Tic-Visit
:proposal-id 13874
:visit-id "03"
:proposal-version -1
:trans-version "20140605"
:date "14-Jan-2015 13:33:30.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 226256
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13874
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13874
:visit-id "03"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2486
:al-overhead-at-end 0
:internal-dur-at-end 385
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2999
:pcs-gap 0
)true10Using ephemeris for target 13874-04-COMET-LOVEJOYephemeris data for target 13874-04-COMET-LOVEJOY does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 14.213 to 16.090. ephemeris interval: 14.365 to 17.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10) Within 3.0 days])The scheduling data was generated by CASM 22.2.CASM was run in Phase II mode./private/var/folders/tb/q3zsbl1j6d3gvdw7h3dn3qmj9fwgz5/T/OPVisit6259493220577728213.xml(Tic-Visit
:proposal-id 13874
:visit-id "04"
:proposal-version -1
:trans-version "20140605"
:date "14-Jan-2015 13:33:40.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 87408
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13874
:visit-id "04"
:obset-id "04"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13874
:visit-id "04"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2450
:al-overhead-at-end 0
:internal-dur-at-end 394
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2999
:pcs-gap 0
)true10Using ephemeris for target 13874-05-COMET-LOVEJOYephemeris data for target 13874-05-COMET-LOVEJOY does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 14.213 to 16.090. ephemeris interval: 14.365 to 17.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10) Within 3.0 days])The scheduling data was generated by CASM 22.2.CASM was run in Phase II mode./private/var/folders/tb/q3zsbl1j6d3gvdw7h3dn3qmj9fwgz5/T/OPVisit6387664009143689265.xml(Tic-Visit
:proposal-id 13874
:visit-id "05"
:proposal-version -1
:trans-version "20140605"
:date "14-Jan-2015 13:33:43.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 124208
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13874
:visit-id "05"
:obset-id "05"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13874
:visit-id "05"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2615
:al-overhead-at-end 0
:internal-dur-at-end 434
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2999
:pcs-gap 0
)true10Using ephemeris for target 13874-06-COMET-LOVEJOYephemeris data for target 13874-06-COMET-LOVEJOY does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 14.213 to 16.090. ephemeris interval: 14.365 to 17.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10) Within 3.0 days])The scheduling data was generated by CASM 22.2.CASM was run in Phase II mode./private/var/folders/tb/q3zsbl1j6d3gvdw7h3dn3qmj9fwgz5/T/OPVisit7479908962097142315.xml(Tic-Visit
:proposal-id 13874
:visit-id "06"
:proposal-version -1
:trans-version "20140605"
:date "14-Jan-2015 13:34:03.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 226256
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13874
:visit-id "06"
:obset-id "06"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13874
:visit-id "06"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2486
:al-overhead-at-end 0
:internal-dur-at-end 385
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2999
:pcs-gap 0
)true10Using ephemeris for target 13874-07-COMET-LOVEJOYephemeris data for target 13874-07-COMET-LOVEJOY does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 14.213 to 16.090. ephemeris interval: 14.365 to 17.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10) Within 3.0 days])The scheduling data was generated by CASM 22.2.CASM was run in Phase II mode./private/var/folders/tb/q3zsbl1j6d3gvdw7h3dn3qmj9fwgz5/T/OPVisit1784250973910718990.xml(Tic-Visit
:proposal-id 13874
:visit-id "07"
:proposal-version -1
:trans-version "20140605"
:date "14-Jan-2015 13:34:08.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 87408
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13874
:visit-id "07"
:obset-id "07"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13874
:visit-id "07"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2450
:al-overhead-at-end 0
:internal-dur-at-end 394
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2999
:pcs-gap 0
)true10Using ephemeris for target 13874-08-COMET-LOVEJOYephemeris data for target 13874-08-COMET-LOVEJOY does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 14.213 to 16.090. ephemeris interval: 14.365 to 17.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10) Within 3.0 days])The scheduling data was generated by CASM 22.2.CASM was run in Phase II mode./private/var/folders/tb/q3zsbl1j6d3gvdw7h3dn3qmj9fwgz5/T/OPVisit3885731922937066169.xml(Tic-Visit
:proposal-id 13874
:visit-id "08"
:proposal-version -1
:trans-version "20140605"
:date "14-Jan-2015 13:34:15.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 124208
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13874
:visit-id "08"
:obset-id "08"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13874
:visit-id "08"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2615
:al-overhead-at-end 0
:internal-dur-at-end 434
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2999
:pcs-gap 0
)true10Using ephemeris for target 13874-09-COMET-LOVEJOYephemeris data for target 13874-09-COMET-LOVEJOY does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 14.213 to 16.090. ephemeris interval: 14.365 to 17.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10) Within 3.0 days])The scheduling data was generated by CASM 22.2.CASM was run in Phase II mode./private/var/folders/tb/q3zsbl1j6d3gvdw7h3dn3qmj9fwgz5/T/OPVisit4280466177825757779.xml(Tic-Visit
:proposal-id 13874
:visit-id "09"
:proposal-version -1
:trans-version "20140605"
:date "14-Jan-2015 13:34:22.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 226256
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13874
:visit-id "09"
:obset-id "09"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13874
:visit-id "09"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2486
:al-overhead-at-end 0
:internal-dur-at-end 385
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2999
:pcs-gap 0
)true10/private/var/folders/tb/q3zsbl1j6d3gvdw7h3dn3qmj9fwgz5/T/OPVisit2700413760217688084.xml(Tic-Visit
:proposal-id 13874
:visit-id "10"
:proposal-version -1
:trans-version "20140605"
:date "14-Jan-2015 13:34:30.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 86992
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13874
:visit-id "10"
:obset-id "10"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13874
:visit-id "10"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2631
:al-overhead-at-end 0
:internal-dur-at-end 394
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2999
:pcs-gap 0
)true10