Target JUPITER: There is no need or capability to test the scheduling of observations of moving targets in Phase I. This warning will go away the next time the proposal is loaded. 0 Assigned ID: 4133 ----- Attempting Submission 1 (Tue May 23 17:35:24 GMT 2023) ----- Moving target visit planner will be run in Phase II This target is not used in this proposal. 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 Update of visits 16-18 from Mike Wong 1031140572 ----- Attempting Submission 1 (Mon Sep 04 14:42:04 GMT 2023) ----- ----- Attempting Submission 2 (Tue Dec 12 18:00:31 GMT 2023) ----- FLASH and exposures ok based on previous observations POS-TARGS checked Blade A is requested, if allowed, for F631 exposures to maximize spatial resolution Oscillations of Jupiter's Great Red Spot Jupiter's Great Red Spot (GRS) is the longest-lived, most mysterious, storm in the solar system. Similar large vortices on Neptune last only a few years, as they drift in latitude or simply fade away. Conversely, Jupiter's strong alternating wind field anchors the GRS in latitude, perhaps contributing to its longevity. On Earth, vortices are also disrupted by changes in latitude (Coriolis forces) or by forces that lead to instability (e.g., landfall, upper-level wind shear), and only rarely last longer than a year. Terrestrial eddies have been extensively studied, showing they dissipate as the mid-level core of storm erodes over time, but intensifying internal winds can increase their longevity. Comprehensive datasets do not yet exist for giant planet vortices, but some peculiar behaviors have been observed over shorter periods. First, the GRS drifts westward relative to Jupiter's wind field but with a ~90-day oscillation in the absolute drift rate. Similarly, a small Neptune dark was seen to oscillate in both latitude and longitude, while the larger Great Dark Spot oscillated in shape. The nature of such oscillations and why they manifest differently in each storm is a mystery. The GRS's smaller size at present allows increased interaction with Jupiter's winds; transient changes of this type were seen in 2019. Our proposed intense Hubble observational study would use the GRS as a fluid dynamics laboratory for studying vortex/wind interaction without terrestrial topography or latitudinal motion by measuring how its internal motions, size, and shape vary to stabilize it against the wind field over an oscillation cycle. Repeated observations of Jupiter's Great Red Spot over a 90-day period. Orbits are in groups of 3, with 2 contiguous orbits (A1 and A2) and one orbit (B) 10 hrs before or after. GRS center will be closer than 7 deg to the central meridian in at least one of the three orbits in each epoch. Predicted crossing times (within 30 sec), are based on amateur imaging from Jan, July & Aug. These will be doublechecked once the plan windows are known: Date Long CML transit Dec 1 90.5 07:22:00 Dec 16 95.1 04:47:00 Dec 31 99.7 02:31;30 Jan 15 104.3 09:37:00 Jan 30 108.9 07:06:30 Feb 14 113.5 04:36:30 If an epoch does not schedule with default values, we have a list of changes for the PC to try sequentially to improve schedulability: [1] ------ Increase BETWEEN timing requirement interval to +/- 6 days. [2] ------ Increase POS-TARG values for FQ727N exposures, first by 3 arcsec in each direction and then by 5 arcsec in each direction. For example, for Epoch 1 the POS-TARGs would increase by 3 arcsec in each direction from [-6.51, +6.72] to [-9.51, +9.72]. If that still does not work, then increase by 5 arcsec in each direction to [-11.51, +11.72]. This causes 10-30% of Jupiter's area to fall within the non-photometric edge area of the 727-nm filter (depending on geocentric distance and POS-TARG increment). [3] ------ Start deleting FQ727N exposures in this order: 3a - Delete from visit A1, keep in visits A2 and B. 3b - Delete from visit B, keep in visits A1 and A2. 3c - Delete from visits A1 and A2, keep in visit B. 3d - Delete from all visits in the epoch. ACTION NOTE (3a,3c,3d): Whenever a FQ727N exposure is deleted, the F631N exposure in 2K2D-SUB that follows it needs additional adjustment: change aperture to 2K2A-SUB, and change POS-TARG to match the other 2K2A-SUB frames in the orbit. It may quickest to duplicate exposure 1 (F631N 2K2A), place at end of visit, and delete the F631N 2K2D. EXPLANATORY NOTE: This change rule [3] distinguishes between A1 and A2, but the timing constraints are identical for the two visits. This is why A1 and A2 are GROUPED WITHIN 1 orbit instead of SEQUENCED, so a change to A1 enables simultaneous testing between that change happening in the first or second visit of the pair. This team has substantial experience with all aspects of Hubble proposals and data reduction and includes leading experts on Jupiter's atmosphere. Simon and Wong have each been PIs on previous successful Hubble programs, including all planning, data validation, image navigation and mapping; both the OPAL (PI: Simon) and WFCJ (PI: Wong) programs have public websites with archived high-level science products, and these programs have resulted in more than four dozen published science manuscripts. Simon will be responsible for managing all aspects of this program. Wong will assist in Phase II planning, as well as post-calibration defringing of the data. Data Analysis: Dr. Simon will be responsible for image mapping, measuring physical parameters, and data trending. Simon has published several papers detailing the changing Great Red Spot size, shapes, motions, and relative altitude changes. Dr. Marcus is one of the world's experts on velocimetry extraction and developed the ACCIV code we will use. His next generation ACCIV takes advantage of the latest developments in machine-learning techniques to even further improve the method. Dr. Wong is an expert in using ACCIV, as well as in planning the observations to maximize their potential with this technique. He will be respoible for producing the 2D velocity maps at each epoch Dr. Irwin was the developer of the NEMSIS radiative transfer retrieval tool, as well as subsequent versions developed for use on Hubble data. He will be responible for dertmining 3D altitude structure. All CoI's are experienced in calculating vorticity and other velocity-based parameters, as well general circulation modeling and analyses. We will work collaboratively on the balance analyses and interpretation. We anticipate several piblications from this work. Solar System Astronomy 6 false false false false false false false false AVAILABLE SOLAR SYSTEM PLANET Jupiter GRS STD=JUPITER NOT ECL P PARTIAL OF JUPITER BY IO FROM EARTH, NOT ECL P PARTIAL OF JUPITER BY EUROPA FROM EARTH, NOT ECL P PARTIAL OF JUPITER BY GANYMEDE FROM EARTH, NOT ECL P PARTIAL OF JUPITER BY CALLISTO FROM EARTH, SEP OF JUPITER IO FROM EARTH GT 1", SEP OF JUPITER EUROPA FROM EARTH GT 1", SEP OF JUPITER GANYMEDE FROM EARTH GT 1", SEP OF JUPITER CALLISTO FROM EARTH GT 1" EARTH SOLAR SYSTEM PLANET Jupiter GRS STD=JUPITER EARTH SOLAR SYSTEM PLANET Jupiter GRS STD=JUPITER NOT ECL P PARTIAL OF JUPITER BY IO FROM EARTH, NOT ECL P PARTIAL OF JUPITER BY EUROPA FROM EARTH, NOT ECL P PARTIAL OF JUPITER BY GANYMEDE FROM EARTH, NOT ECL P PARTIAL OF JUPITER BY CALLISTO FROM EARTH, NOT TRANSIT OF IO ACROSS JUPITER FROM EARTH, NOT TRANSIT OF EUROPA ACROSS JUPITER FROM EARTH, NOT TRANSIT OF GANYMEDE ACROSS JUPITER FROM EARTH, NOT TRANSIT OF CALLISTO ACROSS JUPITER FROM EARTH EARTH WFC3/UVIS Imaging No No F275W WFC3/UVIS Imaging No No F395N WFC3/UVIS Imaging No No F502N WFC3/UVIS Imaging No No F631N WFC3/UVIS Imaging No No FQ889N WFC3/UVIS Imaging No No FQ727N POS-TARG DITHER 0.87 LINE false false 2 46.84 WFC3-UVIS-DITHER-LINE 1 false Using ephemeris for target 17495-01-JUPITER-MOONS-CLOSE ephemeris data for target 17495-01-JUPITER-MOONS-CLOSE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.314 to 25.089. ephemeris interval: 24.031 to 26.032 Phase windows are not calculated when the gap between schedulable intervals is less than 1 days, assuming no scheduling restrictions for constraint Phase 0.000/0.152. Timing link suitability includes constraints ([Group (01 03) Within 0.6 days]) The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. Epoch 7: 24 Feb 1708774741000 71.19999999999999 (Tic-Visit :proposal-id 17495 :visit-id "01" :proposal-version -1 :trans-version "20230626" :date "02-Feb-2024 16:25:58.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 385248 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17495 :visit-id "01" :obset-id "01" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17495 :visit-id "01" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2085 :al-overhead-at-end 0 :internal-dur-at-end 457 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2776 :pcs-gap 0 ) false 1 0 Using ephemeris for target 17495-02-JUPITER-MOONS-CLOSE ephemeris data for target 17495-02-JUPITER-MOONS-CLOSE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.314 to 25.089. ephemeris interval: 24.031 to 26.032 Phase windows are not calculated when the gap between schedulable intervals is less than 1 days, assuming no scheduling restrictions for constraint Phase 0.000/0.152. Timing link suitability includes constraints ([Group (02 08) Within 0.6 days]) The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. Epoch 8: 7 Mar (Tic-Visit :proposal-id 17495 :visit-id "02" :proposal-version -1 :trans-version "20230626" :date "02-Feb-2024 16:26: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 385248 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17495 :visit-id "02" :obset-id "02" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17495 :visit-id "02" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2085 :al-overhead-at-end 0 :internal-dur-at-end 457 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2776 :pcs-gap 0 ) false 1 0 Using ephemeris for target 17495-03-JUPITER-MOONS-CLOSE ephemeris data for target 17495-03-JUPITER-MOONS-CLOSE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.314 to 25.089. ephemeris interval: 24.031 to 26.032 Phase windows are not calculated when the gap between schedulable intervals is less than 1 days, assuming no scheduling restrictions for constraint Phase 0.000/0.152. Timing link suitability includes constraints ([Group (01 03) Within 0.6 days]) The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. Epoch 7: 24 Feb B one Jupiter rotation before or after A 1708814154000 72.18289848103541 (Tic-Visit :proposal-id 17495 :visit-id "03" :proposal-version -1 :trans-version "20230626" :date "02-Feb-2024 16:26:20.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 385248 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17495 :visit-id "03" :obset-id "03" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17495 :visit-id "03" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2085 :al-overhead-at-end 0 :internal-dur-at-end 457 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2776 :pcs-gap 0 ) false 1 0 Using ephemeris for target 17495-04-JUPITER Phase windows are not calculated when the gap between schedulable intervals is less than 1 days, assuming no scheduling restrictions for constraint Phase 0.000/0.258. Timing link suitability includes constraints ([Group (04 05) Within 0.1 days] [Group (04 05 06) Within 0.6 days]) The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Epoch 2: Dec 16 +/- 3 days 1702194905000 69.30465011186169 (Tic-Visit :proposal-id 17495 :visit-id "04" :proposal-version -1 :trans-version "20230627" :date "04-Sep-2023 10:25:39.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 563088 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17495 :visit-id "04" :obset-id "04" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17495 :visit-id "04" :orbit-number 1 :pcs-time 443 :si-vis-utilization 1857 :al-overhead-at-end 0 :internal-dur-at-end 652 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2776 :pcs-gap 0 ) false 1 0 Using ephemeris for target 17495-05-JUPITER Phase windows are not calculated when the gap between schedulable intervals is less than 1 days, assuming no scheduling restrictions for constraint Phase 0.000/0.258. Timing link suitability includes constraints ([Group (04 05) Within 0.1 days] [Group (04 05 06) Within 0.6 days]) The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. A1 and A2 consecutive 1702200253000 69.30741020310549 (Tic-Visit :proposal-id 17495 :visit-id "05" :proposal-version -1 :trans-version "20230627" :date "04-Sep-2023 10:25: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 563088 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17495 :visit-id "05" :obset-id "05" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17495 :visit-id "05" :orbit-number 1 :pcs-time 443 :si-vis-utilization 1857 :al-overhead-at-end 0 :internal-dur-at-end 652 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2776 :pcs-gap 0 ) false 1 0 Using ephemeris for target 17495-06-JUPITER Phase windows are not calculated when the gap between schedulable intervals is less than 1 days, assuming no scheduling restrictions for constraint Phase 0.064/0.195. Timing link suitability includes constraints ([Group (04 05 06) Within 0.6 days]) The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. B one Jupiter rotation before or after A1+A2 1702234440000 69.3248655295215 (Tic-Visit :proposal-id 17495 :visit-id "06" :proposal-version -1 :trans-version "20230627" :date "04-Sep-2023 10:25: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 563088 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17495 :visit-id "06" :obset-id "06" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17495 :visit-id "06" :orbit-number 1 :pcs-time 443 :si-vis-utilization 1857 :al-overhead-at-end 0 :internal-dur-at-end 652 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2776 :pcs-gap 0 ) false 1 0 Using ephemeris for target 17495-07-JUPITER Phase windows are not calculated when the gap between schedulable intervals is less than 1 days, assuming no scheduling restrictions for constraint Phase 0.000/0.258. Timing link suitability includes constraints ([Group (07 08) Within 0.1 days] [Group (07 08 09) Within 0.6 days]) The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Epoch 3: Dec 31 +/- 3 days 1703733320000 69.9116237396727 (Tic-Visit :proposal-id 17495 :visit-id "07" :proposal-version -1 :trans-version "20230627" :date "04-Sep-2023 10:25:42.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 563088 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17495 :visit-id "07" :obset-id "07" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17495 :visit-id "07" :orbit-number 1 :pcs-time 443 :si-vis-utilization 1857 :al-overhead-at-end 0 :internal-dur-at-end 652 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2776 :pcs-gap 0 ) false 1 0 Using ephemeris for target 17495-08-JUPITER-MOONS-CLOSE ephemeris data for target 17495-08-JUPITER-MOONS-CLOSE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.314 to 25.089. ephemeris interval: 24.031 to 26.032 Phase windows are not calculated when the gap between schedulable intervals is less than 1 days, assuming no scheduling restrictions for constraint Phase 0.000/0.152. Timing link suitability includes constraints ([Group (02 08) Within 0.6 days]) The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. Epoch 8: 7 Mar B one Jupiter rotation before or after A (Tic-Visit :proposal-id 17495 :visit-id "08" :proposal-version -1 :trans-version "20230626" :date "02-Feb-2024 16:26:29.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 385248 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17495 :visit-id "08" :obset-id "08" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17495 :visit-id "08" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2085 :al-overhead-at-end 0 :internal-dur-at-end 457 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2776 :pcs-gap 0 ) false 1 0 Using ephemeris for target 17495-09-JUPITER Phase windows are not calculated when the gap between schedulable intervals is less than 1 days, assuming no scheduling restrictions for constraint Phase 0.064/0.195. Timing link suitability includes constraints ([Group (07 08 09) Within 0.6 days]) The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. B one Jupiter rotation before or after A1+A2 1703773425000 69.92507472566169 (Tic-Visit :proposal-id 17495 :visit-id "09" :proposal-version -1 :trans-version "20230627" :date "04-Sep-2023 10:25:44.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 563088 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17495 :visit-id "09" :obset-id "09" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17495 :visit-id "09" :orbit-number 1 :pcs-time 443 :si-vis-utilization 1857 :al-overhead-at-end 0 :internal-dur-at-end 652 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2776 :pcs-gap 0 ) false 1 0 Using ephemeris for target 17495-10-JUPITER Phase windows are not calculated when the gap between schedulable intervals is less than 1 days, assuming no scheduling restrictions for constraint Phase 0.000/0.258. Timing link suitability includes constraints ([Group (10 11) Within 0.1 days] [Group (10 11 12) Within 0.6 days]) The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Epoch 4: Jan 15 +/- 3 days 1705020616000 78.4021122012141 (Tic-Visit :proposal-id 17495 :visit-id "10" :proposal-version -1 :trans-version "20230627" :date "04-Sep-2023 10:25: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 563088 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17495 :visit-id "10" :obset-id "10" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17495 :visit-id "10" :orbit-number 1 :pcs-time 443 :si-vis-utilization 1857 :al-overhead-at-end 0 :internal-dur-at-end 652 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2776 :pcs-gap 0 ) false 1 0 Using ephemeris for target 17495-11-JUPITER Phase windows are not calculated when the gap between schedulable intervals is less than 1 days, assuming no scheduling restrictions for constraint Phase 0.000/0.258. Timing link suitability includes constraints ([Group (10 11) Within 0.1 days] [Group (10 11 12) Within 0.6 days]) The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. A1 and A2 consecutive 1705026313000 77.01245368674842 (Tic-Visit :proposal-id 17495 :visit-id "11" :proposal-version -1 :trans-version "20230627" :date "04-Sep-2023 10:25:46.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 563088 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17495 :visit-id "11" :obset-id "11" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17495 :visit-id "11" :orbit-number 1 :pcs-time 443 :si-vis-utilization 1857 :al-overhead-at-end 0 :internal-dur-at-end 652 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2776 :pcs-gap 0 ) false 1 0 Using ephemeris for target 17495-12-JUPITER Phase windows are not calculated when the gap between schedulable intervals is less than 1 days, assuming no scheduling restrictions for constraint Phase 0.064/0.195. Timing link suitability includes constraints ([Group (10 11 12) Within 0.6 days]) The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. B one Jupiter rotation before or after A1+A2 1705060494000 77.01573988702029 (Tic-Visit :proposal-id 17495 :visit-id "12" :proposal-version -1 :trans-version "20230627" :date "04-Sep-2023 10:25:47.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 563088 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17495 :visit-id "12" :obset-id "12" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17495 :visit-id "12" :orbit-number 1 :pcs-time 443 :si-vis-utilization 1857 :al-overhead-at-end 0 :internal-dur-at-end 652 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2776 :pcs-gap 0 ) false 1 0 Using ephemeris for target 17495-13-JUPITER Phase windows are not calculated when the gap between schedulable intervals is less than 1 days, assuming no scheduling restrictions for constraint Phase 0.000/0.258. Timing link suitability includes constraints ([Group (13 14) Within 0.1 days] [Group (13 14 15) Within 0.6 days]) The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Epoch 5: Jan 30 +/- 3 days 1706700867000 71.0296933147267 (Tic-Visit :proposal-id 17495 :visit-id "13" :proposal-version -1 :trans-version "20230922" :date "11-Dec-2023 16:34:53.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "02" :si-bright-earth-limb-angle 20.0 :data-volume 563088 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17495 :visit-id "13" :obset-id "13" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17495 :visit-id "13" :orbit-number 1 :pcs-time 443 :si-vis-utilization 1857 :al-overhead-at-end 0 :internal-dur-at-end 652 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2776 :pcs-gap 0 ) false 1 0 Using ephemeris for target 17495-14-JUPITER Phase windows are not calculated when the gap between schedulable intervals is less than 1 days, assuming no scheduling restrictions for constraint Phase 0.000/0.258. Timing link suitability includes constraints ([Group (13 14) Within 0.1 days] [Group (13 14 15) Within 0.6 days]) The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. /System/Volumes/Data/solaris/user1/aroman/work/hst/OP-cache/17495-v14.xml A1 and A2 consecutive 1706706562000 71.03231194990121 (Tic-Visit :proposal-id 17495 :visit-id "14" :proposal-version -1 :trans-version "20230626" :date "07-Dec-2023 15: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 "02" :si-bright-earth-limb-angle 20.0 :data-volume 563088 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17495 :visit-id "14" :obset-id "14" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17495 :visit-id "14" :orbit-number 1 :pcs-time 443 :si-vis-utilization 1857 :al-overhead-at-end 0 :internal-dur-at-end 652 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2776 :pcs-gap 0 ) false 1 0 Using ephemeris for target 17495-15-JUPITER Phase windows are not calculated when the gap between schedulable intervals is less than 1 days, assuming no scheduling restrictions for constraint Phase 0.064/0.195. Timing link suitability includes constraints ([Group (13 14 15) Within 0.6 days]) The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. /System/Volumes/Data/solaris/user1/aroman/work/hst/OP-cache/17495-v15.xml B one Jupiter rotation before or after A1+A2 1706740805000 71.04805933373089 (Tic-Visit :proposal-id 17495 :visit-id "15" :proposal-version -1 :trans-version "20230626" :date "07-Dec-2023 16:21:33.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "02" :si-bright-earth-limb-angle 20.0 :data-volume 351936 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17495 :visit-id "15" :obset-id "15" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17495 :visit-id "15" :orbit-number 1 :pcs-time 351 :si-vis-utilization 1192 :al-overhead-at-end 0 :internal-dur-at-end 421 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2776 :pcs-gap 0 ) false 1 0 Using ephemeris for target 17495-16-JUPITER Phase windows are not calculated when the gap between schedulable intervals is less than 1 days, assuming no scheduling restrictions for constraint Phase 0.000/0.258. Timing link suitability includes constraints ([Group (16 17) Within 0.1 days] [Group (16 17 18) Within 0.6 days]) The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Epoch 6: Feb 14 +/- 3 days 1707703501000 71.53331432527489 (Tic-Visit :proposal-id 17495 :visit-id "16" :proposal-version -1 :trans-version "20230922" :date "11-Dec-2023 16:34:42.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 563088 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17495 :visit-id "16" :obset-id "16" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17495 :visit-id "16" :orbit-number 1 :pcs-time 443 :si-vis-utilization 1802 :al-overhead-at-end 0 :internal-dur-at-end 652 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2776 :pcs-gap 0 ) false 1 0 Using ephemeris for target 17495-17-JUPITER Phase windows are not calculated when the gap between schedulable intervals is less than 1 days, assuming no scheduling restrictions for constraint Phase 0.000/0.258. Timing link suitability includes constraints ([Group (16 17) Within 0.1 days] [Group (16 17 18) Within 0.6 days]) The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. A1 and A2 consecutive 1707709269000 71.52655267324329 (Tic-Visit :proposal-id 17495 :visit-id "17" :proposal-version -1 :trans-version "20230922" :date "11-Dec-2023 16:34:42.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 563088 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17495 :visit-id "17" :obset-id "17" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17495 :visit-id "17" :orbit-number 1 :pcs-time 443 :si-vis-utilization 1729 :al-overhead-at-end 0 :internal-dur-at-end 652 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2776 :pcs-gap 0 ) false 1 0 Using ephemeris for target 17495-18-JUPITER Phase windows are not calculated when the gap between schedulable intervals is less than 1 days, assuming no scheduling restrictions for constraint Phase 0.064/0.195. Timing link suitability includes constraints ([Group (16 17 18) Within 0.6 days]) The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. B one Jupiter rotation before or after A1+A2 1707737714000 71.55196616246809 (Tic-Visit :proposal-id 17495 :visit-id "18" :proposal-version -1 :trans-version "20230922" :date "11-Dec-2023 16:34: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 563088 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17495 :visit-id "18" :obset-id "18" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17495 :visit-id "18" :orbit-number 1 :pcs-time 443 :si-vis-utilization 1802 :al-overhead-at-end 0 :internal-dur-at-end 652 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2776 :pcs-gap 0 ) false 1 0