0Assigned ID: 1338
----- Attempting Submission 1 (Tue Jan 31 22:31:53 GMT 2017) -----
HST Phase I Proposal 1338 (PMbinary_submit.apt) successfully submitted.
Receipt: # 1338-1
----- Attempting Submission 2 (Tue Jan 31 22:36:28 GMT 2017) -----
HST Phase I Proposal 1338 (PMbinary_submit.apt) successfully submitted.
Receipt: # 1338-2
----- Attempting Submission 3 (Wed Feb 01 00:23:39 GMT 2017) -----
HST Phase I Proposal 1338 (PMbinary_submit.apt) successfully submitted.
Receipt: # 1338-3
----- Attempting Submission 4 (Wed Feb 01 03:17:02 GMT 2017) -----revision with following changes:
using UVIS2-M512C-SUB subarray - high S/N expected, minimal sensitivity to CTE, away from bad columns
added seq non-int for the F555W astrometric exposures. other exposures in separate sequence to allow for flexible scheduling
added additional F555W exposures in visits 02-05. If scheduling is tight, options include eliminating F814W and/or one of the three F555W repeats
additional changes with this resubmission:
put all exposures in visit 01 in single seq non-int
added seq non-int for F814W exposures in visits 02-05
visit 11 is not to be executed - saved as alternate version of visit 01. can be deleted once visit 01 is scheduled.1470832343----- Attempting Submission 1 (Wed Apr 19 15:46:29 GMT 2017) -----
----- Attempting Submission 2 (Tue Apr 25 15:06:56 GMT 2017) -----
----- Attempting Submission 3 (Sat Apr 29 02:38:34 GMT 2017) -----Orbit of the Patroclus-Menoetius Binary, a Lucy Mission TargetWe are proposing to observe Trojan binary asteroid (617) Patroclus-Menoetius, one of the targets of the Lucy mission. Lucy was selected as the next Discovery mission on January 4, 2017, for launch in October 2021. Observations this year are needed to establish the mutual orbit of the binary, which is of critical importance for mission planning. The mutual orbit phase is essentially undetermined from the accumulation of orbit period uncertainty since last measured in 2010. Orbital phase is needed in order to be able to predict the timing of mutual events that will begin late in 2017. These mutual events are essential to planning for the Lucy mission, especially in establishing the precise orientation of the mutual orbit plane and ascending node that is critical to early planning for flyby encounter design and capabilities.Observations will consist of five one-orbit visits. Each visit will have a minimum component of 9 dithers in the F555W. For at least one visit we will supplement this with additional color filters as proposed.
We will use the phase option to tie visits to the 103 hour orbit of the binary in order to get sampling around the orbit. If possible, the observations should span multiple binary orbit periods consistent with the phasing (i.e. add n*P). All observations must be completed by June 24, 2017.
We have a preference for some of the visits to occur as soon as possible in order to maximize angular resolution.Solar System3falsefalsefalsefalsefalsefalseSUPPORTEDSOLAR SYSTEMASTEROIDTrojan Binary (617) PatroclusTYPE=ASTEROID,A=5.217346931413996 ,E=0.1382962811465384,I=22.04733136614898,O=44.3552188187178 ,W=308.3729072973491 ,M=137.0180464264951 ,EQUINOX=J2000,EPOCH=16-FEB-2017:00:00:00,EpochTimeScale=TDBEARTHWFC3/UVISImagingNoNoF336WWFC3/UVISImagingNoNoF438WWFC3/UVISImagingNoNoF555WWFC3/UVISImagingNoNoF814WWFC3/UVISImagingNoNoF336WWFC3/UVISImagingNoNoF438WWFC3/UVISImagingNoNoF555WWFC3/UVISImagingNoNoF814WWFC3/UVISImagingNoNoF336WWFC3/UVISImagingNoNoF438WWFC3/UVISImagingNoNoF555WWFC3/UVISImagingNoNoF814WWFC3/UVISImagingNoNoF336WWFC3/UVISImagingNoNoF438WWFC3/UVISImagingNoNoF555WWFC3/UVISImagingNoNoF814WWFC3/UVISImagingNoNoF336WWFC3/UVISImagingNoNoF438WWFC3/UVISImagingNoNoF555WWFC3/UVISImagingNoNoF814WPOS-TARGDITHER0.173LINE0.112falsefalse81.785423.884WFC3-UVIS-DITHER-BOX1falseUsing ephemeris for target 14928-11-PATROCLUSephemeris data for target 14928-11-PATROCLUS 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.091The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 14928
:visit-id "11"
:proposal-version -1
:trans-version "20170109"
:date "28-Apr-2017 22:31: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 69904
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 14928
:visit-id "11"
:obset-id "11"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14928
:visit-id "11"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2867
:al-overhead-at-end 0
:internal-dur-at-end 113
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3210
:pcs-gap 0
)true10version of first visit with filters separated. less efficient but allows for orbit splitting if neededUsing ephemeris for target 14928-01-PATROCLUSephemeris data for target 14928-01-PATROCLUS 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.091The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 14928
:visit-id "01"
:proposal-version -1
:trans-version "20170109"
:date "28-Apr-2017 22:33:03.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 69904
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 14928
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14928
:visit-id "01"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2742
:al-overhead-at-end 0
:internal-dur-at-end 113
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3210
:pcs-gap 0
)true10Using ephemeris for target 14928-02-PATROCLUSephemeris data for target 14928-02-PATROCLUS 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.091The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 14928
:visit-id "02"
:proposal-version -1
:trans-version "20170109"
:date "28-Apr-2017 22:32:14.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 69904
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 14928
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14928
:visit-id "02"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2303
:al-overhead-at-end 0
:internal-dur-at-end 113
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3210
:pcs-gap 0
)true10Using ephemeris for target 14928-03-PATROCLUSephemeris data for target 14928-03-PATROCLUS 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.091The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 14928
:visit-id "03"
:proposal-version -1
:trans-version "20170109"
:date "28-Apr-2017 22:33:06.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 69904
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 14928
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14928
:visit-id "03"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2303
:al-overhead-at-end 0
:internal-dur-at-end 113
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3210
:pcs-gap 0
)true10Using ephemeris for target 14928-04-PATROCLUSephemeris data for target 14928-04-PATROCLUS 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.091The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 14928
:visit-id "04"
:proposal-version -1
:trans-version "20170109"
:date "28-Apr-2017 22: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 "29"
:si-bright-earth-limb-angle 20.0
:data-volume 69904
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 14928
:visit-id "04"
:obset-id "04"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14928
:visit-id "04"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2303
:al-overhead-at-end 0
:internal-dur-at-end 113
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3210
:pcs-gap 0
)true10Using ephemeris for target 14928-05-PATROCLUSephemeris data for target 14928-05-PATROCLUS 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.091The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 14928
:visit-id "05"
:proposal-version -1
:trans-version "20170109"
:date "28-Apr-2017 22:33:11.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 69904
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 14928
:visit-id "05"
:obset-id "05"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14928
:visit-id "05"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2303
:al-overhead-at-end 0
:internal-dur-at-end 113
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3210
:pcs-gap 0
)true10Phasing requirements discussed in the phase 1 are required, but have not been included in the phase 2 because there is no way to do this easily without artificially overconstraining the problem.
For the Patroclus binary we will assume a binary orbital period of 103.11 hours for planning purposes. The goal is to get five visits at every 0.20+/-0.02 of this orbital phase. The uncertainty in the phasing of +/-0.02 corresponds to +/-2 hours so that multiple orbits should be usable on a given day. It is possible to relax this if needed with consultation.
There is no particular phase at which we need to start, but we do have preferred times for visit 1 which contains all three color filters. Those times, in JD, starting in mid-May from the time of the last estimated peak are shown below. We prefer as close to the start of this list as possible for angular resolution. Acceptable start times are +/-5 hours for this visit relative to the tabulated time below if this is used as the first visit. Subsequent visits would then follow the phasing as described above.
binary orbit JD 2457... date
10 876.79 May 03, 6:58
11 881.09 May 07, 14:10
12 885.38 May 11, 21:07
13 889.68 May 16, 04:19
14 893.98 May 20, 11:31
15 898.27 May 24, 18:29
16 902.57 May 29, 01:41
17 906.86 Jun 02, 08:38
18 911.16 Jun 06, 15:50
19 915.46 Jun 10, 23:02
20 919.75 Jun 15, 06:00
21 924.04 Jun 19, 12:57
22 928.35 Jun 23, 20:24
In addition to the above phasing, we have a preference for the visits to be spread over multiple binary orbital periods as described in the phase 1. Ideally the first and last visits would be separated by at least 4 binary orbit periods. However, implementation of this preference is flexible and should not override other scheduling considerations.