0 Assigned ID: 1668 ----- Attempting Submission 1 (Wed Mar 21 04:08:38 GMT 2018) ----- FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser We would like Visit 3 to be executed as soon as possible with Visit 4 some 2 days later and Visit 5 some 3 days after Visit 4. We do not want to use the FLASH, despite the warning. 984748131 ----- Attempting Submission 1 (Mon May 14 08:30:44 GMT 2018) ----- ----- Attempting Submission 2 (Wed May 16 10:54:15 GMT 2018) ----- ----- Attempting Submission 3 (Wed May 16 19:04:39 GMT 2018) ----- ----- Attempting Submission 4 (Tue Jun 19 04:11:48 GMT 2018) ----- There is a warning about the F814W exposure that the background doesn't reach the level high enough to mitigate CTE trailing losses and recommends adding a FLASH. We are okay with the FLASH warning comment. The Orbit of the Newly Discovered Satellite around the Dwarf Planet 2013 FY27 From our HST observations in January we discovered that dwarf planet 2013 FY27 has a satellite that is 2.8 mags fainter and 0.16 arcsecs from the primary. 2013 FY27 is the ninth intrinsically brightest trans-Neptunian object (TNO), and thus likely one of the largest. 2013 FY27 is extra interesting because its size is likely in the transition region of TNO structure. The largest few TNOs all have satellites, which show the largest TNOs have higher densities than the smaller TNOs. There are not many known intermediate sized TNOs like 2013 FY27 with satellites, of which 2013 FY27 is likely the largest and just at the beginning of the transition region from high to low density. This borderline intermediate to large sized TNO will allow us to probe the transition of high density to low density TNOs. 2013 FY27 is by far the largest TNO with a known satellite to not have the satellite's orbit known or soon to be known. We also just observed 2013 FY27 with ALMA, which will give us a size and albedo and thus allow us to obtain the mass and bulk density of 2013 FY27 if we know the satellite's orbit. Calculating the satellite's orbit requires 5 well separated observations. We currently have just the one discovery detection, and thus no motion of the satellite. We request 4 additional orbits with HST now so we can use our recent prior detection with the first few new detections to predict the optimal next time to observe it in April and May, which could save HST time. Also, the next HST GO proposal cycle does not allow small programs, which means our discovery detection will not be useful in predicting optimal HST observing times in the far future. We found a satellite around asteroid 2013 FY27 with HST images in Janauary 2018. We now want to observe this satellite at 4 different epochs in order to get the orbit of the satellite. This object is only up for the next month or so before being lost behind the Sun. We want to observe it ASAP with two different HST orbits scheduled about 2 days apart. We will then use those observations to predict when would be optimal to observe the satellite a third and fourth time, a few weeks later. If dynamic scheduling is not possible, we can schedule all 4 HST orbits now with seperations of about 2 days, 5 days and 12 days. This will not give us optimal coverage, but will likely be okay, but the satellite could be too close and thus confused with the primary if we don't have optimal dynamic scheduling. Solar System 6 false false false false false false false SUPPORTED SOLAR SYSTEM NO Need to observe 2013 FY27 with several images to monitor its newly found satellite. Need a few days between HST orbit visits in order to see the satellite move and thus calculate its orbit. DWARF-PLANET Asteroid 2013 FY27 TYPE=ASTEROID,A=58.87112529467599,E=0.3906163476853069,I=33.11838655782182,O=187.0531645959515,W=139.6951422033165,M=207.7450731986418,EQUINOX=J2000,EPOCH=25-AUG-2013:00:00:00,EpochTimeScale=TDB EARTH WFC3/UVIS Imaging No No F350LP WFC3/UVIS Imaging No No F606W WFC3/UVIS Imaging No No F814W WFC3/UVIS Imaging No No F350LP POS-TARG DITHER 0.173 LINE 0.112 false false 81.785 4 23.884 WFC3-UVIS-DITHER-BOX 1 false Using ephemeris for target 15460-01-2013FY27 ephemeris data for target 15460-01-2013FY27 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 18.120 to 19.152. ephemeris interval: 18.151 to 20.153 Timing link suitability includes constraints ([02 After 01 by 1.5 to 2.5 days]) The scheduling data was generated by CASM 26.0. CASM was run in Phase II mode. First visit of dwarf planet 2013 FY27. To do As Soon As Possible. 1527727775000 126.67097522164357 (Tic-Visit :proposal-id 15460 :visit-id "01" :proposal-version -1 :trans-version "20180409" :date "19-Jun-2018 00:09:52.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 1144784 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15460 :visit-id "01" :obset-id "01" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15460 :visit-id "01" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2859 :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 3202 :pcs-gap 0 ) true 1 0 Using ephemeris for target 15460-02-2013FY27 ephemeris data for target 15460-02-2013FY27 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 18.120 to 19.152. ephemeris interval: 18.151 to 20.153 Timing link suitability includes constraints ([02 After 01 by 1.5 to 2.5 days]) The scheduling data was generated by CASM 26.0. CASM was run in Phase II mode. Second visit of dwarf planet 2013 FY27. To do 1.5 to 2.5 days after first visit. 1527891215000 111.85058256768463 (Tic-Visit :proposal-id 15460 :visit-id "02" :proposal-version -1 :trans-version "20180409" :date "19-Jun-2018 00:09:54.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 54448 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15460 :visit-id "02" :obset-id "02" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15460 :visit-id "02" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2864 :al-overhead-at-end 0 :internal-dur-at-end 96 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3202 :pcs-gap 0 ) true 1 0 Using ephemeris for target 15460-03-2013FY27 ephemeris data for target 15460-03-2013FY27 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 18.120 to 19.152. ephemeris interval: 18.151 to 20.153 Timing link suitability includes constraints ([04 After 03 by 2.0 to 2.5 days]) The scheduling data was generated by CASM 26.0. CASM was run in Phase II mode. Third visit of dwarf planet 2013 FY27. To do ASAP. (Tic-Visit :proposal-id 15460 :visit-id "03" :proposal-version -1 :trans-version "20180409" :date "19-Jun-2018 00:09:55.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 54448 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15460 :visit-id "03" :obset-id "03" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15460 :visit-id "03" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2864 :al-overhead-at-end 0 :internal-dur-at-end 96 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3202 :pcs-gap 0 ) false 1 0 Using ephemeris for target 15460-04-2013FY27 ephemeris data for target 15460-04-2013FY27 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 18.120 to 19.152. ephemeris interval: 18.151 to 20.153 Timing link suitability includes constraints ([04 After 03 by 2.0 to 2.5 days] [51 After 04 by 3.0 to 3.5 days]) The scheduling data was generated by CASM 26.0. CASM was run in Phase II mode. Fourth visit of dwarf planet 2013 FY27. To do a few days after Visit 3. (Tic-Visit :proposal-id 15460 :visit-id "04" :proposal-version -1 :trans-version "20180409" :date "19-Jun-2018 00:09:56.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 1144784 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15460 :visit-id "04" :obset-id "04" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15460 :visit-id "04" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2859 :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 3202 :pcs-gap 0 ) false 1 0 Using ephemeris for target 15460-51-2013FY27 ephemeris data for target 15460-51-2013FY27 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 18.120 to 19.152. ephemeris interval: 18.151 to 20.153 Timing link suitability includes constraints ([51 After 04 by 3.0 to 3.5 days]) The scheduling data was generated by CASM 26.0. CASM was run in Phase II mode. Fifth visit, to do a few days after Visit 4. (Tic-Visit :proposal-id 15460 :visit-id "51" :proposal-version -1 :trans-version "20180409" :date "19-Jun-2018 00:09:57.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 1144784 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15460 :visit-id "51" :obset-id "51" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15460 :visit-id "51" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2859 :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 3202 :pcs-gap 0 ) false 1 0