We propose a sequence of observations that will significantly improve the orbit of P/2011 P1 and provide useful improvements to the orbits of other satellites in the Pluto system. The orbit determination work for the newest satellite discovery is critically needed so that New Horizons can know where to point its instruments at close approach. These data will also be useful for improved mass constraints on the outer satellites as well as refining our knowledge of the photometric properties of all objects in the Pluto system. In particular, lightcurve and color evolution will be monitored by these observations for use in constraining models of seasonal evolution on Pluto. Each visit is identically constructed. The timing for all visits is designed to provide nearly uniform astrometric coverage as a function of the orbital longitude of the satellites in the Pluto system. Within each visit there are a series of short, medium, and long duration exposures designed to cover the large dynamic range of the Pluto system and to provide astrometric ties to well-understood wavelengths. The shortest exposures prevent saturation of Pluto and occur at the start of the visit. The longest duration exposure is set to give adequate signal on the faintest satellite, P/2011 P1 (otherwise known as P4). The exposure time is set as a compromise between per-frame photometric depth and minimization of lost pixels due to over-exposure from Pluto, Charon and field stars in the very crowded field Pluto is presently moving through. The medium exposure at the end serves to bridge the gap in brightness range between these two extremes while still providing useful detections of Nix and Hydra. The scheduling windows are set to ensure an SAA-free period but there will be more than one possible orbit that is useable. Once the STScI proposal scheduling staff can provide actual times for the scheduled orbits we can perform checks that will help to avoid orbits compromised by bright star contamination in our FOV as well as determine if we need for off-nominal roll tweaks to prevent the faint outer satellites from falling on diffraction spikes of Pluto or Charon. This can be done as soon as the observations are assigned a specific visibility window within the much coarser time-constraints imposed by the proposal. The dithering pattern we use is a combination of the standard line pattern and pos-targ values that help fill the unit pixel while providing some slighly larger dithering as well. The entire pattern is biased by (+4.0, +0.3) to move the system away from the bad columns near the center of the sub-array. If the location of default pointing within this sub-array changes, we will have to update all of the pos-targ values. SOLAR SYSTEM 12 false false 0.0 0.0 false false false SUPPORTED SOLAR SYSTEM PLANET Pluto STD=PLUTO EARTH WFC3/UVIS Imaging No No F350LP WFC3/UVIS Imaging No No F438W WFC3/UVIS Imaging No No F555W POS-TARG DITHER 0.145 LINE false false 2 46.84 WFC3-UVIS-DITHER-LINE 2 false Timing link suitability includes constraints ([02 After 01 by 26.9 to 27.4 days] [03 After 01 by 30.6 to 31.1 days] [04 After 01 by 38.6 to 39.1 days] [05 After 01 by 47.7 to 48.2 days] [06 After 01 by 61.5 to 62.0 days] [07 After 01 by 69.5 to 70.0 days] [08 After 01 by 72.7 to 73.2 days] [09 After 01 by 81.2 to 81.7 days] [10 After 01 by 91.3 to 91.8 days] [11 After 01 by 112.1 to 112.6 days] [12 After 01 by 134.9 to 135.4 days]) The scheduling data was generated by CASM 20.2. CASM was run in Phase II mode. The set of visits provided is a linked set of observations to provide a very specific observational cadence of the Pluto system. It is specially chosen to optimize the coverage of the system given the three major periods (Charon, Nix, and Hydra orbital periods). Visits 2-12 are linked to visit 1 rather than to each other so that the entire pattern is not destroyed by a compromise to any single visit. The scheduling window is provided at 12 hours long (+/- 6 hours from nominal) to make the program more easily schedulable. The actual length of this window may not be critical (though we'd rather not extend it much longer than this without considerable thought). Visit 6 has a special timing contraint, see comments there. The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. 1367370737000 263.0 (Tic-Visit :proposal-id 12897 :visit-id "01" :proposal-version -1 :trans-version "20120604" :date "10-Jul-2012 14:22: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 64080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12897 :visit-id "01" :obset-id "01" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12897 :visit-id "01" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2763 :al-overhead-at-end 0 :internal-dur-at-end 107 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3229 :pcs-gap 0 ) false 1 0 Timing link suitability includes constraints ([02 After 01 by 26.9 to 27.4 days]) The scheduling data was generated by CASM 20.2. CASM was run in Phase II mode. The set of visits provided is a linked set of observations to provide a very specific observational cadence of the Pluto system. It is specially chosen to optimize the coverage of the system given the three major periods (Charon, Nix, and Hydra orbital periods). Visits 2-12 are linked to visit 1 rather than to each other so that the entire pattern is not destroyed by a compromise to any single visit. The scheduling window is provided at 12 hours long (+/- 6 hours from nominal) to make the program more easily schedulable. The actual length of this window may not be critical (though we'd rather not extend it much longer than this without considerable thought). Visit 6 has a special timing contraint, see comments there. The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. 1369730286000 267.0 (Tic-Visit :proposal-id 12897 :visit-id "02" :proposal-version -1 :trans-version "20120604" :date "10-Jul-2012 14:22:50.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 64080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12897 :visit-id "02" :obset-id "02" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12897 :visit-id "02" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2763 :al-overhead-at-end 0 :internal-dur-at-end 107 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3229 :pcs-gap 0 ) false 1 0 Timing link suitability includes constraints ([03 After 01 by 30.6 to 31.1 days]) The scheduling data was generated by CASM 20.2. CASM was run in Phase II mode. The set of visits provided is a linked set of observations to provide a very specific observational cadence of the Pluto system. It is specially chosen to optimize the coverage of the system given the three major periods (Charon, Nix, and Hydra orbital periods). Visits 2-12 are linked to visit 1 rather than to each other so that the entire pattern is not destroyed by a compromise to any single visit. The scheduling window is provided at 12 hours long (+/- 6 hours from nominal) to make the program more easily schedulable. The actual length of this window may not be critical (though we'd rather not extend it much longer than this without considerable thought). Visit 6 has a special timing contraint, see comments there. The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. 1370034521000 259.0 (Tic-Visit :proposal-id 12897 :visit-id "03" :proposal-version -1 :trans-version "20120604" :date "10-Jul-2012 14:23: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 64080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12897 :visit-id "03" :obset-id "03" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12897 :visit-id "03" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2763 :al-overhead-at-end 0 :internal-dur-at-end 107 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3229 :pcs-gap 0 ) false 1 0 Timing link suitability includes constraints ([04 After 01 by 38.6 to 39.1 days]) The scheduling data was generated by CASM 20.2. CASM was run in Phase II mode. The set of visits provided is a linked set of observations to provide a very specific observational cadence of the Pluto system. It is specially chosen to optimize the coverage of the system given the three major periods (Charon, Nix, and Hydra orbital periods). Visits 2-12 are linked to visit 1 rather than to each other so that the entire pattern is not destroyed by a compromise to any single visit. The scheduling window is provided at 12 hours long (+/- 6 hours from nominal) to make the program more easily schedulable. The actual length of this window may not be critical (though we'd rather not extend it much longer than this without considerable thought). Visit 6 has a special timing contraint, see comments there. The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. 1370717698000 260.0 (Tic-Visit :proposal-id 12897 :visit-id "04" :proposal-version -1 :trans-version "20120604" :date "10-Jul-2012 14:23: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 64080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12897 :visit-id "04" :obset-id "04" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12897 :visit-id "04" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2763 :al-overhead-at-end 0 :internal-dur-at-end 107 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3229 :pcs-gap 0 ) false 1 0 Timing link suitability includes constraints ([05 After 01 by 47.7 to 48.2 days]) The scheduling data was generated by CASM 20.2. CASM was run in Phase II mode. The set of visits provided is a linked set of observations to provide a very specific observational cadence of the Pluto system. It is specially chosen to optimize the coverage of the system given the three major periods (Charon, Nix, and Hydra orbital periods). Visits 2-12 are linked to visit 1 rather than to each other so that the entire pattern is not destroyed by a compromise to any single visit. The scheduling window is provided at 12 hours long (+/- 6 hours from nominal) to make the program more easily schedulable. The actual length of this window may not be critical (though we'd rather not extend it much longer than this without considerable thought). Visit 6 has a special timing contraint, see comments there. The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. 1371505250000 252.0 (Tic-Visit :proposal-id 12897 :visit-id "05" :proposal-version -1 :trans-version "20120604" :date "10-Jul-2012 14:23: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 64080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12897 :visit-id "05" :obset-id "05" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12897 :visit-id "05" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2763 :al-overhead-at-end 0 :internal-dur-at-end 107 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3229 :pcs-gap 0 ) false 1 0 Timing link suitability includes constraints ([06 After 01 by 61.5 to 62.0 days]) The scheduling data was generated by CASM 20.2. CASM was run in Phase II mode. The set of visits provided is a linked set of observations to provide a very specific observational cadence of the Pluto system. It is specially chosen to optimize the coverage of the system given the three major periods (Charon, Nix, and Hydra orbital periods). Visits 2-12 are linked to visit 1 rather than to each other so that the entire pattern is not destroyed by a compromise to any single visit. The scheduling window is provided at 12 hours long (+/- 6 hours from nominal) to make the program more easily schedulable. The actual length of this window may not be critical (though we'd rather not extend it much longer than this without considerable thought). Visit 6 has a special timing contraint, see comments there. The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. 1372698681000 177.0 (Tic-Visit :proposal-id 12897 :visit-id "06" :proposal-version -1 :trans-version "20120604" :date "10-Jul-2012 14:23:48.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 64080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12897 :visit-id "06" :obset-id "06" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12897 :visit-id "06" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2763 :al-overhead-at-end 0 :internal-dur-at-end 107 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3229 :pcs-gap 0 ) false 1 0 Timing link suitability includes constraints ([07 After 01 by 69.5 to 70.0 days]) The scheduling data was generated by CASM 20.2. CASM was run in Phase II mode. The set of visits provided is a linked set of observations to provide a very specific observational cadence of the Pluto system. It is specially chosen to optimize the coverage of the system given the three major periods (Charon, Nix, and Hydra orbital periods). Visits 2-12 are linked to visit 1 rather than to each other so that the entire pattern is not destroyed by a compromise to any single visit. The scheduling window is provided at 12 hours long (+/- 6 hours from nominal) to make the program more easily schedulable. The actual length of this window may not be critical (though we'd rather not extend it much longer than this without considerable thought). Visit 6 has a special timing contraint, see comments there. The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. 1373387796000 108.0 (Tic-Visit :proposal-id 12897 :visit-id "07" :proposal-version -1 :trans-version "20120604" :date "10-Jul-2012 14:24:01.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 64080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12897 :visit-id "07" :obset-id "07" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12897 :visit-id "07" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2763 :al-overhead-at-end 0 :internal-dur-at-end 107 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3229 :pcs-gap 0 ) false 1 0 Timing link suitability includes constraints ([08 After 01 by 72.7 to 73.2 days]) The scheduling data was generated by CASM 20.2. CASM was run in Phase II mode. The set of visits provided is a linked set of observations to provide a very specific observational cadence of the Pluto system. It is specially chosen to optimize the coverage of the system given the three major periods (Charon, Nix, and Hydra orbital periods). Visits 2-12 are linked to visit 1 rather than to each other so that the entire pattern is not destroyed by a compromise to any single visit. The scheduling window is provided at 12 hours long (+/- 6 hours from nominal) to make the program more easily schedulable. The actual length of this window may not be critical (though we'd rather not extend it much longer than this without considerable thought). Visit 6 has a special timing contraint, see comments there. The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. 1373669092000 108.0 (Tic-Visit :proposal-id 12897 :visit-id "08" :proposal-version -1 :trans-version "20120604" :date "10-Jul-2012 14:24:15.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 64080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12897 :visit-id "08" :obset-id "08" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12897 :visit-id "08" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2763 :al-overhead-at-end 0 :internal-dur-at-end 107 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3229 :pcs-gap 0 ) false 1 0 Timing link suitability includes constraints ([09 After 01 by 81.2 to 81.7 days]) The scheduling data was generated by CASM 20.2. CASM was run in Phase II mode. The set of visits provided is a linked set of observations to provide a very specific observational cadence of the Pluto system. It is specially chosen to optimize the coverage of the system given the three major periods (Charon, Nix, and Hydra orbital periods). Visits 2-12 are linked to visit 1 rather than to each other so that the entire pattern is not destroyed by a compromise to any single visit. The scheduling window is provided at 12 hours long (+/- 6 hours from nominal) to make the program more easily schedulable. The actual length of this window may not be critical (though we'd rather not extend it much longer than this without considerable thought). Visit 6 has a special timing contraint, see comments there. The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. 1374464048000 94.0 (Tic-Visit :proposal-id 12897 :visit-id "09" :proposal-version -1 :trans-version "20120604" :date "10-Jul-2012 14:24: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 64080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12897 :visit-id "09" :obset-id "09" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12897 :visit-id "09" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2763 :al-overhead-at-end 0 :internal-dur-at-end 107 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3229 :pcs-gap 0 ) false 1 0 Timing link suitability includes constraints ([10 After 01 by 91.3 to 91.8 days]) The scheduling data was generated by CASM 20.2. CASM was run in Phase II mode. The set of visits provided is a linked set of observations to provide a very specific observational cadence of the Pluto system. It is specially chosen to optimize the coverage of the system given the three major periods (Charon, Nix, and Hydra orbital periods). Visits 2-12 are linked to visit 1 rather than to each other so that the entire pattern is not destroyed by a compromise to any single visit. The scheduling window is provided at 12 hours long (+/- 6 hours from nominal) to make the program more easily schedulable. The actual length of this window may not be critical (though we'd rather not extend it much longer than this without considerable thought). Visit 6 has a special timing contraint, see comments there. The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. (Tic-Visit :proposal-id 12897 :visit-id "10" :proposal-version -1 :trans-version "20120604" :date "10-Jul-2012 14:24:40.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 64080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12897 :visit-id "10" :obset-id "10" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12897 :visit-id "10" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2763 :al-overhead-at-end 0 :internal-dur-at-end 107 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3229 :pcs-gap 0 ) false 1 0 Timing link suitability includes constraints ([11 After 01 by 112.1 to 112.6 days]) The scheduling data was generated by CASM 20.2. CASM was run in Phase II mode. The set of visits provided is a linked set of observations to provide a very specific observational cadence of the Pluto system. It is specially chosen to optimize the coverage of the system given the three major periods (Charon, Nix, and Hydra orbital periods). Visits 2-12 are linked to visit 1 rather than to each other so that the entire pattern is not destroyed by a compromise to any single visit. The scheduling window is provided at 12 hours long (+/- 6 hours from nominal) to make the program more easily schedulable. The actual length of this window may not be critical (though we'd rather not extend it much longer than this without considerable thought). Visit 6 has a special timing contraint, see comments there. The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. (Tic-Visit :proposal-id 12897 :visit-id "11" :proposal-version -1 :trans-version "20120604" :date "10-Jul-2012 14:24: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 64080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12897 :visit-id "11" :obset-id "11" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12897 :visit-id "11" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2763 :al-overhead-at-end 0 :internal-dur-at-end 107 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3229 :pcs-gap 0 ) false 1 0 Timing link suitability includes constraints ([12 After 01 by 134.9 to 135.4 days]) The scheduling data was generated by CASM 20.2. CASM was run in Phase II mode. The set of visits provided is a linked set of observations to provide a very specific observational cadence of the Pluto system. It is specially chosen to optimize the coverage of the system given the three major periods (Charon, Nix, and Hydra orbital periods). Visits 2-12 are linked to visit 1 rather than to each other so that the entire pattern is not destroyed by a compromise to any single visit. The scheduling window is provided at 12 hours long (+/- 6 hours from nominal) to make the program more easily schedulable. The actual length of this window may not be critical (though we'd rather not extend it much longer than this without considerable thought). Visit 6 has a special timing contraint, see comments there. The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. (Tic-Visit :proposal-id 12897 :visit-id "12" :proposal-version -1 :trans-version "20120604" :date "10-Jul-2012 14:25: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 64080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 12897 :visit-id "12" :obset-id "12" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 12897 :visit-id "12" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2763 :al-overhead-at-end 0 :internal-dur-at-end 107 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3229 :pcs-gap 0 ) false 1 0