0 Assigned ID: 3631 ----- Attempting Submission 1 (Fri Mar 25 22:15:18 GMT 2022) ----- HST Phase I Proposal 3631 successfully submitted. Receipt: # 3631-1 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 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 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 POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. 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 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 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 POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. 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 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 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 POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. 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 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 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 POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. 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 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 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 POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. 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 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 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 POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. 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 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 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 POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. 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 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 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 POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. 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 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 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 POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. 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 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 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 POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. 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 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 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 POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. 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 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 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 POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser 0 ----- Attempting Submission 1 (Thu Jul 07 19:03:04 GMT 2022) ----- ----- Attempting Submission 2 (Wed Oct 12 15:40:17 GMT 2022) ----- FLASH is not required on these observations, based on past imaging performance of Uranus and Neptune. the Same POS-TARG dither pattern is used by OPAL Observing the Ice Giants with Hubble WFC3 to Enhance Cycle 1 James Webb Space Telescope Data The JWST will provide exceptional near- and mid-infrared spectral coverage of the Ice Giants via guaranteed time observations in Cycle 1 (Programs 1248 and 1249), capturing new, critical information on their atmospheric temperatures, their chemical structures, and the flow of energy between their cloud-forming weather layer and their middle and upper atmospheres. However, the JWST data cannot be interpreted reliably without context. JWST observations provide only brief snapshots of these two highly dynamic worlds, requiring temporal context to understand how the atmospheres have varied with time, and spatial context to understand the distribution of meteorological features during the JWST observations. The HST campaign offers a critical extension of spectral coverage into the visible that will be capable of detecting important features like dark spots and their bright cloud companions. HST is the only facility capable of the high-resolution at visible- specifically blue- wavelengths. We therefore propose a HST GO campaign using the WFC3 instrument in UVIS observing mode to provide complementary, comparative, and synergistic science alongside the JWST Cycle 1 Guaranteed-Time Observations (GTO) of these distant, cold, and exceptional worlds. From a strategic perspective, as the international planetary community looks ahead to future NASA and ESA missions to the ice giants, this combined Hubble and JWST campaign will pave the way for more robust understanding of these distant worlds. Four orbits for each visit for each planet. To match the JWST observing windows that occur in Cycle 30, we request 1 visit for Uranus and 2 for Neptune, totaling 12 orbits. With 16 to 17-hr rotation periods, each orbit should be separated by ~4 hours to give global coverage. The filters were chosen to match these objectives and fit within an orbit. As Uranus and Neptune are small targets, we can use subarrays to minimize the readout time and maximize the number of images. We will exclusively use the C512C subarray, which also minimizes charge transfer losses due to its proximity to the readout amplifiers. Additionally, these are faint targets and will be dominated by pixel instability, so we will dither the observations to lessen this effect. Dr. Naomi Rowe-Gurney, the PI of this proposal, is a postdoctoral researcher and expert in mid-infrared space telescope data reduction and analysis for the intended targets, the Ice Giants. Dr. Rowe-Gurney is involved directly in the JWST GTO program that we wish to support with this proposal. Dr. Amy Simon is the PI for the Hubble 2020: Outer Planets Atmospheres Legacy (OPAL) Program and therefore has expertise in HST data reduction for WFC3, the instrument being used in these proposed observations. Dr. Simon is also an expert in giant planet atmospheres and has many publications that use data from HST/WFC3. Dr. Michael Roman is an expert in mid-infrared spectroscopy and imaging of the Ice Giants and works with ground-based instruments in going from raw data to publication. Dr. Henrik Melin is an expert in near-IR UV and visible studies of the aurora and upper atmosphere of the giant planets. Dr. Melin has many years of experience in observing the Ice Giants and using data in the same ranges as WFC3. Dr. Heidi Hammel is a JWST Interdisciplinary Scientist that has extensive experience with Hubble observations of the Solar System and with observing and studying the Ice Giants specifically. Dr. Stefanie Milam is the JWST Deputy Project Scientist for Planetary Science. Prof. Leigh Fletcher is the PI for the JWST GTO Ice Giant observing programs. Prof. Fletcher is an expert in planetary atmospheres and has investigated the Ice Giants with multiple different telescopes on the ground and in space using many different wavelength ranges. Dr. Danna Qasim works in the Astrochemistry Laboratory studying ices with JWST. Dr. Rowe-Gurney and Dr. Simon will have the primary roles of reducing the data with the help of Dr. Roman and Dr. Melin. This data will be made available to the entire JWST GTO team via Dr. Rowe-Gurney, Prof. Fletcher, Dr. Hammel and Dr. Milam who all have integral roles in the Solar System GTO program. Dr. Qasim is an ice chemistry advisor for the team. Solar System Astronomy 6 false false false false false false false SUPPORTED SOLAR SYSTEM PLANET PLANET URANUS STD=URANUS EARTH SOLAR SYSTEM PLANET PLANET NEPTUNE STD=NEPTUNE EARTH WFC3/UVIS Imaging No No F845M WFC3/UVIS Imaging No No F467M WFC3/UVIS Imaging No No F547M WFC3/UVIS Imaging No No F657N WFC3/UVIS Imaging No No F763M WFC3/UVIS Imaging No No F845M WFC3/UVIS Imaging No No F487N WFC3/UVIS Imaging No No F657N WFC3/UVIS Imaging No No F763M WFC3/UVIS Imaging No No FQ727N WFC3/UVIS Imaging No No FQ727N WFC3/UVIS Imaging No No FQ619N WFC3/UVIS Imaging No No FQ619N WFC3/UVIS Imaging No No F845M WFC3/UVIS Imaging No No F467M WFC3/UVIS Imaging No No F547M WFC3/UVIS Imaging No No F657N WFC3/UVIS Imaging No No F763M WFC3/UVIS Imaging No No F845M WFC3/UVIS Imaging No No F487N WFC3/UVIS Imaging No No F657N WFC3/UVIS Imaging No No F763M WFC3/UVIS Imaging No No FQ727N WFC3/UVIS Imaging No No FQ727N WFC3/UVIS Imaging No No FQ619N WFC3/UVIS Imaging No No FQ619N WFC3/UVIS Imaging No No F845M WFC3/UVIS Imaging No No F467M WFC3/UVIS Imaging No No F547M WFC3/UVIS Imaging No No F657N WFC3/UVIS Imaging No No F763M WFC3/UVIS Imaging No No F845M WFC3/UVIS Imaging No No F487N WFC3/UVIS Imaging No No F657N WFC3/UVIS Imaging No No F763M WFC3/UVIS Imaging No No FQ727N WFC3/UVIS Imaging No No FQ727N WFC3/UVIS Imaging No No FQ619N WFC3/UVIS Imaging No No FQ619N POS-TARG DITHER 0.145 LINE false false 2 46.84 WFC3-UVIS-DITHER-LINE 1 false POS-TARG DITHER 0.725 LINE false false 2 46.84 WFC3-UVIS-DITHER-LINE 2 false Using ephemeris for target 17187-01-URANUS ephemeris data for target 17187-01-URANUS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.273 to 24.275 Timing link suitability includes constraints ([02 After 01 by 0.1 to 0.2 days]) The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. /private/var/folders/58/m3km1yk15rgcq0hfq011tfk80002ks/T/OPVisit17026827418486077672.xml Uranus in window 22-DEC-2022 to 08-FEB-2023 as close as possible to the JWST observations in program 1248. 4 orbits. Visit 4 after visit 1 by between 9 and 11 orbits. All visits spaced out as evenly as possible within the 17 hour 14 minute Uranian day, with ideally 2- or 3-orbit gaps between them (ideal spacing is 4 hours). 1-orbit gaps are too close. Impingement into SAA is OK if the above timing gaps cannot prevent it. We can tolerate gyro bias updates to ease the contiguous orbit constraints, and will work with our program contacts to fit them in. 3-gyro mode may be necessary as this is a moving target. (Tic-Visit :proposal-id 17187 :visit-id "01" :proposal-version -1 :trans-version "20220630" :date "22-Oct-2022 11:09:00.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 254848 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17187 :visit-id "01" :obset-id "01" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17187 :visit-id "01" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2370 :al-overhead-at-end 0 :internal-dur-at-end 315 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2782 :pcs-gap 0 ) true 1 0 Using ephemeris for target 17187-02-URANUS ephemeris data for target 17187-02-URANUS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.273 to 24.275 Timing link suitability includes constraints ([02 After 01 by 0.1 to 0.2 days] [03 After 02 by 0.1 to 0.2 days]) The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. /private/var/folders/58/m3km1yk15rgcq0hfq011tfk80002ks/T/OPVisit7169775663896448155.xml Uranus in window 22-DEC-2022 to 08-FEB-2023 as close as possible to the JWST observations in program 1248. 4 orbits. Visit 4 after visit 1 by between 9 and 11 orbits. All visits spaced out as evenly as possible within the 17 hour 14 minute Uranian day, with ideally 2- or 3-orbit gaps between them (ideal spacing is 4 hours). 1-orbit gaps are too close. Impingement into SAA is OK if the above timing gaps cannot prevent it. We can tolerate gyro bias updates to ease the contiguous orbit constraints, and will work with our program contacts to fit them in. 3-gyro mode may be necessary as this is a moving target. (Tic-Visit :proposal-id 17187 :visit-id "02" :proposal-version -1 :trans-version "20220630" :date "22-Oct-2022 11:09: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 254848 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17187 :visit-id "02" :obset-id "02" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17187 :visit-id "02" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2370 :al-overhead-at-end 0 :internal-dur-at-end 315 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2782 :pcs-gap 0 ) true 1 0 Using ephemeris for target 17187-03-URANUS ephemeris data for target 17187-03-URANUS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.273 to 24.275 Timing link suitability includes constraints ([03 After 02 by 0.1 to 0.2 days] [04 After 03 by 0.1 to 0.2 days]) The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. /private/var/folders/58/m3km1yk15rgcq0hfq011tfk80002ks/T/OPVisit3543179026441757331.xml Uranus in window 22-DEC-2022 to 08-FEB-2023 as close as possible to the JWST observations in program 1248. 4 orbits. Visit 4 after visit 1 by between 9 and 11 orbits. All visits spaced out as evenly as possible within the 17 hour 14 minute Uranian day, with ideally 2- or 3-orbit gaps between them (ideal spacing is 4 hours). 1-orbit gaps are too close. Impingement into SAA is OK if the above timing gaps cannot prevent it. We can tolerate gyro bias updates to ease the contiguous orbit constraints, and will work with our program contacts to fit them in. 3-gyro mode may be necessary as this is a moving target. (Tic-Visit :proposal-id 17187 :visit-id "03" :proposal-version -1 :trans-version "20220630" :date "22-Oct-2022 11:09: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 254848 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17187 :visit-id "03" :obset-id "03" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17187 :visit-id "03" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2370 :al-overhead-at-end 0 :internal-dur-at-end 315 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2782 :pcs-gap 0 ) true 1 0 Using ephemeris for target 17187-04-URANUS ephemeris data for target 17187-04-URANUS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.273 to 24.275 Timing link suitability includes constraints ([04 After 03 by 0.1 to 0.2 days]) The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. /private/var/folders/58/m3km1yk15rgcq0hfq011tfk80002ks/T/OPVisit4351506020699524406.xml Uranus in window 22-DEC-2022 to 08-FEB-2023 as close as possible to the JWST observations in program 1248. 4 orbits. Visit 4 after visit 1 by between 9 and 11 orbits. All visits spaced out as evenly as possible within the 17 hour 14 minute Uranian day, with ideally 2- or 3-orbit gaps between them (ideal spacing is 4 hours). 1-orbit gaps are too close. Impingement into SAA is OK if the above timing gaps cannot prevent it. We can tolerate gyro bias updates to ease the contiguous orbit constraints, and will work with our program contacts to fit them in. 3-gyro mode may be necessary as this is a moving target. (Tic-Visit :proposal-id 17187 :visit-id "04" :proposal-version -1 :trans-version "20220630" :date "22-Oct-2022 11:09: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 254848 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17187 :visit-id "04" :obset-id "04" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17187 :visit-id "04" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2370 :al-overhead-at-end 0 :internal-dur-at-end 315 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2782 :pcs-gap 0 ) true 1 0 Using ephemeris for target 17187-05-NEPTUNE ephemeris data for target 17187-05-NEPTUNE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.273 to 24.275 Timing link suitability includes constraints ([06 After 05 by 0.1 to 0.2 days]) The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. 52 /private/var/folders/58/m3km1yk15rgcq0hfq011tfk80002ks/T/OPVisit7962674318182677751.xml Neptune in first window 01-NOV-2022 to 19-DEC-2022 (very flexible due to JWST observations not being sceduled in this window, just needs to be separated in time as much as possible from both the 2022 OPAL Neptune and window 2 in 2023). 4 orbits. Visit 4 after visit 1 by between 9 and 11 orbits. All visits spaced out as evenly as possible within the 16 hour 6 minute Neptunian day, with ideally 2- or 3-orbit gaps between them (ideal spacing is 4 hours). 1-orbit gaps are too close. Impingement into SAA is OK if the above timing gaps cannot prevent it. We can tolerate gyro bias updates to ease the contiguous orbit constraints, and will work with our program contacts to fit them in. 3-gyro mode may be necessary as this is a moving target. (Tic-Visit :proposal-id 17187 :visit-id "05" :proposal-version -1 :trans-version "20220630" :date "22-Oct-2022 11:09: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 255056 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17187 :visit-id "05" :obset-id "05" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17187 :visit-id "05" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2361 :al-overhead-at-end 0 :internal-dur-at-end 315 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2782 :pcs-gap 0 ) true 1 0 Using ephemeris for target 17187-06-NEPTUNE ephemeris data for target 17187-06-NEPTUNE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.273 to 24.275 Timing link suitability includes constraints ([06 After 05 by 0.1 to 0.2 days] [07 After 06 by 0.1 to 0.2 days]) The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. 52 /private/var/folders/58/m3km1yk15rgcq0hfq011tfk80002ks/T/OPVisit14829048653128448011.xml Neptune in first window 01-NOV-2022 to 19-DEC-2022 (very flexible due to JWST observations not being sceduled in this window, just needs to be separated in time as much as possible from both the 2022 OPAL Neptune and window 2 in 2023). 4 orbits. Visit 4 after visit 1 by between 9 and 11 orbits. All visits spaced out as evenly as possible within the 16 hour 6 minute Neptunian day, with ideally 2- or 3-orbit gaps between them (ideal spacing is 4 hours). 1-orbit gaps are too close. Impingement into SAA is OK if the above timing gaps cannot prevent it. We can tolerate gyro bias updates to ease the contiguous orbit constraints, and will work with our program contacts to fit them in. 3-gyro mode may be necessary as this is a moving target. (Tic-Visit :proposal-id 17187 :visit-id "06" :proposal-version -1 :trans-version "20220630" :date "22-Oct-2022 11:09: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 255056 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17187 :visit-id "06" :obset-id "06" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17187 :visit-id "06" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2361 :al-overhead-at-end 0 :internal-dur-at-end 315 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2782 :pcs-gap 0 ) true 1 0 Using ephemeris for target 17187-07-NEPTUNE ephemeris data for target 17187-07-NEPTUNE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.273 to 24.275 Timing link suitability includes constraints ([07 After 06 by 0.1 to 0.2 days] [08 After 07 by 0.1 to 0.2 days]) The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. 52 /private/var/folders/58/m3km1yk15rgcq0hfq011tfk80002ks/T/OPVisit6916669711814547120.xml Neptune in first window 01-NOV-2022 to 19-DEC-2022 (very flexible due to JWST observations not being sceduled in this window, just needs to be separated in time as much as possible from both the 2022 OPAL Neptune and window 2 in 2023). 4 orbits. Visit 4 after visit 1 by between 9 and 11 orbits. All visits spaced out as evenly as possible within the 16 hour 6 minute Neptunian day, with ideally 2- or 3-orbit gaps between them (ideal spacing is 4 hours). 1-orbit gaps are too close. Impingement into SAA is OK if the above timing gaps cannot prevent it. We can tolerate gyro bias updates to ease the contiguous orbit constraints, and will work with our program contacts to fit them in. 3-gyro mode may be necessary as this is a moving target. (Tic-Visit :proposal-id 17187 :visit-id "07" :proposal-version -1 :trans-version "20220630" :date "22-Oct-2022 11:09: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 255056 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17187 :visit-id "07" :obset-id "07" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17187 :visit-id "07" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2361 :al-overhead-at-end 0 :internal-dur-at-end 315 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2782 :pcs-gap 0 ) true 1 0 Using ephemeris for target 17187-08-NEPTUNE ephemeris data for target 17187-08-NEPTUNE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.273 to 24.275 Timing link suitability includes constraints ([08 After 07 by 0.1 to 0.2 days]) The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. 52 /private/var/folders/58/m3km1yk15rgcq0hfq011tfk80002ks/T/OPVisit16752793121674964123.xml Neptune in first window 01-NOV-2022 to 19-DEC-2022 (very flexible due to JWST observations not being sceduled in this window, just needs to be separated in time as much as possible from both the 2022 OPAL Neptune and window 2 in 2023). 4 orbits. Visit 4 after visit 1 by between 9 and 11 orbits. All visits spaced out as evenly as possible within the 16 hour 6 minute Neptunian day, with ideally 2- or 3-orbit gaps between them (ideal spacing is 4 hours). 1-orbit gaps are too close. Impingement into SAA is OK if the above timing gaps cannot prevent it. We can tolerate gyro bias updates to ease the contiguous orbit constraints, and will work with our program contacts to fit them in. 3-gyro mode may be necessary as this is a moving target. (Tic-Visit :proposal-id 17187 :visit-id "08" :proposal-version -1 :trans-version "20220630" :date "22-Oct-2022 11:09: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 255056 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17187 :visit-id "08" :obset-id "08" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17187 :visit-id "08" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2361 :al-overhead-at-end 0 :internal-dur-at-end 315 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2782 :pcs-gap 0 ) true 1 0 Using ephemeris for target 17187-09-NEPTUNE ephemeris data for target 17187-09-NEPTUNE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.273 to 24.275 Timing link suitability includes constraints ([10 After 09 by 0.1 to 0.2 days]) The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. 52 /private/var/folders/58/m3km1yk15rgcq0hfq011tfk80002ks/T/OPVisit10373165376225516110.xml Neptune in first window 13-JUN-2023 to 26-JUN-2023 - as close as possible to the JWST observations in program 1249. 4 orbits. Visit 4 after visit 1 by between 9 and 11 orbits. All visits spaced out as evenly as possible within the 16 hour 6 minute Neptunian day, with ideally 2- or 3-orbit gaps between them (ideal spacing is 4 hours). 1-orbit gaps are too close. Impingement into SAA is OK if the above timing gaps cannot prevent it. We can tolerate gyro bias updates to ease the contiguous orbit constraints, and will work with our program contacts to fit them in. 3-gyro mode may be necessary as this is a moving target. (Tic-Visit :proposal-id 17187 :visit-id "09" :proposal-version -1 :trans-version "20220630" :date "22-Oct-2022 11:09: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 255056 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17187 :visit-id "09" :obset-id "09" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17187 :visit-id "09" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2361 :al-overhead-at-end 0 :internal-dur-at-end 315 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2782 :pcs-gap 0 ) true 1 0 Using ephemeris for target 17187-10-NEPTUNE ephemeris data for target 17187-10-NEPTUNE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.273 to 24.275 Timing link suitability includes constraints ([10 After 09 by 0.1 to 0.2 days] [11 After 10 by 0.1 to 0.2 days]) The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. 52 /private/var/folders/58/m3km1yk15rgcq0hfq011tfk80002ks/T/OPVisit12422549949495556488.xml Neptune in first window 13-JUN-2023 to 26-JUN-2023 - as close as possible to the JWST observations in program 1249. 4 orbits. Visit 4 after visit 1 by between 9 and 11 orbits. All visits spaced out as evenly as possible within the 16 hour 6 minute Neptunian day, with ideally 2- or 3-orbit gaps between them (ideal spacing is 4 hours). 1-orbit gaps are too close. Impingement into SAA is OK if the above timing gaps cannot prevent it. We can tolerate gyro bias updates to ease the contiguous orbit constraints, and will work with our program contacts to fit them in. 3-gyro mode may be necessary as this is a moving target. (Tic-Visit :proposal-id 17187 :visit-id "10" :proposal-version -1 :trans-version "20220630" :date "22-Oct-2022 11:09: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 255056 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17187 :visit-id "10" :obset-id "10" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17187 :visit-id "10" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2361 :al-overhead-at-end 0 :internal-dur-at-end 315 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2782 :pcs-gap 0 ) true 1 0 Using ephemeris for target 17187-11-NEPTUNE ephemeris data for target 17187-11-NEPTUNE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.273 to 24.275 Timing link suitability includes constraints ([11 After 10 by 0.1 to 0.2 days] [12 After 11 by 0.1 to 0.2 days]) The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. 52 /private/var/folders/58/m3km1yk15rgcq0hfq011tfk80002ks/T/OPVisit12408360860078933805.xml Neptune in first window 13-JUN-2023 to 26-JUN-2023 - as close as possible to the JWST observations in program 1249. 4 orbits. Visit 4 after visit 1 by between 9 and 11 orbits. All visits spaced out as evenly as possible within the 16 hour 6 minute Neptunian day, with ideally 2- or 3-orbit gaps between them (ideal spacing is 4 hours). 1-orbit gaps are too close. Impingement into SAA is OK if the above timing gaps cannot prevent it. We can tolerate gyro bias updates to ease the contiguous orbit constraints, and will work with our program contacts to fit them in. 3-gyro mode may be necessary as this is a moving target. (Tic-Visit :proposal-id 17187 :visit-id "11" :proposal-version -1 :trans-version "20220630" :date "22-Oct-2022 11:09:09.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 255056 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17187 :visit-id "11" :obset-id "11" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17187 :visit-id "11" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2361 :al-overhead-at-end 0 :internal-dur-at-end 315 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2782 :pcs-gap 0 ) true 1 0 Using ephemeris for target 17187-12-NEPTUNE ephemeris data for target 17187-12-NEPTUNE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.273 to 24.275 Timing link suitability includes constraints ([12 After 11 by 0.1 to 0.2 days]) The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. 52 /private/var/folders/58/m3km1yk15rgcq0hfq011tfk80002ks/T/OPVisit11727196105345554752.xml Neptune in first window 13-JUN-2023 to 26-JUN-2023 - as close as possible to the JWST observations in program 1249. 4 orbits. Visit 4 after visit 1 by between 9 and 11 orbits. All visits spaced out as evenly as possible within the 16 hour 6 minute Neptunian day, with ideally 2- or 3-orbit gaps between them (ideal spacing is 4 hours). 1-orbit gaps are too close. Impingement into SAA is OK if the above timing gaps cannot prevent it. We can tolerate gyro bias updates to ease the contiguous orbit constraints, and will work with our program contacts to fit them in. 3-gyro mode may be necessary as this is a moving target. (Tic-Visit :proposal-id 17187 :visit-id "12" :proposal-version -1 :trans-version "20220630" :date "22-Oct-2022 11:09:10.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 255056 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17187 :visit-id "12" :obset-id "12" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17187 :visit-id "12" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2361 :al-overhead-at-end 0 :internal-dur-at-end 315 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2782 :pcs-gap 0 ) true 1 0