Version 3; Final typo cleanup.1828054220Assigned ID: 959
----- Attempting Submission 1 (Fri Apr 07 21:56:56 GMT 2017) -----
HST Phase I Proposal 959 (Makemake_OR10_satellites.apt) successfully submitted.
Receipt: # 959-1
----- Attempting Submission 2 (Fri Apr 07 22:04:56 GMT 2017) -----
HST Phase I Proposal 959 (Makemake_OR10_satellites.apt) successfully submitted.
Receipt: # 959-2
----- Attempting Submission 3 (Fri Apr 07 22:42:09 GMT 2017) -----New timing constraints added. Observations renamed to match observation type. Total orbit request to spec.552112432----- Attempting Submission 1 (Thu Jul 20 17:07:53 GMT 2017) -----
HST Phase II Proposal 15207 (Mk2_PhaseII.apt) successfully submitted.
Receipt: # 15207-1
----- Attempting Submission 2 (Thu Jul 20 18:02:42 GMT 2017) -----
----- Attempting Submission 3 (Fri Sep 15 19:16:36 GMT 2017) -----
----- Attempting Submission 4 (Tue Sep 26 21:15:01 GMT 2017) -----
----- Attempting Submission 5 (Mon Nov 06 23:40:14 GMT 2017) -----
----- Attempting Submission 6 (Thu Jan 18 12:41:32 GMT 2018) -----
----- Attempting Submission 7 (Wed Feb 07 19:32:23 GMT 2018) -----
----- Attempting Submission 8 (Mon May 07 20:15:25 GMT 2018) -----
----- Attempting Submission 9 (Wed Oct 31 22:55:51 GMT 2018) -----The Moons of Kuiper Belt Dwarf Planets Makemake and 2007 OR10In two recent analyses of Hubble data, we discovered that both Makemake (the second-brightest trans-Neptunian Object behind only Pluto) and 2007 OR10 (the third largest TNO behind only Pluto and Eris) each have a faint satellite in orbit about them. With the addition of these satellites, all known TNOs with diameters unequivically larger than 1000 km are known to have moons; these are the only two for which the satellite orbits have not been characterized. The presence of these satellites provides the opportunity to accurately characterize bulk properties of Makemake and 2007 OR10 for the first time, including their masses and densities. This is a remarkable opportunity to study two of the largest dwarf planets in the solar system, completeing the census of bulk properties for TNOs with D>1000 km. Hubble has been instrumental in characterizing the satellites of the other TNO dwarf planets, as its union of sensitivity and angular resolution make it uniquely capable of studying these faint, high-contrast systems. We request an 18-orbit program to accurately measure the orbital properties of these satellites and to derive the masses and densities of Makemake and 2007 OR10. Both Makemake and 2007 OR10 are targets of JWST Guaranteed Time Observations, and this HST program is required to provide orbital phasing information that will ensure that the JWST MIRI observations can resolve the systems.All visits will follow the same basic pattern, with small variations depending on the choice of filters. This pattern will be to start the visit with several short F350LP exposures followed by several longer exposures in a second filter after which we will repeat the F350LP exposures to finish the visit. The bracketing F350LP exposures will provide a baseline to correct for any possible lightcurve effects and allow us to work on one wide-band filter (F606W or F814W) at a time in the visits.
MK2: The initial set will be guided by the large acceptable orbit volume from Parker
et al. (2016b) until there is sufficient new data to generate an preliminary orbit. Until these are done we cannot know with certainty if any given scheduled observation will detect MK2. According to our simulations, at least four out of seven visits are expected to be successful, we just cannot know which visits in advance. Also, success with this minimal number of orbits requires that they be scheduled over a short enough time range (~21 days) that the timing of all seven have to be decided at once and there can be no feedback to improve our odds. The successful observations will then be sufficient to get an initial orbit that will permit us to predict the location of MK2 during the rest of Cycle 25 and 26. After the first group are executed, the results will be collated into an orbit model. From that orbit will determine the most effective time to schedule the remaining visits for maximum orbit improvement in the remainder of Cycle 25 and/or Cycle 26. If the satellite is not recovered in these initial seven orbits, the subsequent four orbits can be re-allocated to other programs.
OR2: The discovery observations of OR2 do not suggest an orbit that spends a large fraction of its time at separations from the primary that would preclude detection. Thus, only three initial recovery observations are planned for OR2, which combined with the previous measurements will inform the four characterization orbits. If the satellite is not recovered in these initial three orbits, the subsequent four orbits can be re-allocated to other programs.Solar System0falsefalsefalsefalsetruefalsefalseSUPPORTEDSOLAR SYSTEMNODWARF-PLANETDwarf planet Makemake and satelliteSTD=MAKEMAKESatellite Mk2 V ~ 24.7EARTHSOLAR SYSTEMNODWARF-PLANETDwarf planet 2007 OR10 and its satellite.TYPE=ASTEROID,A=66.84156896375929,E=0.5045718566367412,I=30.9050913888484,O=336.8211090973072,W=206.618255615117,M=103.4692469440252,EQUINOX=J2000,EPOCH=13-JAN-2014:00:00:00,EpochTimeScale=TDBSatellite OR10b V ~25.5EARTHWFC3/UVISImagingNoNoF350LPWFC3/UVISImagingNoNoF814WWFC3/UVISImagingNoNoF350LPWFC3/UVISImagingNoNoF606WWFC3/UVISImagingNoNoF350LPWFC3/UVISImagingNoNoF814WWFC3/UVISImagingNoNoF350LPWFC3/UVISImagingNoNoF606WPOS-TARGDITHER0.173LINE0.112falsefalse81.785423.884WFC3-UVIS-DITHER-BOX1falseUsing ephemeris for target 15500-01-MAKEMAKEephemeris data for target 15500-01-MAKEMAKE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 18.213 to 20.090. ephemeris interval: 18.273 to 20.275Timing link suitability includes constraints ([02 After 01 by 8.5 to 9.5 days] [03 After 01 by 17.5 to 18.5 days])The scheduling data was generated by CASM 26.0.CASM was run in Phase II mode./private/var/folders/7m/rd0g0r7j33x551p1627vd7280000gn/T/OPVisit626494385753001319.xmlThis is a time-sensitive program measuring the orbital properties of Makemake's satellite. There are a series of possible start dates in 2019, and after Makemake Nail 01 executes, Makemake Nail 02 and Makemake Nail 03 must execute shortly thereafter with relatively tight timing constraints.(Tic-Visit
:proposal-id 15500
:visit-id "01"
:proposal-version -1
:trans-version "20180409"
:date "31-Oct-2018 16:54:02.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 91536
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15500
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15500
:visit-id "01"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2570
:al-overhead-at-end 0
:internal-dur-at-end 137
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)true10Using ephemeris for target 15500-02-MAKEMAKEephemeris data for target 15500-02-MAKEMAKE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 18.213 to 20.090. ephemeris interval: 18.273 to 20.275Timing link suitability includes constraints ([02 After 01 by 8.5 to 9.5 days])The scheduling data was generated by CASM 26.0.CASM was run in Phase II mode./private/var/folders/7m/rd0g0r7j33x551p1627vd7280000gn/T/OPVisit2197083050184679353.xml(Tic-Visit
:proposal-id 15500
:visit-id "02"
:proposal-version -1
:trans-version "20180409"
:date "31-Oct-2018 16:54:04.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 73232
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15500
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15500
:visit-id "02"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2486
:al-overhead-at-end 0
:internal-dur-at-end 117
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)true10Using ephemeris for target 15500-03-MAKEMAKEephemeris data for target 15500-03-MAKEMAKE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 18.213 to 20.090. ephemeris interval: 18.273 to 20.275Timing link suitability includes constraints ([03 After 01 by 17.5 to 18.5 days])The scheduling data was generated by CASM 26.0.CASM was run in Phase II mode./private/var/folders/7m/rd0g0r7j33x551p1627vd7280000gn/T/OPVisit3781345733764392572.xml(Tic-Visit
:proposal-id 15500
:visit-id "03"
:proposal-version -1
:trans-version "20180409"
:date "31-Oct-2018 16:54:05.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 73232
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15500
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15500
:visit-id "03"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2486
:al-overhead-at-end 0
:internal-dur-at-end 117
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)true10Using ephemeris for target 15500-04-2007OR10ephemeris data for target 15500-04-2007OR10 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 18.213 to 20.090. ephemeris interval: 18.273 to 20.275Timing link suitability includes constraints ([05 After 04 by 6.0 to 7.0 days] [06 After 04 by 18.5 to 19.5 days])The scheduling data was generated by CASM 26.0.CASM was run in Phase II mode./private/var/folders/7m/rd0g0r7j33x551p1627vd7280000gn/T/OPVisit170040578632948756.xmlThis is a time-sensitive program measuring the orbital properties of 2007 OR10's satellite. There are a series of possible start dates in 2019, and after OR10 Nail 01 executes, OR10 Nail 02 and OR10 Nail 03 must execute shortly thereafter with relatively tight timing constraints.(Tic-Visit
:proposal-id 15500
:visit-id "04"
:proposal-version -1
:trans-version "20180409"
:date "31-Oct-2018 16:54: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 73232
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15500
:visit-id "04"
:obset-id "04"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15500
:visit-id "04"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2634
:al-overhead-at-end 0
:internal-dur-at-end 117
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)true10Using ephemeris for target 15500-05-2007OR10ephemeris data for target 15500-05-2007OR10 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 18.213 to 20.090. ephemeris interval: 18.273 to 20.275Timing link suitability includes constraints ([05 After 04 by 6.0 to 7.0 days])The scheduling data was generated by CASM 26.0.CASM was run in Phase II mode./private/var/folders/7m/rd0g0r7j33x551p1627vd7280000gn/T/OPVisit3908794173295389276.xml(Tic-Visit
:proposal-id 15500
:visit-id "05"
:proposal-version -1
:trans-version "20180409"
:date "31-Oct-2018 16:54:07.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 54928
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15500
:visit-id "05"
:obset-id "05"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15500
:visit-id "05"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2582
:al-overhead-at-end 0
:internal-dur-at-end 97
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)true10Using ephemeris for target 15500-06-2007OR10ephemeris data for target 15500-06-2007OR10 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 18.213 to 20.090. ephemeris interval: 18.273 to 20.275Timing link suitability includes constraints ([06 After 04 by 18.5 to 19.5 days])The scheduling data was generated by CASM 26.0.CASM was run in Phase II mode./private/var/folders/7m/rd0g0r7j33x551p1627vd7280000gn/T/OPVisit4007939940264463053.xml(Tic-Visit
:proposal-id 15500
:visit-id "06"
:proposal-version -1
:trans-version "20180409"
:date "31-Oct-2018 16:54: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 73232
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15500
:visit-id "06"
:obset-id "06"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15500
:visit-id "06"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2634
:al-overhead-at-end 0
:internal-dur-at-end 117
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)true10