Target 2014MU69: 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: 718
----- Attempting Submission 1 (Fri Apr 08 19:22:24 GMT 2016) -----
HST Phase I Proposal 718 (Benecchi_NH_Lightcurve.apt) successfully submitted.
Receipt: # 718-12014MU69 won't be processed using the visit planner because it targets a Moving target.Updated ephemeris based on most recent astrometry results from HST program, PI Buie.1137004694----- Attempting Submission 1 (Tue Jul 19 19:24:28 GMT 2016) -----
----- Attempting Submission 2 (Mon Apr 03 08:56:49 GMT 2017) -----
----- Attempting Submission 3 (Tue Jun 06 00:45:23 GMT 2017) -----Everything has been verified by Bill Januszewski, this is just an ephemeris update.The Lightcurve of New Horizons Encounter TNO 2014 MU69The New Horizons spacecraft was recently redirected to encounter the Transneptunian Object (TNO) 2014 MU69 on 1 January 2019. In order to optimally plan the fly-by sequencing, we must learn as much about this object in advance of the encounter as possible. In particular, it is critical that we determine, to the best of our ability, if the object is binary (as is the case for ~20% of cold classical TNOs in this size range), the rotation period and shape of the body. All of these parameters influence the encounter design and timing. Existing and proposed HST astrometric datasets constrain its diameter (21-41 km for an albedo of 0.15-0.04) and orbit, and suggest a rotational lightcurve amplitude of >0.3 mags, but cannot determine the rotation period or lightcurve shape. To that end we propose to use 24 HST orbits over ~4 days to measure the lightcurve amplitude of 2014 MU69, and constrain its rotation period to better than 5%. 2014 MU69's orbit identifies it as very typical member of the "cold classical" TNO population. This makes it an ideal target for our spacecraft mission because close-up observations obtained of 2014 MU69 can be extrapolated to understand the cold classical population as a whole, which is the most primitive and least disturbed part of the Kuiper Belt.Our measurement sequence utilizes 4 sets of 6 consecutive HST orbits for a total of 24 orbits within the timespan of ~90 hours (4 days) near opposition when 2014 MU69 will be the brightest (July). Each visit includes 5x367 second exposures in the 350LP filter. The first sequence of orbits (visits 1-6 and 7-12) are separated by ~14 hours (~9 orbits) and the second sequence (visits 7-12 and 13-18) are separated by ~47 hours (~32 orbits) and the final sequence (visits 13-18 and 19-24) are separated by ~158 hours (~106 orbits). The orbits within a sequence must be consecutive in order to minimize aliasing interpretations of the period, however they do not require an identical set of guide stars, which should make scheduling easier. Observations near opposition are required because of the faintness of the object. Fields will be pre-searched for background sources as has been done effectively for previous programs. This involves selecting the times that are best for HST scheduling followed by the PI checking those pointings and fields for background sources, and either proceeding with the STScI selected time or suggesting another time when the field is clear. Adjustments to the exact timing and cadence will be analyzed as observations are being scheduled to deal with background star issues. This project imposes no orientation constraints and uses ordinary blind target acquisition. Target motion rates are very slow, at most a few arcsec per hour, so tracking under FGS control is feasible, regardless of the gyroscopic mode in use.Solar System6falsefalsefalsefalsefalsefalseSUPPORTEDSOLAR SYSTEMASTEROIDNH-Encounter-TNOTYPE=ASTEROID,A=44.393021984512,E=0.037829258490,I=2.453204044172,O=158.933218291765,W=177.301435896413,M=311.343123199475,EQUINOX=J2000,EPOCH=01-JUL-2017:00:00:00,EpochTimeScale=UTCEARTHWFC3/UVISImagingNoNoF350LPWFC3/UVISImagingNoNoF350LPWFC3/UVISImagingNoNoF350LPWFC3/UVISImagingNoNoF350LPWFC3/UVISImagingNoNoF350LPCELESTIALOTHER.030Objects will naturally dither themselves in a predominantly east-west direction.
This dither pattern uses offsets perpendicular to the mean motion of the objects
with a two-level pattern so that the dither cannot lead to a false detection with
coherent motion. The overall pattern is six positions with 0.75 pixel spacing.LINEfalsetrue50LINE1falseCELESTIALOTHER.030Objects will naturally dither themselves in a predominantly east-west direction.
This dither pattern uses offsets perpendicular to the mean motion of the objects
with a two-level pattern so that the dither cannot lead to a false detection with
coherent motion. The overall pattern is six positions with 0.75 pixel spacing.LINEfalsetrue40LINE2falseUsing ephemeris for target 14627-01-2014MU69ephemeris data for target 14627-01-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (01 02 03 04 05 06) Within 0.4 days] [Sequence (01 02 03 04 05 06 07 08) within 0.5 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.1498375559000253.30851364385308(Tic-Visit
:proposal-id 14627
:visit-id "01"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:18.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "01"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-02-2014MU69ephemeris data for target 14627-02-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (01 02 03 04 05 06) Within 0.4 days] [Sequence (01 02 03 04 05 06 07 08) within 0.5 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.1498381280000253.24523794157017(Tic-Visit
:proposal-id 14627
:visit-id "02"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:19.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "02"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-03-2014MU69ephemeris data for target 14627-03-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (01 02 03 04 05 06) Within 0.4 days] [Sequence (01 02 03 04 05 06 07 08) within 0.5 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.1498387001000253.1812270191577(Tic-Visit
:proposal-id 14627
:visit-id "03"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:20.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "03"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-04-2014MU69ephemeris data for target 14627-04-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (01 02 03 04 05 06) Within 0.4 days] [Sequence (01 02 03 04 05 06 07 08) within 0.5 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.1498392723000253.11645670763477(Tic-Visit
:proposal-id 14627
:visit-id "04"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:21.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "04"
:obset-id "04"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "04"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-05-2014MU69ephemeris data for target 14627-05-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (01 02 03 04 05 06) Within 0.4 days] [Sequence (01 02 03 04 05 06 07 08) within 0.5 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.1498404166000252.98463030586015(Tic-Visit
:proposal-id 14627
:visit-id "05"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:21.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "05"
:obset-id "05"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "05"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-06-2014MU69ephemeris data for target 14627-06-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (01 02 03 04 05 06) Within 0.4 days] [Sequence (01 02 03 04 05 06 07 08) within 0.5 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.1498409887000252.91754740788025(Tic-Visit
:proposal-id 14627
:visit-id "06"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:22.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "06"
:obset-id "06"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "06"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-07-2014MU69ephemeris data for target 14627-07-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (07 08 09 10 11 12) Within 0.4 days] [Sequence (01 02 03 04 05 06 07 08) within 0.5 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.1498461377000252.27589585638515(Tic-Visit
:proposal-id 14627
:visit-id "07"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:23.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "07"
:obset-id "07"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "07"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-08-2014MU69ephemeris data for target 14627-08-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (07 08 09 10 11 12) Within 0.4 days] [Sequence (01 02 03 04 05 06 07 08) within 0.5 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.1498467099000252.20008955831463(Tic-Visit
:proposal-id 14627
:visit-id "08"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:24.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "08"
:obset-id "08"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "08"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-09-2014MU69ephemeris data for target 14627-09-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (07 08 09 10 11 12) Within 0.4 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.1498472820000252.12333431246884(Tic-Visit
:proposal-id 14627
:visit-id "09"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:25.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "09"
:obset-id "09"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "09"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-10-2014MU69ephemeris data for target 14627-10-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (07 08 09 10 11 12) Within 0.4 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.1498478541000252.04559872999067(Tic-Visit
:proposal-id 14627
:visit-id "10"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:26.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "10"
:obset-id "10"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "10"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-11-2014MU69ephemeris data for target 14627-11-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (07 08 09 10 11 12) Within 0.4 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.1498495753000251.80630659047682(Tic-Visit
:proposal-id 14627
:visit-id "11"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:27.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "11"
:obset-id "11"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "11"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-12-2014MU69ephemeris data for target 14627-12-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (07 08 09 10 11 12) Within 0.4 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.1498501737000251.7199777999581(Tic-Visit
:proposal-id 14627
:visit-id "12"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:28.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "12"
:obset-id "12"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "12"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-13-2014MU69ephemeris data for target 14627-13-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (13 14 15 16 17 18) Within 0.4 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.1498627291000249.6078130387146(Tic-Visit
:proposal-id 14627
:visit-id "13"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:29.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "13"
:obset-id "13"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "13"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-14-2014MU69ephemeris data for target 14627-14-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (13 14 15 16 17 18) Within 0.4 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.1498633012000249.49464496811106(Tic-Visit
:proposal-id 14627
:visit-id "14"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:29.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "14"
:obset-id "14"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "14"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-15-2014MU69ephemeris data for target 14627-15-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (13 14 15 16 17 18) Within 0.4 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.1498638733000249.37973430272785(Tic-Visit
:proposal-id 14627
:visit-id "15"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:30.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "15"
:obset-id "15"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "15"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-16-2014MU69ephemeris data for target 14627-16-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (13 14 15 16 17 18) Within 0.4 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.1498644455000249.26302076906455(Tic-Visit
:proposal-id 14627
:visit-id "16"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:31.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "16"
:obset-id "16"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "16"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-17-2014MU69ephemeris data for target 14627-17-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (13 14 15 16 17 18) Within 0.4 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.1498661618000248.90183174037617(Tic-Visit
:proposal-id 14627
:visit-id "17"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:32.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "17"
:obset-id "17"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "17"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-18-2014MU69ephemeris data for target 14627-18-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (13 14 15 16 17 18) Within 0.4 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.1498667339000248.77758761024006(Tic-Visit
:proposal-id 14627
:visit-id "18"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:33.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "18"
:obset-id "18"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "18"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-19-2014MU69ephemeris data for target 14627-19-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (19 20 21 22 23 24) Within 0.4 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.(Tic-Visit
:proposal-id 14627
:visit-id "19"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:34.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "19"
:obset-id "19"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "19"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-20-2014MU69ephemeris data for target 14627-20-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (19 20 21 22 23 24) Within 0.4 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.(Tic-Visit
:proposal-id 14627
:visit-id "20"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:35.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "20"
:obset-id "20"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "20"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-21-2014MU69ephemeris data for target 14627-21-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (19 20 21 22 23 24) Within 0.4 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.(Tic-Visit
:proposal-id 14627
:visit-id "21"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:36.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "21"
:obset-id "21"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "21"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-22-2014MU69ephemeris data for target 14627-22-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (19 20 21 22 23 24) Within 0.4 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.(Tic-Visit
:proposal-id 14627
:visit-id "22"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:37.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "22"
:obset-id "22"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "22"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-23-2014MU69ephemeris data for target 14627-23-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (19 20 21 22 23 24) Within 0.4 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.(Tic-Visit
:proposal-id 14627
:visit-id "23"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:37.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "23"
:obset-id "23"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "23"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10Using ephemeris for target 14627-24-2014MU69ephemeris data for target 14627-24-2014MU69 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 16.214 to 18.091. ephemeris interval: 17.090 to 19.091Timing link suitability includes constraints ([Group (19 20 21 22 23 24) Within 0.4 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.We need to check the background field once scheduling windows for HST are chosen to ensure that there are no background stars which would compromise the observation.(Tic-Visit
:proposal-id 14627
:visit-id "24"
:proposal-version -1
:trans-version "20170109"
:date "03-Apr-2017 08:26:38.0"
:trans-errors '(:WARNINGS 0 :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 14627
:visit-id "24"
:obset-id "24"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14627
:visit-id "24"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2656
: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 2992
:pcs-gap 0
)false10