0 Assigned ID: 1098 ----- Attempting Submission 1 (Tue Feb 26 19:47:34 GMT 2013) ----- HST Phase I Proposal 1098 (plutogo21.apt) successfully submitted. ----- Attempting Submission 2 (Fri Mar 01 20:30:15 GMT 2013) ----- According to APT there is one visit that is slightly affected by a Moon constraint (better than we had it in Cycle 20). It should be fine unless we are unlucky with SAA avoidance. The schedule of observations is rather complicated to generate but there is some flexibility in case of difficulties. -691807808 ----- Attempting Submission 1 (Thu Jun 27 19:42:19 GMT 2013) ----- Pluto Satellite Orbits in Support of New Horizons We propose a sequence of observations that will significantly improve the orbit of P/2011 P1 and P/2012 P1 and provide useful improvements to the orbits of other satellites in the Pluto system. The orbit determination work for the newest satellite discoveries are 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 except for a slight exposure time adjustment for solar phase angle. 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 satellites, P/2011 P1 and P/2012 P1 (otherwise known as P4 and P5). 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. --------- Additional Comments ---------- 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 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 Default false false false false false SUPPORTED SOLAR SYSTEM DWARF-PLANET Pluto system STD=PLUTO Satellites range in brightness, faintest is about V=25 EARTH WFC3/UVIS Imaging No No F438W WFC3/UVIS Imaging No No F555W WFC3/UVIS Imaging No No F350LP POS-TARG DITHER 0.145 LINE false false 2 46.84 WFC3-UVIS-DITHER-LINE 1 false The scheduling data was generated by CASM 21.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 five major periods (Charon, Nix, P4, Hydra, and P5 orbital periods). All visits are given individual specific scheduling window to maintain this cadence and the windows provided are 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). The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. Once the visits have been scheduled, we need to check for contamination by bright stars (rare) and to make sure the faint satellites do not fall on diffraction spikes from Pluto or Charon. If they do, we will provide a small off-nominal roll to eliminate the problem. This is the same preocedure we used for our Cycle 20 observations. 1397411844000 257.3 (Tic-Visit :proposal-id 13315 :visit-id "01" :proposal-version -1 :trans-version "20130502" :date "26-Jun-2013 20:05:16.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 13315 :visit-id "01" :obset-id "01" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 13315 :visit-id "01" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2803 :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 The scheduling data was generated by CASM 21.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 five major periods (Charon, Nix, P4, Hydra, and P5 orbital periods). All visits are given individual specific scheduling window to maintain this cadence and the windows provided are 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). The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. Once the visits have been scheduled, we need to check for contamination by bright stars (rare) and to make sure the faint satellites do not fall on diffraction spikes from Pluto or Charon. If they do, we will provide a small off-nominal roll to eliminate the problem. This is the same preocedure we used for our Cycle 20 observations. 1398553129000 263.3 (Tic-Visit :proposal-id 13315 :visit-id "02" :proposal-version -1 :trans-version "20130502" :date "26-Jun-2013 20:05:53.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 13315 :visit-id "02" :obset-id "02" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 13315 :visit-id "02" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2803 :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 The scheduling data was generated by CASM 21.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 five major periods (Charon, Nix, P4, Hydra, and P5 orbital periods). All visits are given individual specific scheduling window to maintain this cadence and the windows provided are 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). The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. Once the visits have been scheduled, we need to check for contamination by bright stars (rare) and to make sure the faint satellites do not fall on diffraction spikes from Pluto or Charon. If they do, we will provide a small off-nominal roll to eliminate the problem. This is the same preocedure we used for our Cycle 20 observations. 1400463624000 258.9 (Tic-Visit :proposal-id 13315 :visit-id "03" :proposal-version -1 :trans-version "20130502" :date "26-Jun-2013 20:06:45.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 13315 :visit-id "03" :obset-id "03" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 13315 :visit-id "03" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2803 :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 The scheduling data was generated by CASM 21.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 five major periods (Charon, Nix, P4, Hydra, and P5 orbital periods). All visits are given individual specific scheduling window to maintain this cadence and the windows provided are 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). The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. Once the visits have been scheduled, we need to check for contamination by bright stars (rare) and to make sure the faint satellites do not fall on diffraction spikes from Pluto or Charon. If they do, we will provide a small off-nominal roll to eliminate the problem. This is the same preocedure we used for our Cycle 20 observations. 1401605499000 265.4 (Tic-Visit :proposal-id 13315 :visit-id "04" :proposal-version -1 :trans-version "20130502" :date "26-Jun-2013 20:07:41.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 13315 :visit-id "04" :obset-id "04" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 13315 :visit-id "04" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2803 :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 The scheduling data was generated by CASM 21.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 five major periods (Charon, Nix, P4, Hydra, and P5 orbital periods). All visits are given individual specific scheduling window to maintain this cadence and the windows provided are 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). The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. Once the visits have been scheduled, we need to check for contamination by bright stars (rare) and to make sure the faint satellites do not fall on diffraction spikes from Pluto or Charon. If they do, we will provide a small off-nominal roll to eliminate the problem. This is the same preocedure we used for our Cycle 20 observations. 1402321220000 260.8 (Tic-Visit :proposal-id 13315 :visit-id "05" :proposal-version -1 :trans-version "20130502" :date "26-Jun-2013 19:53: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 13315 :visit-id "05" :obset-id "05" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 13315 :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 The scheduling data was generated by CASM 21.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 five major periods (Charon, Nix, P4, Hydra, and P5 orbital periods). All visits are given individual specific scheduling window to maintain this cadence and the windows provided are 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). The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. Once the visits have been scheduled, we need to check for contamination by bright stars (rare) and to make sure the faint satellites do not fall on diffraction spikes from Pluto or Charon. If they do, we will provide a small off-nominal roll to eliminate the problem. This is the same preocedure we used for our Cycle 20 observations. 1402825837000 256.8 (Tic-Visit :proposal-id 13315 :visit-id "06" :proposal-version -1 :trans-version "20130502" :date "26-Jun-2013 19:53: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 64080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 13315 :visit-id "06" :obset-id "06" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 13315 :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 The scheduling data was generated by CASM 21.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 five major periods (Charon, Nix, P4, Hydra, and P5 orbital periods). All visits are given individual specific scheduling window to maintain this cadence and the windows provided are 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). The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. Once the visits have been scheduled, we need to check for contamination by bright stars (rare) and to make sure the faint satellites do not fall on diffraction spikes from Pluto or Charon. If they do, we will provide a small off-nominal roll to eliminate the problem. This is the same preocedure we used for our Cycle 20 observations. 1403561147000 254.2 (Tic-Visit :proposal-id 13315 :visit-id "07" :proposal-version -1 :trans-version "20130502" :date "26-Jun-2013 19:59: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 13315 :visit-id "07" :obset-id "07" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 13315 :visit-id "07" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2723 :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 The scheduling data was generated by CASM 21.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 five major periods (Charon, Nix, P4, Hydra, and P5 orbital periods). All visits are given individual specific scheduling window to maintain this cadence and the windows provided are 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). The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. Once the visits have been scheduled, we need to check for contamination by bright stars (rare) and to make sure the faint satellites do not fall on diffraction spikes from Pluto or Charon. If they do, we will provide a small off-nominal roll to eliminate the problem. This is the same preocedure we used for our Cycle 20 observations. 1404735294000 128.89999999999998 (Tic-Visit :proposal-id 13315 :visit-id "08" :proposal-version -1 :trans-version "20130502" :date "26-Jun-2013 20:00:43.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 13315 :visit-id "08" :obset-id "08" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 13315 :visit-id "08" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2723 :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 The scheduling data was generated by CASM 21.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 five major periods (Charon, Nix, P4, Hydra, and P5 orbital periods). All visits are given individual specific scheduling window to maintain this cadence and the windows provided are 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). The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. Once the visits have been scheduled, we need to check for contamination by bright stars (rare) and to make sure the faint satellites do not fall on diffraction spikes from Pluto or Charon. If they do, we will provide a small off-nominal roll to eliminate the problem. This is the same preocedure we used for our Cycle 20 observations. 1405354636000 110.39999999999998 (Tic-Visit :proposal-id 13315 :visit-id "09" :proposal-version -1 :trans-version "20130502" :date "26-Jun-2013 19: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 64080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 13315 :visit-id "09" :obset-id "09" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 13315 :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 The scheduling data was generated by CASM 21.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 five major periods (Charon, Nix, P4, Hydra, and P5 orbital periods). All visits are given individual specific scheduling window to maintain this cadence and the windows provided are 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). The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. Once the visits have been scheduled, we need to check for contamination by bright stars (rare) and to make sure the faint satellites do not fall on diffraction spikes from Pluto or Charon. If they do, we will provide a small off-nominal roll to eliminate the problem. This is the same preocedure we used for our Cycle 20 observations. 1406656700000 87.69999999999999 (Tic-Visit :proposal-id 13315 :visit-id "10" :proposal-version -1 :trans-version "20130502" :date "26-Jun-2013 19: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 64080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 13315 :visit-id "10" :obset-id "10" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 13315 :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 The scheduling data was generated by CASM 21.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 five major periods (Charon, Nix, P4, Hydra, and P5 orbital periods). All visits are given individual specific scheduling window to maintain this cadence and the windows provided are 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). The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. Once the visits have been scheduled, we need to check for contamination by bright stars (rare) and to make sure the faint satellites do not fall on diffraction spikes from Pluto or Charon. If they do, we will provide a small off-nominal roll to eliminate the problem. This is the same preocedure we used for our Cycle 20 observations. 1406966530000 89.80000000000001 (Tic-Visit :proposal-id 13315 :visit-id "11" :proposal-version -1 :trans-version "20130502" :date "26-Jun-2013 19:54: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 64080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 13315 :visit-id "11" :obset-id "11" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 13315 :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 The scheduling data was generated by CASM 21.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 five major periods (Charon, Nix, P4, Hydra, and P5 orbital periods). All visits are given individual specific scheduling window to maintain this cadence and the windows provided are 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). The visits are sorted by time but are pseudo-random in sub-earth longitude on each body. Once the visits have been scheduled, we need to check for contamination by bright stars (rare) and to make sure the faint satellites do not fall on diffraction spikes from Pluto or Charon. If they do, we will provide a small off-nominal roll to eliminate the problem. This is the same preocedure we used for our Cycle 20 observations. (Tic-Visit :proposal-id 13315 :visit-id "12" :proposal-version -1 :trans-version "20130502" :date "26-Jun-2013 20:08: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 13315 :visit-id "12" :obset-id "12" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 13315 :visit-id "12" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2803 :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