Target NH-KBO: There is no need or capability to test the scheduling of observations of moving targets in Phase I. This warning will go away the next time the proposal is loaded.
Target NH-KBO2: There is no need or capability to test the scheduling of observations of moving targets in Phase I. This warning will go away the next time the proposal is loaded.0Assigned ID: 451
----- Attempting Submission 1 (Fri Apr 11 12:56:41 GMT 2014) -----An error is generated because my targets are moving solar system objects. The warning I get is
that " There is no need or capability to test the scheduling of observations of moving targets
in Phase I. This warning will go away the next time the proposal is loaded."ORBITAL VISIBILITY OVERRUN
Unschedulable Visit
ORBITAL VISIBILITY OVERRUN
Unschedulable Visit
ORBITAL VISIBILITY OVERRUN
Unschedulable Visit
ORBITAL VISIBILITY OVERRUN
Unschedulable VisitWe are requesting ToO activation to observe one newly discovered KBO.
Visits 01,02,03 and 04 are for KBO G12000JZ ("KBO-G1").
Visits 01,02 should be executed in consecutive orbits on Oct 15, if possible.
Visits 03,04 should be executed in consecutive orbits on Oct 22, if possible.
Please inform us as soon as specific observation times are picked, so we can
verify there no spoiler objects that might adversely affect our ability to detect
these faint KBOs.992110127----- Attempting Submission 1 (Thu Jul 17 20:52:49 GMT 2014) -----
----- Attempting Submission 2 (Wed Sep 17 00:13:53 GMT 2014) -----
HST Phase II Proposal 13663 (13663_Revised_weaver.apt) successfully submitted.
----- Attempting Submission 3 (Fri Oct 03 22:42:42 GMT 2014) -----The orbit planner complained that the activities overrun
the visibility window by 5 sec for each of the 10 visits,
but that's probably spurious. If it's indeed true that these
10 visits overrun the available window, then we will shave
5-10 sec from each exposure to get back in the box.
In any case, *all* exposure times for all images must be identical.Precise Orbit Determination for a New Horizons KBOThe New Horizons (NH) spacecraft will flyby the Pluto system next summer, after this the spacecraft will be retargeted to one or more Kuiper Belt Objects (KBOs) to learn about the remnant material from our outer solar system's formation. We are actively carrying out dedicated ground-based observations to identify a target for NH to flyby and continue to improve our analysis algorithms. To date, we have 52 discoveries including five objects that are long-range reconnaissance candidates, and two that current orbit predictions require about a factor of 2 more propellant than is available for the encounter maneuver. Our searches are continuing in to 2014 and we anticipate as many as 2 objects that will require high precision HST imaging. Unfortunately, NH's trajectory line of site is within the galactic center (Sagittarius) making stellar confusion a major problem in recovering these objects from the ground to obtain precise astrometry and high precision orbits. HST's sensitivity, resolution and PSF stability are crucial components for the success of the NH Kuiper belt mission component. We are requesting 4 TOO orbits to be triggered when a candidate object is found within the targetable region. These observations will provide the required high precision astrometry required for targeting, will evaluate if the NH candidate is binary (~30%) and will make a preliminary color determination to assist in long or short range encounter planning.We obtain 5-370 second exposures in the F350LP filter using a line dither pattern to obtain astrometric measurements for a faint NH candidate object.The orbits are scheduled in pairs so that images can be co-added to meet the depth requirement and the pairs separated by days to meet the orbit extension requirements to determine targetability. Colors as described in the abstract have been set asside because the astrometric need is greater and the object is fainter than originally expected.SOLAR SYSTEMDefaultfalsefalsefalsefalsefalseSUPPORTEDSOLAR SYSTEMSATELLITENH-KBOTYPE=ASTEROID,A=46.405608921901,E=0.26388505198582,I=4.1466231993107,O=136.00700117810,W=49.426808689232,M=64.734133299721,EQUINOX=J2000,EPOCH=20-AUG-2014:00:00:00,EpochTimeScale=UTCEARTHWFC3/UVISImagingNoNoF606WWFC3/UVISImagingNoNoF814WWFC3/UVISImagingNoNoF814WWFC3/UVISImagingNoNoF606WWFC3/UVISImagingNoNoF606WWFC3/UVISImagingNoNoF814WWFC3/UVISImagingNoNoF814WWFC3/UVISImagingNoNoF606WCELESTIALOTHER0.75LINEfalsetrue50LINE1falseUsing ephemeris for target 13663-01-KBO-G1ephemeris data for target 13663-01-KBO-G1 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.273 to 16.275Timing link suitability includes constraints ([Sequence (01 02) within 0.1 days] [Sequence (01 04) within 0.1 days] [02 After 01 by 0.1 to 0.1 days])The scheduling data was generated by CASM 22.2.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 13663
:visit-id "01"
:proposal-version -1
:trans-version "20140605"
:date "04-Oct-2014 16:11:44.0"
:trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "29"
:si-bright-earth-limb-angle 20.0
:data-volume 1443744
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13663
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13663
:visit-id "01"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2671
:al-overhead-at-end 0
:internal-dur-at-end 668
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2999
:pcs-gap 0
)true11Using ephemeris for target 13663-02-KBO-G1ephemeris data for target 13663-02-KBO-G1 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.273 to 16.275Timing link suitability includes constraints ([Sequence (01 02) within 0.1 days] [02 After 01 by 0.1 to 0.1 days])The scheduling data was generated by CASM 22.2.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 13663
:visit-id "02"
:proposal-version -1
:trans-version "20140605"
:date "04-Oct-2014 16:11:47.0"
:trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "29"
:si-bright-earth-limb-angle 20.0
:data-volume 1443744
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13663
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13663
:visit-id "02"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2671
:al-overhead-at-end 0
:internal-dur-at-end 668
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2999
:pcs-gap 0
)true11Using ephemeris for target 13663-03-KBO-G1ephemeris data for target 13663-03-KBO-G1 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.273 to 16.275Timing link suitability includes constraints ([04 After 03 by 0.1 to 0.1 days])The scheduling data was generated by CASM 22.2.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 13663
:visit-id "03"
:proposal-version -1
:trans-version "20140605"
:date "04-Oct-2014 16:11:49.0"
:trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "29"
:si-bright-earth-limb-angle 20.0
:data-volume 1443744
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13663
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13663
:visit-id "03"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2671
:al-overhead-at-end 0
:internal-dur-at-end 668
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2999
:pcs-gap 0
)true11Using ephemeris for target 13663-04-KBO-G1ephemeris data for target 13663-04-KBO-G1 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.273 to 16.275Timing link suitability includes constraints ([Sequence (01 04) within 0.1 days] [04 After 03 by 0.1 to 0.1 days])The scheduling data was generated by CASM 22.2.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 13663
:visit-id "04"
:proposal-version -1
:trans-version "20140605"
:date "04-Oct-2014 16:11:51.0"
:trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "29"
:si-bright-earth-limb-angle 20.0
:data-volume 1443744
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 13663
:visit-id "04"
:obset-id "04"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 13663
:visit-id "04"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2671
:al-overhead-at-end 0
:internal-dur-at-end 668
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2999
:pcs-gap 0
)true11