0 Assigned ID: 4205 ----- Attempting Submission 1 (Tue May 23 23:41:57 GMT 2023) ----- This target is not used in this proposal. This target is not used in this proposal. This target is not used in this proposal. This pattern is not used in this proposal. This pattern is not used in this proposal. This pattern is not used in this proposal. This pattern is not used in this proposal. This pattern is not used in this proposal. This pattern is not used in this proposal. For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser. The specified GS Acq Scenario is not in the current list of valid scenarios. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. The specified GS Acq Scenario is not in the current list of valid scenarios. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. A target acquisition should probably be performed before doing spectroscopy or coronography with STIS or COS. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. A target acquisition should probably be performed before doing spectroscopy or coronography with STIS or COS. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. A target acquisition should probably be performed before doing spectroscopy or coronography with STIS or COS. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. A target acquisition should probably be performed before doing spectroscopy or coronography with STIS or COS. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. The specified GS Acq Scenario is not in the current list of valid scenarios. The EXTENDED optional parameter is deprecated and ignored. Please set EXTENDED on the target. The EXTENDED optional parameter is deprecated and ignored. Please set EXTENDED on the target. For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. The specified GS Acq Scenario is not in the current list of valid scenarios. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. The specified GS Acq Scenario is not in the current list of valid scenarios. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. The specified GS Acq Scenario is not in the current list of valid scenarios. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. The specified GS Acq Scenario is not in the current list of valid scenarios. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. The specified GS Acq Scenario is not in the current list of valid scenarios. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Unsupported characters were found in Comments and replaced with |*| Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser The specified GS Acq Scenario is not in the current list of valid scenarios. 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 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 Sensitive exposures should have an ETC run number provided. Sensitive exposures should have an ETC run number provided. The specified GS Acq Scenario is not in the current list of valid scenarios. The specified GS Acq Scenario is not in the current list of valid scenarios. Be very careful mixing POS TARG and Center_Pattern = Yes Be very careful mixing POS TARG and Center_Pattern = Yes The specified GS Acq Scenario is not in the current list of valid scenarios. Be very careful mixing POS TARG and Center_Pattern = Yes Be very careful mixing POS TARG and Center_Pattern = Yes The specified GS Acq Scenario is not in the current list of valid scenarios. Be very careful mixing POS TARG and Center_Pattern = Yes Be very careful mixing POS TARG and Center_Pattern = Yes Be very careful mixing POS TARG and Center_Pattern = Yes Be very careful mixing POS TARG and Center_Pattern = Yes COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details. Updated Visit 44 to have a POS-TARG of X=7 and Y=-7 to place Io in the lower right of the FOV following what was done for Visits 42 and 43. -939729966 ----- Attempting Submission 1 (Wed Aug 23 17:57:01 GMT 2023) ----- ----- Attempting Submission 2 (Fri Sep 15 00:41:59 GMT 2023) ----- HST Phase II Proposal 17470 successfully submitted. Receipt: # 17470-2 ----- Attempting Submission 3 (Fri Sep 15 11:36:51 GMT 2023) ----- ----- Attempting Submission 4 (Thu Oct 12 19:15:50 GMT 2023) ----- ----- Attempting Submission 5 (Fri Oct 13 17:50:49 GMT 2023) ----- ----- Attempting Submission 6 (Tue Oct 31 14:05:38 GMT 2023) ----- ----- Attempting Submission 7 (Wed Nov 01 10:39:39 GMT 2023) ----- HST Phase II Proposal 17470 successfully submitted. Receipt: # 17470-7 ----- Attempting Submission 8 (Wed Nov 01 11:46:38 GMT 2023) ----- ----- Attempting Submission 9 (Wed Nov 01 18:43:12 GMT 2023) ----- ----- Attempting Submission 10 (Fri Nov 10 09:35:24 GMT 2023) ----- ----- Attempting Submission 11 (Tue Nov 14 03:30:39 GMT 2023) ----- ----- Attempting Submission 12 (Mon Nov 20 18:45:21 GMT 2023) ----- ----- Attempting Submission 13 (Fri Dec 08 16:16:20 GMT 2023) ----- ----- Attempting Submission 14 (Thu Jan 11 15:02:31 GMT 2024) ----- ----- Attempting Submission 15 (Fri Jan 26 20:45:27 GMT 2024) ----- ----- Attempting Submission 16 (Mon Jan 29 19:28:27 GMT 2024) ----- ----- Attempting Submission 17 (Fri Feb 16 08:06:06 GMT 2024) ----- Your proposal could not be saved. Submission aborted. ----- Attempting Submission 18 (Fri May 03 18:38:56 GMT 2024) ----- ----- Attempting Submission 19 (Thu May 09 19:01:45 GMT 2024) ----- ----- Attempting Submission 20 (Wed Jul 17 14:38:31 GMT 2024) ----- ----- Attempting Submission 21 (Fri Jul 19 21:00:35 GMT 2024) ----- ----- Attempting Submission 22 (Wed Aug 14 05:37:56 GMT 2024) ----- HST Phase II Proposal 17470 successfully submitted. Receipt: # 17470-22 ----- Attempting Submission 23 (Wed Aug 14 06:41:45 GMT 2024) ----- ----- Attempting Submission 24 (Wed Aug 14 16:37:18 GMT 2024) ----- ----- Attempting Submission 25 (Thu Aug 15 12:57:16 GMT 2024) ----- ----- Attempting Submission 26 (Thu Aug 15 15:05:46 GMT 2024) ----- ----- Attempting Submission 27 (Fri Aug 16 20:35:24 GMT 2024) ----- ----- Attempting Submission 28 (Thu Aug 22 16:51:53 GMT 2024) ----- Your proposal could not be saved. Submission aborted. ----- Attempting Submission 29 (Tue Aug 27 12:56:57 GMT 2024) ----- ----- Attempting Submission 30 (Wed Aug 28 14:08:00 GMT 2024) ----- ----- Attempting Submission 31 (Fri Aug 30 17:18:43 GMT 2024) ----- ----- Attempting Submission 32 (Tue Sep 03 15:49:36 GMT 2024) ----- ----- Attempting Submission 33 (Wed Aug 20 16:55:13 GMT 2025) ----- ----- Attempting Submission 34 (Wed Sep 17 14:52:09 GMT 2025) ----- ----- Attempting Submission 35 (Wed Oct 01 20:14:32 GMT 2025) ----- ----- Attempting Submission 36 (Tue Oct 07 20:01:41 GMT 2025) ----- ----- Attempting Submission 37 (Fri Oct 10 20:23:48 GMT 2025) ----- ----- Attempting Submission 38 (Fri Oct 24 19:41:50 GMT 2025) ----- ----- Attempting Submission 39 (Mon Oct 27 20:13:35 GMT 2025) ----- ----- Attempting Submission 40 (Tue Nov 11 17:35:57 GMT 2025) ----- Your proposal could not be saved. Submission aborted. ----- Attempting Submission 41 (Mon Nov 17 19:52:34 GMT 2025) ----- Visit 44 POS-TARG update Io is the most volcanically active body in the solar system and its escaping atmosphere is the dominant source of material for the Jovian magnetosphere. Despite decades of research and major advances in understanding individual processes and features, the connections between Io's volcanos, surface volatiles, atmosphere, magnetospheric plasma-interaction, and beyond to Io's neutral cloud, the Io Plasma Torus, and Jupiter's ionosphere, all remain difficult to quantify and understand. Juno, a polar orbiter originally designed to study Jupiter's deep interior, magnetosphere, and aurora, is now in an extended mission focused on studying the Galilean satellites. Juno's upcoming Io flybys in Cycle 31 offer an excellent opportunity for combining Juno's intensive in situ measurements with Earth-based remote sensing to advance our understanding of Io's role in driving coupled phenomena within the Jupiter system. Two flybys come within ~1500 km of Io, with a third more distant encounter at ~120,000 km. Our HST-Juno Io campaign performs numerous coordinated Io observations to take full advantage of this opportunity for combining in situ and remote sensing datasets within a comprehensive modeling framework (not otherwise possible until the late 2030's). We plan multi-spectral, multi-instrument HST observations of the following types: Io neutral cloud profiling and ansae stares, Io FUV aurora imaging, Io transit imaging, Io eclipse imaging (with hot spot and time series studies), and Io surface mapping. Coordinated JWST MIRI/MRS IFU measurements of Io's 7.3 um SO2 band and newly detected 5 um features are requested for Juno's Sep. 2024 encounter (following plans for JWST program 4078). We identify five needed measurement types to investigate the five science themes. This implementation approach and scope has considered the schedulability of moving target observations, including the 2-orbit per visit constraint under 2-gyro mode. The first two Juno flybys in Dec. 2023 and Feb. 2024 approach closer to Io than the one in Sept. 2024. Hence the earlier encounters are higher priority and with more visits. The STScI help desk confirmed that PJ57 & PJ58 are not impacted by the South Atlantic Anomaly (SAA). Io Neutral Cloud Profiling and Ansae Stares: The Io neutral cloud profiling technique includes six sets of two nearly consecutive visits, each with two orbits STIS G140L 52x2 and two orbits of COS G130M. The STIS FUV measurements start at Io, step left of Io by 2" and then step right of Io by 2" for a view of its near-Io (<10 R_Io) neutral emissions in each of two consecutive orbits per visit. The two orbits provide radial profiles to enable characterization for hemispherical asymmetries near-Io hinted at (but indistinguishable) in previous data. In near-consecutive visits, COS 130M step-scans start on Io with high SNR and step along the orbital plane and perpendicular to it in the two respective orbits (if HST pitch and roll slew angles are required instead our large program is flexible in this way). Each step within the orbit has progressively longer exposures to provide similar error bars at each point along a power-law fall-off in distance (-0.025 R/RIo, as determined with New Horizons Alice spectral imaging to 1 R sensitivity; we expect better, down to ~0.1 R with COS). That is, ~1 min * 2N each for 0pt (on Io), 5 RIo, 10 RIo, 20 RIo, and 40 RIo, and then dwell at 80 RIo for the remainder of an HST orbit (up to 20 min). These times can be adjusted as informed by first visit (e.g., change 2N to 1.8N) and tailored for each scan direction. The COS time-tag mode allows data acquisition while slewing between steps (or possibly scan with decreasing angular velocity away from Io). The six visits cover Io at leading/trailing and sub-/anti-jovian orbital longitudes, with the leading and trailing repeated near the end of Cy31. Additional visits with Io at the east and west ansae, 2 orbits each, use the STIS G140M 1285 mode and 52x0.5 slit with four 0.5"-step positions covering Io to obtain spectrally separated images of neutral sulfur SI 125.1 nm and ionized SII 125.6 nm emissions for near-Io ionospheric chemistry modeling. Four orbits with COS 130M are planned at each of two geometries targeting the east and west ansae of Io's orbit while Io is at the direct opposite ansa. These long stares determine the furthest extent of neutrals within the environment and their relation to the torus; previous data show ~1-3 R O & S signals over very large spatial scales, which needs better characterization. Another visit with two orbits is planned with COS G230L to constrain the Mg species in Io's atmosphere and trailing hemisphere plasma environment. To address the topic of where the Io neutral cloud environment leaves off and the Europa neutral cloud or tori dominates we plan identical COS G130M step-scan observation orthogonal pairs starting on Europa but ranging out to 20 R_Europa instead and 2-orbit STIS G140L 52x2 context images. Total for neutral cloud mapping: 46 orbits. Io FUV Aurora Imaging: STIS G140L 52x2D1 images are planned closest in time as possible for each of the three Juno C/A events. Our early checks indicate that SAA-exclusions will not overlap with these key times. Three 2-orbit visits are planned for a series of 6 orbits covering the three C/A event times, with one visit likely shifted to follow or precede the SAA-exclusion time. The two consecutive 2-orbit visits cover more than half a synodic period of Jupiter's magnetic field orientation changing at Io, providing good temporal coverage of the rocking of the aurora equatorial spot locations for investigation the plasma-atmosphere interaction in detail; the additional near-consecutive 2-orbit visit completes the full synodic period coverage. For ease of scheduling within SAA constraints, just four orbits each are planned for Juno plasma sheet crossings on PJ59 in early March and PJ64 in mid-August, timed such that Io is exposed to the plasma probed earlier by Juno. Each of the 5 perijoves by Juno in the observable windows for Cy31 offers opportunities for joint Io aurora STIS imaging during both Juno-UVS Io footprint imaging and/or views of Io from Juno-UVS while in a radiation quite zone near Jupiter and ~6 R_J range. Two-orbit visits for 3 such occurrences are planned (with the 6 neutral cloud series also possibly available for coordination). Any orbits lost to gyro problems would best be replanned to extend the series during future events, as possible. Total for FUV auroral spot imaging: 32 orbits. Io Transit Imaging: With Io's 1.7 day orbital period roughly 60 (35) transit events are available early (late) in Cy31 (similarly but less so for eclipse events), with one and sometimes two HST orbits possible in each event. We search for plume gas variability in 4 events using STIS MAMA F25QTZ FUV imaging using the dither method implemented previously for Europa to obtain ~30 km/pix resolution elements with 1-orbit per event. Two additional orbits using the same longpass (>150 nm) F25QTZ filter would assess any faint auroral emission or disk reflectance PSF systematic features. Imaging mostly dust absorption at visible wavelengths, transit events near the beginning and end of Cy31 (1-orbit each) are planned with WFC3 filter sets (F225W, F280N, F336W, F343N, F390W, F475W, F555W). STIS NUV spectral imaging demonstrated SO2 and S2 absorption with G230LB. We plan four separate transit events using STIS G230M centered at c2095 & c2659 for mapping the deepest SO2 & S2 absorption features, respectively (2 events each). The 52x0.5 slit is used with a set of five or more 0.1" step-offsets, expecting to improve on previous resolutions and noise (using NUV MAMA vs CCD). Lastly, 4 transit events use the COS 225M mode to measure SO2 absorption features (210-234 nm); these include one or two off-Io pointings at ~3 R_Io and/or 5 RIo (as time allows) and also a pointing farther away to provide the Jupiter background divisor spectrum (i.e., pointing back towards the location on Jupiter recently transited) in 1-orbit. A fifth orbit observes Io in sunlight with COS G225M just before or after transit to characterize its disk spectrum for comparison with the off-Io data. Total for Io transit imaging: 17 orbits. Io Eclipse Imaging, Loki Hot Spot, and Time Series: Observations in Jupiter's shadow offer the best ability to image Loki's hot-spot thermal and auroral emissions without the overwhelming component of reflected sunlight. The STIS G750L 52x0.1E1 slit targets the Loki hot spot, staring at ~13N,309W for one orbit and performing a three-step scan across it in an orbit during a different event to provide partial mapping of additional hot spots and/or provide an improved spectral background removal when extracting the black-body spectral reddening. The two orbits described occur for the post-ingress geometry to optimize pointing. For auroral SO2 and potentially S2 studies one orbit with STIS G430M c4706 52x2 targets a not yet confirmed S2 aurora spectral peak in previous G430L eclipse observations. Io Na doublet auroral images overlap when using the 52x2 slit, so an orbit with the G750M c6094 52x0.5E1 mode uses three steps across Io to image sodium (~2kR) simultaneously with oxygen red-line 630 nm emissions (~20-30kR). Two additional orbits search for auroral H-alpha and K features, with G750M 52x2E1 at c6768 and c7795, respectively. Angular separations of >20" from Jupiter are needed to avoid Jupiter straylight. While COS G130M and G225M spectra of Io in and out of eclipse have been performed (PID=11539), Io COS G230L c3000 (PID=12041) and STIS G230LB spectra have only been obtained while in sunlight. Two visits viewing pairs of orbits, one in eclipse and one just before ingress and one paired just after egress with COS G230L c2635 will search for changes to SO2, SO, and S2 emissions with time in and out of shadow. Lastly, one orbit of STIS G230LB eclipse imaging identifies the locations of any emissions searched for more sensitively with the COS G230L eclipse spectra. Total for Io eclipse spectra & imaging: 11 orbits. Io Surface Mapping: To search for changes in Io's surface coloration and the associated spectral features resulting from active volcanism we plan a few sets of visits spanning HST wavelengths. STIS G430L and G750L modes use the 52x0.05E1 aperture with 0.025" steps across Io's 0.9-1.2" disk, targeting the leading and trailing hemispheres largely spanned by PJ57 & PJ58 (planned later in Cy31), complementing the previous geometries of PID=15925, and capturing the entire Pele region (19S,225W) all with ~2" better spatial resolution. STIS G140L FUV spectral maps similarly use the 52x0.2D1 slit with 0.1" steps to cover the full disk with two orbits (needed for SNR) in each of 4 visits centered at orbital longitudes 45, 135, 225, and 315 deg. COS G130M c1055 mode spectra of Io's leading and trailing hemispheres investigate Io's extreme-UV albedo ratios with two orbits each. The two COS G230L observations pre-ingress and post-egress described above complete the spectral coverage story, but primarily indicate molecular gas absorptions rather than albedo. Total for Io surface mapping: 16 orbits. The PI Kurt Retherford has experience from leading one successful HST program as PI (ProgID=13805), several as U.S. administrative PI, and many more as CoI. He has a proven record of leading HST programs to successful publication (Retherford et al., AJ, 2019). As PI of the Europa Clipper UV Spectrograph (UVS), Dep. PI of JUICE-UVS, and PI of LRO-LAMP he has extensive spectroscopic and leadership expertise. Fran Bagenal is Co-PI, leading the team's model synthesis of numerous datasets from Hubble, Juno, JWST, Keck, and other ground-based observations. Lorenz Roth leads the team's European cohort, and the presentation of results in European venues. Roth has experience from leading five successful HST programs as PI, including a medium sized Europa program with similar scope of scheduling efforts and copious publications. Katherine de Kleer leads the JWST coordinated observations. She has experience with previous JWST Cycle 1 ERS observations of Io, leads a Cycle 2 JWST program observing Io, and extensive expertise in Keck and Alma observations of Io and the Jupiter system. Dr. Tracy Becker has experience with HST data analysis from STIS and COS, with Europa, Psyche, and other targets with expertise in UV surface reflectance measurements like those planned here. Nathaniel Cunningham is an expert on the COS instrument with detailed knowledge about the instrument characteristics, having been involved in its development and Callisto data analysis. Randy Gladstone is the PI of Juno-UVS, JUICE-UVS, and numerous joint Chandra-HST studies of Jupiter. Vincent Hue has experience leading the analysis of Juno-UVS Io Flux Tube footprint measurements and correlated variability with Io's plasma environment. Josh Kammer has extensive experience with the inversion of stellar occultation datasets into column densities, as for Pluto, MU69, Titan, and Saturn observational datasets. Philippa Molyneux has experience with HST data analysis from COS, STIS, and other spectroscopic instruments, with Galilean satellite programs specifically. Jonny Nichols has experience leading the analysis of HST Jupiter Io footprint spectral images and we will coordinate scheduling with his ongoing projects ProgID=16675/16989. Samantha Trumbo has experience with creating HST surface reflectance maps using step-scan image cubes with STIS like those we'll obtain with improved spatial resolution. Joachim Saur has experience in modelling moon-magnetospheric plasma interaction in the Jupiter system and was PI of several HST programs. Michael Velez is a graduate student at the University of Texas at San Antonio, with mentor Retherford, and presently analyzing Europa eclipse STIS G750M datasets. Matthew Burger, Vincent Dols, Eddie Nerney, Carl Schmidt, and Todd Smith all have extensive experience working together to constrain models using observations of Io, neutral clouds, and the plasma torus. Lori Feaga, Amanda Hendrix, Kandis Lea Jessup, Emmanuel Lellouch, Melissa McGrath, and John Spencer have a deep set of experience observing Io's atmosphere and auroral morphology with all planned HST modes. Shawn Brueshaber, Tommy Greathouse, Candy Hansen, Tom Momary, Alessandro Mura, and Glen Orton are Juno key personnel (as is Co-PI Bagenal). Solar System Astronomy 0 false true false false false false false SUPPORTED SOLAR SYSTEM YES Start at Io and scan both sides around it with STIS and in one direction away from it with COS to determine extent of detectable emissions several tens of arcseconds away from Io SATELLITE Io Neutral Cloud targeted STIS Step-scan set of three 2 arcsecond steps and a Sub-Jupiter pointed COS-Scan pattern STD=JUPITER STD=IO OLG 315 TO 45; STIS Step-scan & COS-Scan NOT OCC OF IO-NCLOUD-SUBJUPITER BY JUPITER FROM EARTH, SEP OF IO-NCLOUD-SUBJUPITER EUROPA FROM EARTH GT 10", SEP OF IO-NCLOUD-SUBJUPITER GANYMEDE FROM EARTH GT 10", SEP OF IO-NCLOUD-SUBJUPITER CALLISTO FROM EARTH GT 10", OLG OF IO-NCLOUD-SUBJUPITER BETWEEN 315 45 EARTH SOLAR SYSTEM YES SATELLITE Io Neutral Cloud STIS Step-scan & COS-Scan viewing Io's leading hemisphere STD=JUPITER STD=IO OLG 45 TO 135; STIS Step-scan & COS-Scan NOT OCC OF IO-NCLOUD-LEADING BY JUPITER FROM EARTH, SEP OF IO-NCLOUD-LEADING EUROPA FROM EARTH GT 10", SEP OF IO-NCLOUD-LEADING GANYMEDE FROM EARTH GT 10", SEP OF IO-NCLOUD-LEADING CALLISTO FROM EARTH GT 10", OLG OF IO-NCLOUD-LEADING BETWEEN 45 135 EARTH SOLAR SYSTEM YES SATELLITE Io Neutral Cloud STIS Step-scan & COS-Scan viewing Io's leading hemisphere STD=JUPITER STD=IO OLG 45 TO 135; STIS Step-scan & COS-Scan NOT OCC OF IO-NCLOUD-LEADING2 BY JUPITER FROM EARTH, SEP OF IO-NCLOUD-LEADING2 EUROPA FROM EARTH GT 10", SEP OF IO-NCLOUD-LEADING2 GANYMEDE FROM EARTH GT 10", SEP OF IO-NCLOUD-LEADING2 CALLISTO FROM EARTH GT 10", OLG OF IO-NCLOUD-LEADING BETWEEN 45 135 EARTH SOLAR SYSTEM YES SATELLITE Io Neutral Cloud STIS Step-scan & COS-Scan viewing Io's anti-Jupiter hemisphere STD=JUPITER STD=IO OLG 135 TO 225; STIS Step-scan & COS-Scan NOT OCC OF IO-NCLOUD-ANTIJUPITER BY JUPITER FROM EARTH, SEP OF IO-NCLOUD-ANTIJUPITER EUROPA FROM EARTH GT 10", SEP OF IO-NCLOUD-ANTIJUPITER GANYMEDE FROM EARTH GT 10", SEP OF IO-NCLOUD-ANTIJUPITER CALLISTO FROM EARTH GT 10", OLG OF IO-NCLOUD-ANTIJUPITER BETWEEN 135 225 EARTH SOLAR SYSTEM YES SATELLITE Io Neutral Cloud STIS Step-scan & COS-Scan viewing Io's trailing hemisphere STD=JUPITER STD=IO OLG 225 TO 315; STIS Step-scan & COS-Scan NOT OCC OF IO-NCLOUD-TRAILING BY JUPITER FROM EARTH, SEP OF IO-NCLOUD-TRAILING EUROPA FROM EARTH GT 10", SEP OF IO-NCLOUD-TRAILING GANYMEDE FROM EARTH GT 10", SEP OF IO-NCLOUD-TRAILING CALLISTO FROM EARTH GT 10", OLG OF IO-NCLOUD-TRAILING BETWEEN 225 315 EARTH SOLAR SYSTEM YES .. SATELLITE Io Plasma Torus Leading Hemisphere Scan STD=JUPITER STD=IO OLG 45 TO 135; STIS G140M Near-Io Torus Scan NOT OCC OF IO-PLASMATORUS-LEADING BY JUPITER FROM EARTH, SEP OF IO-PLASMATORUS-LEADING EUROPA FROM EARTH GT 10", SEP OF IO-PLASMATORUS-LEADING GANYMEDE FROM EARTH GT 10", SEP OF IO-PLASMATORUS-LEADING CALLISTO FROM EARTH GT 10", OLG OF IO-PLASMATORUS-LEADING BETWEEN 45 135 EARTH SOLAR SYSTEM YES .. SATELLITE Io Plasma Torus Trailing Hemisphere Scan STD=JUPITER STD=IO OLG 225 TO 315; STIS G140M Near-Io Torus Scan NOT OCC OF IO-PLASMATORUS-TRAILING BY JUPITER FROM EARTH, SEP OF IO-PLASMATORUS-TRAILING EUROPA FROM EARTH GT 10", SEP OF IO-PLASMATORUS-TRAILING GANYMEDE FROM EARTH GT 10", SEP OF IO-PLASMATORUS-TRAILING CALLISTO FROM EARTH GT 10", OLG OF IO-PLASMATORUS-TRAILING BETWEEN 225 315 EARTH SOLAR SYSTEM YES TORUS Io Neutral Cloud COS Stare with No Io at its orbital ansa point east of Jupiter (would be the leading/dawn-side) STD=JUPITER STD=CALLISTO TYPE=POS_ANGLE,RAD=35,ANG=260,REF=NORTH COS East Ansa Stare No Io NOT OCC OF NCLOUD-EASTANSA BY JUPITER FROM EARTH, SEP OF NCLOUD-EASTANSA IO FROM EARTH GT 10", SEP OF NCLOUD-EASTANSA EUROPA FROM EARTH GT 10", SEP OF NCLOUD-EASTANSA GANYMEDE FROM EARTH GT 10" EARTH SOLAR SYSTEM YES TORUS Io Neutral Cloud COS Stare with No Io at its orbital ansa point wast of Jupiter (would be the trailing/dusk-side) STD=JUPITER TYPE=TORUS,LONG=90,LAT=0,RAD=4.22e5,POLE_LONG=0,POLE_LAT=90 COS West Ansa Stare No Io NOT OCC OF NCLOUD-WESTANSA BY JUPITER FROM EARTH, NOT ECL P PARTIAL OF NCLOUD-WESTANSA BY IO FROM EARTH, NOT ECL P PARTIAL OF NCLOUD-WESTANSA BY EUROPA FROM EARTH, NOT ECL P PARTIAL OF NCLOUD-WESTANSA BY GANYMEDE FROM EARTH, NOT ECL P PARTIAL OF NCLOUD-WESTANSA BY CALLISTO FROM EARTH, SEP OF NCLOUD-WESTANSA IO FROM EARTH GT 10", SEP OF NCLOUD-WESTANSA EUROPA FROM EARTH GT 10", SEP OF NCLOUD-WESTANSA GANYMEDE FROM EARTH GT 10", SEP OF NCLOUD-WESTANSA CALLISTO FROM EARTH GT 10", OLG OF NCLOUD-WESTANSA BETWEEN 260 280 EARTH SOLAR SYSTEM YES SATELLITE Io Neutral Cloud COS Stare viewing Io's trailing hemisphere STD=JUPITER STD=IO OLG 225 TO 315; COS Io Stare NOT OCC OF IO-NCLOUD-TRAILING-NUV BY JUPITER FROM EARTH, SEP OF IO-NCLOUD-TRAILING-NUV EUROPA FROM EARTH GT 10", SEP OF IO-NCLOUD-TRAILING-NUV GANYMEDE FROM EARTH GT 10", SEP OF IO-NCLOUD-TRAILING-NUV CALLISTO FROM EARTH GT 10" EARTH SOLAR SYSTEM YES SATELLITE Europa Neutral Cloud STIS Step-scan & COS-Scan viewing Europa's leading hemisphere STD=JUPITER TYPE=TORUS,LONG=270,LAT=0,RAD=6.65e5,POLE_LONG=0,POLE_LAT=90 OLG 45 TO 135; STIS Stare & COS-Scan OLG OF EUROPA-NCLOUD-EASTANSA BETWEEN 45 135, NOT OCC OF EUROPA-NCLOUD-EASTANSA BY JUPITER FROM EARTH, NOT ECL P PARTIAL OF EUROPA-NCLOUD-EASTANSA BY IO FROM EARTH, NOT ECL P PARTIAL OF EUROPA-NCLOUD-EASTANSA BY EUROPA FROM EARTH, NOT ECL P PARTIAL OF EUROPA-NCLOUD-EASTANSA BY GANYMEDE FROM EARTH, NOT ECL P PARTIAL OF EUROPA-NCLOUD-EASTANSA BY CALLISTO FROM EARTH, SEP OF EUROPA-NCLOUD-EASTANSA IO FROM EARTH GT 10", SEP OF EUROPA-NCLOUD-EASTANSA EUROPA FROM EARTH GT 10", SEP OF EUROPA-NCLOUD-EASTANSA GANYMEDE FROM EARTH GT 10", SEP OF EUROPA-NCLOUD-EASTANSA CALLISTO FROM EARTH GT 10" EARTH SOLAR SYSTEM YES SATELLITE Europa Neutral Cloud STIS Step-scan & COS-Scan viewing Europa's trailing hemisphere STD=JUPITER TYPE=TORUS,LONG=90,LAT=0,RAD=6.65e5,POLE_LONG=0,POLE_LAT=90 OLG 225 TO 315; STIS Stare & COS-Scan OLG OF EUROPA-NCLOUD-WESTANSA BETWEEN 225 315, NOT OCC OF EUROPA-NCLOUD-WESTANSA BY JUPITER FROM EARTH, NOT ECL P PARTIAL OF EUROPA-NCLOUD-WESTANSA BY IO FROM EARTH, NOT ECL P PARTIAL OF EUROPA-NCLOUD-WESTANSA BY EUROPA FROM EARTH, NOT ECL P PARTIAL OF EUROPA-NCLOUD-WESTANSA BY GANYMEDE FROM EARTH, NOT ECL P PARTIAL OF EUROPA-NCLOUD-WESTANSA BY CALLISTO FROM EARTH, SEP OF EUROPA-NCLOUD-WESTANSA IO FROM EARTH GT 10", SEP OF EUROPA-NCLOUD-WESTANSA EUROPA FROM EARTH GT 10", SEP OF EUROPA-NCLOUD-WESTANSA GANYMEDE FROM EARTH GT 10", SEP OF EUROPA-NCLOUD-WESTANSA CALLISTO FROM EARTH GT 10" EARTH SOLAR SYSTEM YES SATELLITE Io aurora STIS G140L 52x2 during Juno PJ57 STD=JUPITER STD=IO Juno Perijove 57 Dec 30, 2023 NOT OCC OF IO-AURORA-PJ57 BY JUPITER FROM EARTH, SEP OF IO-AURORA-PJ57 EUROPA FROM EARTH GT 10", SEP OF IO-AURORA-PJ57 GANYMEDE FROM EARTH GT 10", SEP OF IO-AURORA-PJ57 CALLISTO FROM EARTH GT 10" EARTH SOLAR SYSTEM YES SATELLITE Io aurora STIS G140L 52x2 during Juno PJ58 STD=JUPITER STD=IO Juno Perijove 58 Feb 3, 2023 NOT OCC OF IO-AURORA-PJ58 BY JUPITER FROM EARTH, SEP OF IO-AURORA-PJ58 EUROPA FROM EARTH GT 10", SEP OF IO-AURORA-PJ58 GANYMEDE FROM EARTH GT 10", SEP OF IO-AURORA-PJ58 CALLISTO FROM EARTH GT 10" EARTH SOLAR SYSTEM YES SATELLITE Io aurora STIS G140L 52x2 during Juno PJ59 STD=JUPITER STD=IO Juno Perijove 59 Mar 7, 2023 (close to Elong. 55 deg) NOT OCC OF IO-AURORA-PJ59 BY JUPITER FROM EARTH, SEP OF IO-AURORA-PJ59 EUROPA FROM EARTH GT 10", SEP OF IO-AURORA-PJ59 GANYMEDE FROM EARTH GT 10", SEP OF IO-AURORA-PJ59 CALLISTO FROM EARTH GT 10" EARTH SOLAR SYSTEM YES SATELLITE Io aurora STIS G140L 52x2 during Juno PJ64 STD=JUPITER STD=IO Juno Perijove 64 Aug 18, 2024 NOT OCC OF IO-AURORA-PJ64 BY JUPITER FROM EARTH, SEP OF IO-AURORA-PJ64 EUROPA FROM EARTH GT 10", SEP OF IO-AURORA-PJ64 GANYMEDE FROM EARTH GT 10", SEP OF IO-AURORA-PJ64 CALLISTO FROM EARTH GT 10" EARTH SOLAR SYSTEM YES DWARF-PLANET Io aurora STIS G140L 52x2 during Juno PJ65 STD=JUPITER STD=IO Juno Perijove 66 Oct 22, 2024 NOT OCC OF IO-AURORA-PJ66 BY JUPITER FROM EARTH, SEP OF IO-AURORA-PJ66 EUROPA FROM EARTH GT 10", SEP OF IO-AURORA-PJ66 GANYMEDE FROM EARTH GT 10", SEP OF IO-AURORA-PJ66 CALLISTO FROM EARTH GT 10" EARTH SOLAR SYSTEM YES SATELLITE Io aurora STIS G140L 52x2 during Juno-UVS Coordinated Obs. 1 STD=JUPITER STD=IO Juno-UVS Near-Jupiter Io Observations PJ57 NOT OCC OF IO-AURORA-UVS1 BY JUPITER FROM EARTH, SEP OF IO-AURORA-UVS1 EUROPA FROM EARTH GT 10", SEP OF IO-AURORA-UVS1 GANYMEDE FROM EARTH GT 10", SEP OF IO-AURORA-UVS1 CALLISTO FROM EARTH GT 10" EARTH SOLAR SYSTEM YES Originally the aim was to observe Io emerging from eclipse. Due to the restricted field of regard for HST, egress can not be observed in cycle 32 and we therefore changed the constraints to ingress / eclipse SATELLITE Io aurora STIS G140L 52x2 during Juno-UVS Coordinated Obs. 2 STD=JUPITER STD=IO Juno-UVS Near-Jupiter Io Observations PJ59 NOT OCC OF IO-AURORA-UVS2-ECLIPSE BY JUPITER FROM EARTH, OLG OF IO-AURORA-UVS2-ECLIPSE FROM EARTH BETWEEN 330 360 EARTH SOLAR SYSTEM YES This orbital perijove away from Io provides improved Juno-UVS datasets, owing to less radiation environment at the time of planned distant observations . SATELLITE Io aurora STIS G140L 52x2 during Juno-UVS Coordinated Obs. 3 STD=JUPITER STD=IO Juno-UVS Near-Jupiter Io Observations PJ65 NOT OCC OF IO-AURORA-UVS3 BY JUPITER FROM EARTH, SEP OF IO-AURORA-UVS3 EUROPA FROM EARTH GT 10", SEP OF IO-AURORA-UVS3 GANYMEDE FROM EARTH GT 10", SEP OF IO-AURORA-UVS3 CALLISTO FROM EARTH GT 10" EARTH SOLAR SYSTEM YES Dither pattern from Sparks Europa plume imaging program SATELLITE Io transiting Jupiter with STIS FUV imaging STD=JUPITER STD=IO Jupiter v-magnitude -2.4+/-0.4; Io OLG 180+/-5; STIS FUV NOT OCC OF IO-TRANSIT-FUV BY JUPITER FROM EARTH, SEP OF IO-TRANSIT-FUV EUROPA FROM EARTH GT 10", SEP OF IO-TRANSIT-FUV GANYMEDE FROM EARTH GT 10", SEP OF IO-TRANSIT-FUV CALLISTO FROM EARTH GT 10", TRANSIT OF IO-TRANSIT-FUV ACROSS JUPITER FROM EARTH, OLG OF IO-TRANSIT-FUV FROM EARTH BETWEEN 175 185 EARTH SOLAR SYSTEM YES Skip a Level 3 or dither pattern from Sparks Europa plume imaging program - they saw a drift and this method didn't seem to work as hoped for. SATELLITE Io transiting Jupiter with STIS FUV imaging STD=JUPITER STD=IO Jupiter v-magnitude -2.4+/-0.4; Io OLG 180+/-5; STIS FUV TRANSIT OF IO-TRANSIT-FUV2 ACROSS JUPITER FROM EARTH, OLG OF IO-TRANSIT-FUV FROM EARTH BETWEEN 175 185, NOT OCC OF IO-TRANSIT-FUV2 BY JUPITER FROM EARTH, SEP OF IO-TRANSIT-FUV2 EUROPA FROM EARTH GT 10", SEP OF IO-TRANSIT-FUV2 GANYMEDE FROM EARTH GT 10", SEP OF IO-TRANSIT-FUV2 CALLISTO FROM EARTH GT 10" EARTH SOLAR SYSTEM YES No Dither pattern SATELLITE Io transiting Jupiter with STIS NUV imaging STD=JUPITER STD=IO Jupiter v-magnitude -2.4+/-0.4; Io OLG 180+/-5; STIS FUV TRANSIT OF IO-TRANSIT-FUV ACROSS JUPITER FROM EARTH, OLG OF IO-TRANSIT-FUV FROM EARTH BETWEEN 175 185, NOT OCC OF IO-TRANSIT-NUV4 BY JUPITER FROM EARTH, SEP OF IO-TRANSIT-NUV4 EUROPA FROM EARTH GT 10", SEP OF IO-TRANSIT-NUV4 GANYMEDE FROM EARTH GT 10", SEP OF IO-TRANSIT-NUV4 CALLISTO FROM EARTH GT 10" EARTH SOLAR SYSTEM YES Could be 1 Io orbit later/earlier, want to avoid Jupiter limb with 25" fov of aperture but still have Io limb context ~similar to transit OLG Use same artificial satellite dither pattern used for IO-TRANSIT-FUV SATELLITE Io just after transiting Jupiter with STIS FUV imaging STD=JUPITER STD=IO Jupiter v-magnitude -2.4+/-0.4; Io OLG 180+/-5; STIS FUV NOT OCC OF IO-POSTTRANSIT-FUV BY JUPITER FROM EARTH, SEP OF IO-POSTTRANSIT-FUV EUROPA FROM EARTH GT 10", SEP OF IO-POSTTRANSIT-FUV GANYMEDE FROM EARTH GT 10", SEP OF IO-POSTTRANSIT-FUV CALLISTO FROM EARTH GT 10", NOT TRANSIT OF IO-POSTTRANSIT-FUV ACROSS JUPITER FROM EARTH EARTH SOLAR SYSTEM YES Could be 1 Io orbit later/earlier, want to avoid Jupiter limb with 25" fov of aperture but still have Io limb context ~similar to transit OLG Skip a Level 3 or dither pattern SATELLITE Io just after transiting Jupiter with STIS FUV imaging STD=JUPITER STD=IO Jupiter v-magnitude -2.4+/-0.4; Io OLG 180+/-5; STIS FUV NOT TRANSIT OF IO-POSTTRANSIT-FUV ACROSS JUPITER FROM EARTH, NOT OCC OF IO-POSTTRANSIT-FUV2 BY JUPITER FROM EARTH, SEP OF IO-POSTTRANSIT-FUV2 EUROPA FROM EARTH GT 10", SEP OF IO-POSTTRANSIT-FUV2 GANYMEDE FROM EARTH GT 10", SEP OF IO-POSTTRANSIT-FUV2 CALLISTO FROM EARTH GT 10" EARTH SOLAR SYSTEM YES SATELLITE Io transiting Jupiter with WFC3 imaging STD=JUPITER STD=IO Jupiter v-magnitude -2.4+/-0.4; OLG 180+/-5; STIS FUV NOT OCC OF IO-TRANSIT-WFC3 BY JUPITER FROM EARTH, SEP OF IO-TRANSIT-WFC3 EUROPA FROM EARTH GT 3", SEP OF IO-TRANSIT-WFC3 GANYMEDE FROM EARTH GT 3", SEP OF IO-TRANSIT-WFC3 CALLISTO FROM EARTH GT 3", TRANSIT OF IO-TRANSIT-WFC3 ACROSS JUPITER FROM EARTH EARTH SOLAR SYSTEM YES SATELLITE Io transiting Jupiter with STIS NUV spectral imaging STD=JUPITER STD=IO Jupiter v-magnitude -2.4+/-0.4; OLG 180+/-5; STIS FUV NOT OCC OF IO-TRANSIT-STISNUV BY JUPITER FROM EARTH, SEP OF IO-TRANSIT-STISNUV EUROPA FROM EARTH GT 10", SEP OF IO-TRANSIT-STISNUV GANYMEDE FROM EARTH GT 10", SEP OF IO-TRANSIT-STISNUV CALLISTO FROM EARTH GT 10", TRANSIT OF IO-TRANSIT-STISNUV ACROSS JUPITER FROM EARTH EARTH SOLAR SYSTEM YES SATELLITE Io transiting Jupiter with STIS NUV spectral imaging STD=JUPITER STD=IO Jupiter v-magnitude -2.4+/-0.4; OLG 180+/-5; STIS FUV NOT OCC OF IO-TRANSIT-STISNUV2 BY JUPITER FROM EARTH, SEP OF IO-TRANSIT-STISNUV2 EUROPA FROM EARTH GT 10", SEP OF IO-TRANSIT-STISNUV2 GANYMEDE FROM EARTH GT 10", SEP OF IO-TRANSIT-STISNUV2 CALLISTO FROM EARTH GT 10", TRANSIT OF IO ACROSS JUPITER FROM EARTH EARTH SOLAR SYSTEM YES SATELLITE Io transiting Jupiter with COS NUV spectroscopy STD=JUPITER STD=IO Jupiter v-magnitude -2.4+/-0.4; OLG 180+/-5; STIS FUV NOT OCC OF IO-TRANSIT-COSNUV BY JUPITER FROM EARTH, SEP OF IO-TRANSIT-COSNUV EUROPA FROM EARTH GT 10", SEP OF IO-TRANSIT-COSNUV GANYMEDE FROM EARTH GT 10", SEP OF IO-TRANSIT-COSNUV CALLISTO FROM EARTH GT 10" EARTH SOLAR SYSTEM YES Copy of target 44 to be used with visit 53 SATELLITE Io transiting Jupiter with COS NUV spectroscopy STD=JUPITER STD=IO Jupiter v-magnitude -2.4+/-0.4; OLG 180+/-5; STIS FUV NOT OCC OF IO-TRANSIT-COSNUV2 BY JUPITER FROM EARTH, SEP OF IO-TRANSIT-COSNUV2 EUROPA FROM EARTH GT 10", SEP OF IO-TRANSIT-COSNUV2 GANYMEDE FROM EARTH GT 10", SEP OF IO-TRANSIT-COSNUV2 CALLISTO FROM EARTH GT 5", SEP OF IO JUPITER FROM EARTH LT 5" EARTH SOLAR SYSTEM YES SATELLITE Io after transiting Jupiter with COS NUV spectroscopy STD=JUPITER STD=IO Jupiter v-magnitude -2.4+/-0.4; OLG 180+/-5; STIS FUV NOT OCC OF IO-POSTTRANSIT-COSNUV BY JUPITER FROM EARTH, SEP OF IO-POSTTRANSIT-COSNUV EUROPA FROM EARTH GT 10", SEP OF IO-POSTTRANSIT-COSNUV GANYMEDE FROM EARTH GT 10", SEP OF IO-POSTTRANSIT-COSNUV CALLISTO FROM EARTH GT 10" EARTH SOLAR SYSTEM YES Target OLG window is determined based on: -1.769 day orbital period of Io -umbral eclipse begins at TBC +/-0.1 degrees OLG measured from Sun in Aug 2024 - Sep 2024 -3000s exposure time available in the second orbit. -want to get all of Io in eclipse Override default SEP between Io and Jupiter to allow observation in/near eclipse SATELLITE Io in eclipse by Jupiter with STIS VIS spectral imaging STD=JUPITER STD=IO TYPE=PGRAPHIC,LONG=308.79,LAT=13.01 OLG 0+/-20; In Jupiter Shadow, but not occulted ECL U FULL OF IO-ECLIPSE-VIS-LOKI-STARE BY JUPITER FROM EARTH, NOT OCC OF IO-ECLIPSE-VIS-LOKI-STARE BY IO FROM EARTH, NOT OCC OF IO-ECLIPSE-VIS-LOKI-STARE BY JUPITER FROM EARTH, SEP OF IO-ECLIPSE-VIS-LOKI-STARE EUROPA FROM EARTH GT 10", SEP OF IO-ECLIPSE-VIS-LOKI-STARE GANYMEDE FROM EARTH GT 10", SEP OF IO-ECLIPSE-VIS-LOKI-STARE CALLISTO FROM EARTH GT 10" EARTH SOLAR SYSTEM YES Target OLG window is determined based on: -1.769 day orbital period of Io -umbral eclipse begins at TBC +/-0.1 degrees OLG measured from Sun in Aug 2024 - Sep 2024 -3000s exposure time available in the second orbit. -want to get all of Io in eclipse Override default SEP between Io and Jupiter to allow observation in/near eclipse OFFSET Io in eclipse by Jupiter with STIS VIS spectral imaging STD=JUPITER STD=IO TYPE=PGRAPHIC,LONG=308.79,LAT=13.01 OLG 0+/-20; In Jupiter Shadow, but not occulted ECL U FULL OF IO-ECLIPSE-VIS-LOKI-SCAN BY JUPITER FROM EARTH, NOT OCC OF IO-ECLIPSE-VIS-LOKI-SCAN BY IO FROM EARTH, NOT OCC OF IO-ECLIPSE-VIS-LOKI-SCAN BY JUPITER FROM EARTH, SEP OF IO-ECLIPSE-VIS-LOKI-SCAN EUROPA FROM EARTH GT 10", SEP OF IO-ECLIPSE-VIS-LOKI-SCAN GANYMEDE FROM EARTH GT 10", SEP OF IO-ECLIPSE-VIS-LOKI-SCAN CALLISTO FROM EARTH GT 10" EARTH SOLAR SYSTEM YES SATELLITE Io in eclipse by Jupiter with STIS VIS spectral imaging STD=JUPITER STD=IO OLG 0+/-20; In Jupiter Shadow, but not occulted NOT OCC OF IO-ECLIPSE-VIS-S2 BY JUPITER FROM EARTH, SEP OF IO-ECLIPSE-VIS-S2 EUROPA FROM EARTH GT 10", SEP OF IO-ECLIPSE-VIS-S2 GANYMEDE FROM EARTH GT 10", SEP OF IO-ECLIPSE-VIS-S2 CALLISTO FROM EARTH GT 10", ECL U FULL OF IO-ECLIPSE-VIS-S2 BY JUPITER FROM EARTH EARTH SOLAR SYSTEM YES SATELLITE Io in eclipse by Jupiter with STIS VIS spectral imaging STD=JUPITER STD=IO OLG 0+/-20; In Jupiter Shadow, but not occulted NOT OCC OF IO-ECLIPSE-VIS-NA-SCAN BY JUPITER FROM EARTH, SEP OF IO-ECLIPSE-VIS-NA-SCAN EUROPA FROM EARTH GT 10", SEP OF IO-ECLIPSE-VIS-NA-SCAN GANYMEDE FROM EARTH GT 10", SEP OF IO-ECLIPSE-VIS-NA-SCAN CALLISTO FROM EARTH GT 10", ECL U FULL OF IO-ECLIPSE-VIS-NA-SCAN BY JUPITER FROM EARTH EARTH SOLAR SYSTEM YES Target OLG window is determined based on: -1.769 day orbital period of Io -umbral eclipse begins at TBC +/-0.1 degrees OLG measured from Sun in Aug 2024 - Sep 2024 -3000s exposure time available in the second orbit. -want to get all of Io in eclipse Override default SEP between Io and Jupiter to allow observation in/near eclipse SATELLITE Io in eclipse by Jupiter with STIS VIS spectral imaging STD=JUPITER STD=IO OLG 0+/-20; In Jupiter Shadow, but not occulted NOT OCC OF IO-ECLIPSE-VIS-HALPHA BY JUPITER FROM EARTH, SEP OF IO-ECLIPSE-VIS-HALPHA EUROPA FROM EARTH GT 10", SEP OF IO-ECLIPSE-VIS-HALPHA GANYMEDE FROM EARTH GT 10", SEP OF IO-ECLIPSE-VIS-HALPHA CALLISTO FROM EARTH GT 10", ECL U FULL OF IO-ECLIPSE-VIS-HALPHA BY JUPITER FROM EARTH EARTH SOLAR SYSTEM YES SATELLITE Io in eclipse by Jupiter with STIS VIS spectral imaging STD=JUPITER STD=IO OLG 0+/-20; In Jupiter Shadow, but not occulted NOT OCC OF IO-ECLIPSE-VIS-K BY JUPITER FROM EARTH, SEP OF IO-ECLIPSE-VIS-K EUROPA FROM EARTH GT 10", SEP OF IO-ECLIPSE-VIS-K GANYMEDE FROM EARTH GT 10", SEP OF IO-ECLIPSE-VIS-K CALLISTO FROM EARTH GT 10", ECL U FULL OF IO-ECLIPSE-VIS-K BY JUPITER FROM EARTH EARTH SOLAR SYSTEM YES SATELLITE Io in eclipse by Jupiter with COS NUV spectroscopy STD=JUPITER STD=IO OLG 0+/-20; Entering Jupiter Shadow, not occulted NOT OCC OF IO-ECLIPSE-INGRESS-COS-NUV BY JUPITER FROM EARTH, SEP OF IO-ECLIPSE-INGRESS-COS-NUV EUROPA FROM EARTH GT 10", SEP OF IO-ECLIPSE-INGRESS-COS-NUV GANYMEDE FROM EARTH GT 10", SEP OF IO-ECLIPSE-INGRESS-COS-NUV CALLISTO FROM EARTH GT 10", ECL P FULL OF IO-ECLIPSE-INGRESS-COS-NUV BY JUPITER FROM EARTH EARTH SOLAR SYSTEM YES SATELLITE Io in eclipse by Jupiter with COS NUV spectroscopy STD=JUPITER STD=IO OLG 0+/-20; Exiting Jupiter Shadow, when not occulted NOT OCC OF IO-ECLIPSE-EGRESS-COS-NUV BY JUPITER FROM EARTH, SEP OF IO-ECLIPSE-EGRESS-COS-NUV EUROPA FROM EARTH GT 10", SEP OF IO-ECLIPSE-EGRESS-COS-NUV GANYMEDE FROM EARTH GT 10", SEP OF IO-ECLIPSE-EGRESS-COS-NUV CALLISTO FROM EARTH GT 10" EARTH SOLAR SYSTEM YES Is context for COS eclipse data (IO-ECLIPSE-INGRESS-COS-NUV and IO-ECLIPSE-INGRESS-COS-NUV) and should be linked in time one Io orbit before/after SATELLITE Io in eclipse by Jupiter with STIS NUV spectral imaging STD=JUPITER STD=IO OLG 0+/-20; In Jupiter Shadow, but not occulted NOT OCC OF IO-ECLIPSE-STIS-NUV BY JUPITER FROM EARTH, SEP OF IO-ECLIPSE-STIS-NUV EUROPA FROM EARTH GT 10", SEP OF IO-ECLIPSE-STIS-NUV GANYMEDE FROM EARTH GT 10", SEP OF IO-ECLIPSE-STIS-NUV CALLISTO FROM EARTH GT 10", ECL U FULL OF IO-ECLIPSE-STIS-NUV BY JUPITER FROM EARTH EARTH SOLAR SYSTEM YES Was OLG 80 TO 100 but expanded to help with scheduling. SATELLITE SATELLITE IO STD=JUPITER STD=IO OLG 75 TO 105; STIS with 52x0.05 slit scans at half-slit sampling NOT OCC OF IO-SURFACE-STIS-VIS-LEADING BY JUPITER FROM EARTH, SEP OF IO-SURFACE-STIS-VIS-LEADING EUROPA FROM EARTH GT 10", SEP OF IO-SURFACE-STIS-VIS-LEADING GANYMEDE FROM EARTH GT 10", SEP OF IO-SURFACE-STIS-VIS-LEADING CALLISTO FROM EARTH GT 10", CML OF IO-SURFACE-STIS-VIS-LEADING FROM EARTH BETWEEN 75 105 EARTH SOLAR SYSTEM YES Was OLG 260 TO 280 but expanded to help with scheduling. SATELLITE SATELLITE IO STD=JUPITER STD=IO OLG 255 TO 285; STIS with 52x0.05 slit scans at half-slit sampling NOT OCC OF IO-SURFACE-STIS-VIS-TRAILING BY JUPITER FROM EARTH, SEP OF IO-SURFACE-STIS-VIS-TRAILING EUROPA FROM EARTH GT 10", SEP OF IO-SURFACE-STIS-VIS-TRAILING GANYMEDE FROM EARTH GT 10", SEP OF IO-SURFACE-STIS-VIS-TRAILING CALLISTO FROM EARTH GT 10", CML OF IO-SURFACE-STIS-VIS-TRAILING FROM EARTH BETWEEN 255 285 EARTH SOLAR SYSTEM YES Was OLG 260 TO 280 but expanded to help with scheduling. Copy of target 81 to be used with visit 91. SATELLITE SATELLITE IO STD=JUPITER STD=IO OLG 255 TO 285; STIS with 52x0.05 slit scans at half-slit sampling NOT OCC OF IO-SURFACE-STIS-VIS-TRAILING2 BY JUPITER FROM EARTH, SEP OF IO-SURFACE-STIS-VIS-TRAILING2 EUROPA FROM EARTH GT 10", SEP OF IO-SURFACE-STIS-VIS-TRAILING2 GANYMEDE FROM EARTH GT 10", SEP OF IO-SURFACE-STIS-VIS-TRAILING2 CALLISTO FROM EARTH GT 10", CML OF IO-SURFACE-STIS-VIS-TRAILING FROM EARTH BETWEEN 255 285 EARTH SOLAR SYSTEM YES Was CML 45+/-10 but expanded to help with scheduling. SATELLITE Io UV reflectance STIS G140L 52x0.2 step-scan image STD=JUPITER STD=IO CML 45+/-15; STIS with 52x0.2 slit scans NOT OCC OF IO-SURFACE-STIS-FUV-45 BY JUPITER FROM EARTH, SEP OF IO-SURFACE-STIS-FUV-45 EUROPA FROM EARTH GT 10", SEP OF IO-SURFACE-STIS-FUV-45 GANYMEDE FROM EARTH GT 10", SEP OF IO-SURFACE-STIS-FUV-45 CALLISTO FROM EARTH GT 10", CML OF IO-SURFACE-STIS-FUV-45 FROM EARTH BETWEEN 30 63 EARTH SOLAR SYSTEM YES Was CML 135+/-10 but expanded to help with scheduling. SATELLITE Io UV reflectance STIS G140L 52x0.2 step-scan image STD=JUPITER STD=IO CML 135+/-15; STIS with 52x0.2 slit scans NOT OCC OF IO-SURFACE-STIS-FUV-135 BY JUPITER FROM EARTH, SEP OF IO-SURFACE-STIS-FUV-135 EUROPA FROM EARTH GT 10", SEP OF IO-SURFACE-STIS-FUV-135 GANYMEDE FROM EARTH GT 10", SEP OF IO-SURFACE-STIS-FUV-135 CALLISTO FROM EARTH GT 10", CML OF IO-SURFACE-STIS-FUV-135 FROM EARTH BETWEEN 120 150 EARTH SOLAR SYSTEM YES Was CML 225+/-10 but expanded to help with scheduling. SATELLITE Io UV reflectance STIS G140L 52x0.2 step-scan image STD=JUPITER STD=IO CML 225+/-15; STIS with 52x0.2 slit scans NOT OCC OF IO-SURFACE-STIS-FUV-225 BY JUPITER FROM EARTH, SEP OF IO-SURFACE-STIS-FUV-225 EUROPA FROM EARTH GT 10", SEP OF IO-SURFACE-STIS-FUV-225 GANYMEDE FROM EARTH GT 10", SEP OF IO-SURFACE-STIS-FUV-225 CALLISTO FROM EARTH GT 10", CML OF IO-SURFACE-STIS-FUV-225 FROM EARTH BETWEEN 210 240 EARTH SOLAR SYSTEM YES Was CML 315+/-10 but expanded to help with scheduling. SATELLITE Io UV reflectance STIS G140L 52x0.2 step-scan image STD=JUPITER STD=IO CML 315+/-15; STIS with 52x0.2 slit scans NOT OCC OF IO-SURFACE-STIS-FUV-315 BY JUPITER FROM EARTH, SEP OF IO-SURFACE-STIS-FUV-315 EUROPA FROM EARTH GT 10", SEP OF IO-SURFACE-STIS-FUV-315 GANYMEDE FROM EARTH GT 10", SEP OF IO-SURFACE-STIS-FUV-315 CALLISTO FROM EARTH GT 10", CML OF IO-SURFACE-STIS-FUV-315 FROM EARTH BETWEEN 300 330 EARTH SOLAR SYSTEM YES SATELLITE Io EUV reflectance COS spectra STD=JUPITER STD=IO OLG 45 TO 135; COS EUV NOT OCC OF IO-SURFACE-COS-LEADING BY JUPITER FROM EARTH, SEP OF IO-SURFACE-COS-LEADING EUROPA FROM EARTH GT 10", SEP OF IO-SURFACE-COS-LEADING GANYMEDE FROM EARTH GT 10", SEP OF IO-SURFACE-COS-LEADING CALLISTO FROM EARTH GT 10", OLG OF IO-SURFACE-COS-LEADING BETWEEN 45 135 EARTH SOLAR SYSTEM YES SATELLITE Io EUV reflectance COS spectra STD=JUPITER STD=IO OLG 225 TO 315; COS EUV NOT OCC OF IO-SURFACE-COS-TRAILING BY JUPITER FROM EARTH, SEP OF IO-SURFACE-COS-TRAILING EUROPA FROM EARTH GT 10", SEP OF IO-SURFACE-COS-TRAILING GANYMEDE FROM EARTH GT 10", SEP OF IO-SURFACE-COS-TRAILING CALLISTO FROM EARTH GT 10", OLG OF IO-SURFACE-COS-TRAILING BETWEEN 225 315 EARTH SOLAR SYSTEM YES Could use Ganymede or Callisto instead If Jupiter max angular diam is ~48" during Cycle 31, and this acquisition is used for Io in eclipse/transit, need Europa to be separated from Io by at least 24", but that puts it right on Jupiter limb, so I doubled that angular distance Added observing restriction of Europa transiting Jupiter as well SATELLITE For transit/eclipse observations where acquisition images of Io are not possible STD=JUPITER STD=EUROPA NOT OCC OF EUROPA-ACQ BY JUPITER FROM EARTH, SEP OF EUROPA-ACQ IO FROM EARTH GT 50", SEP OF EUROPA-ACQ GANYMEDE FROM EARTH GT 10", SEP OF EUROPA-ACQ CALLISTO FROM EARTH GT 10", NOT TRANSIT OF EUROPA-ACQ ACROSS JUPITER FROM EARTH EARTH SOLAR SYSTEM YES Could use Ganymede or Callisto instead If Jupiter max angular diam is ~48" during Cycle 31, and this acquisition is used for Io in eclipse/transit, need Europa to be separated from Io by at least 24", but that puts it right on Jupiter limb, so I doubled that angular distance Added observing restriction of Europa transiting Jupiter as well Duplicate of target 100. SATELLITE For transit/eclipse observations where acquisition images of Io are not possible STD=JUPITER STD=EUROPA NOT OCC OF EUROPA-ACQ2 BY JUPITER FROM EARTH, SEP OF EUROPA-ACQ2 IO FROM EARTH GT 50", SEP OF EUROPA-ACQ2 GANYMEDE FROM EARTH GT 10", SEP OF EUROPA-ACQ2 CALLISTO FROM EARTH GT 10", NOT TRANSIT OF EUROPA-ACQ ACROSS JUPITER FROM EARTH EARTH SOLAR SYSTEM YES Could use Ganymede or Callisto instead If Jupiter max angular diam is ~48" during Cycle 31, and this acquisition is used for Io in eclipse/transit, need Europa to be separated from Io by at least 24", but that puts it right on Jupiter limb, so I doubled that angular distance Added observing restriction of Europa transiting Jupiter as well Duplicate of target 199 & 202. SATELLITE For transit/eclipse observations where acquisition images of Io are not possible STD=JUPITER STD=EUROPA NOT OCC OF EUROPA-ACQ3 BY JUPITER FROM EARTH, SEP OF EUROPA-ACQ3 IO FROM EARTH GT 50", SEP OF EUROPA-ACQ3 GANYMEDE FROM EARTH GT 10", SEP OF EUROPA-ACQ3 CALLISTO FROM EARTH GT 10", NOT TRANSIT OF EUROPA-ACQ ACROSS JUPITER FROM EARTH EARTH SOLAR SYSTEM YES SATELLITE Io transiting Jupiter with COS NUV spectroscopy STD=JUPITER STD=IO Jupiter v-magnitude -2.4+/-0.4; OLG 180+/-5; STIS FUV NOT OCC OF IO-ACQ BY JUPITER FROM EARTH, SEP OF IO-ACQ EUROPA FROM EARTH GT 10", SEP OF IO-ACQ GANYMEDE FROM EARTH GT 10", SEP OF IO-ACQ CALLISTO FROM EARTH GT 10" EARTH SOLAR SYSTEM YES Could use Europa or Callisto instead SATELLITE For transit/eclipse observations where acquisition images of Io are not possible STD=JUPITER STD=GANYMEDE NOT OCC OF GANYMEDE-ACQ BY JUPITER FROM EARTH, SEP OF GANYMEDE-ACQ IO FROM EARTH GT 10", SEP OF GANYMEDE-ACQ EUROPA FROM EARTH GT 10", SEP OF GANYMEDE-ACQ CALLISTO FROM EARTH GT 10" EARTH COS/FUV Spectroscopic No No G130M 1327 STIS/FUV-MAMA Spectroscopic No No G140L 1425 COS/FUV Spectroscopic No No G130M 1327 STIS/FUV-MAMA Spectroscopic No No G140L 1425 COS/FUV Spectroscopic No No G130M 1327 STIS/FUV-MAMA Spectroscopic No No G140L 1425 COS/FUV Spectroscopic No No G130M 1327 STIS/FUV-MAMA Spectroscopic No No G140L 1425 COS/FUV Spectroscopic No No G130M 1327 COS/FUV Spectroscopic No No G130M 1327 COS/NUV Spectroscopic No No G230L 2950 COS/FUV Spectroscopic No No G130M 1327 STIS/FUV-MAMA Spectroscopic No No G140L 1425 COS/FUV Spectroscopic No No G130M 1327 STIS/FUV-MAMA Spectroscopic No No G140L 1425 STIS/FUV-MAMA Spectroscopic No No G140M 1272 STIS/FUV-MAMA Spectroscopic No No G140M 1272 STIS/FUV-MAMA Spectroscopic No No G140L 1425 STIS/FUV-MAMA Spectroscopic No No G140L 1425 STIS/FUV-MAMA Spectroscopic No No G140L 1425 STIS/FUV-MAMA Spectroscopic No No G140L 1425 STIS/FUV-MAMA Spectroscopic No No G140L 1425 STIS/FUV-MAMA Spectroscopic No No G140L 1425 STIS/FUV-MAMA Spectroscopic No No G140L 1425 STIS/FUV-MAMA Spectroscopic No No G140L 1425 STIS/FUV-MAMA Imaging No No F25QTZ STIS/FUV-MAMA Imaging No No F25QTZ WFC3/UVIS Imaging No No F225W WFC3/UVIS Imaging No No F280N WFC3/UVIS Imaging No No F336W WFC3/UVIS Imaging No No F343N WFC3/UVIS Imaging No No F390W WFC3/UVIS Imaging No No F475W WFC3/UVIS Imaging No No F555W STIS/NUV-MAMA Spectroscopic No No G230M 2095 STIS/NUV-MAMA Spectroscopic No No G230M 2659 COS/NUV Spectroscopic No No G225M 2217 COS/NUV Spectroscopic No No G225M 2217 STIS/CCD Spectroscopic No No G750L 7751 STIS/CCD Spectroscopic No No G750L 7751 STIS/CCD Spectroscopic No No G430M 4706 STIS/CCD Spectroscopic No No G750M 6094 STIS/CCD Spectroscopic No No G750M 6768 STIS/CCD Spectroscopic No No G750M 7795 COS/NUV Spectroscopic No No G230L 2635 COS/NUV Spectroscopic No No G230L 2635 STIS/NUV-MAMA Spectroscopic No No G230L 2376 STIS/CCD Spectroscopic No No G750L 7751 STIS/CCD Spectroscopic No No G430L 4300 STIS/CCD Spectroscopic No No G750L 7751 STIS/CCD Spectroscopic No No G430L 4300 STIS/FUV-MAMA Spectroscopic No No G140L 1425 STIS/FUV-MAMA Spectroscopic No No G140L 1425 STIS/FUV-MAMA Spectroscopic No No G140L 1425 STIS/FUV-MAMA Spectroscopic No No G140L 1425 COS/FUV Spectroscopic No No G130M 1055 COS/FUV Spectroscopic No No G130M 1055 POS-TARG MOSAIC DITHER 0.034 STIS-ALONG-SLIT false true 28 0.0 POS-TARG STIS-PERP-TO-SLIT 90.0 1 false POS-TARG MOSAIC DITHER 0.034 STIS-ALONG-SLIT false true 23 0.0 POS-TARG STIS-PERP-TO-SLIT 90.0 15 false POS-TARG MOSAIC DITHER 2.0 STIS offset by the 2" slit width for the near-Io neutral cloud scans. STIS-ALONG-SLIT false true 3 0.0 POS-TARG STIS-PERP-TO-SLIT 90.0 2 false CELESTIAL OTHER 5 COS offsets for the farthest-Io neutral cloud scans with custom pattern ~1 min * 2N each for 0pt (on Io), 5 RIo, 10 RIo, 20 RIo, and 40 RIo, and then dwell at 80 RIo for the remainder of an HST orbit (up to 20 min). Purpose is to identify furthest detectable emissions and understand distributions of escaping atmospheric gases. Directionality of the scan is best described in the Jupiter satellite orbital plane reference, or Ecliptic coordinates. A variable rate COS drift-scan would also achieve our goals, starting at higher angular rate than ending in a slew from 0 to 80 Io radii (roughly 80 arcsec) away.~1 min * 2N each for 0pt (on Io), 5 RIo, 10 RIo, 20 RIo, and 40 RIo, and then dwell at 80 RIo for the remainder of an HST orbit (up to 20 min). Two "LINE" entries, orthogonal to each other. 0 and 1, but -1 works fine too. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. LINE false false 6 0 LINE 3 false CELESTIAL OTHER 5 COS offsets for the farthest-Io neutral cloud scans with custom pattern ~1 min * 2N each for 0pt (on Io), 5 RIo, 10 RIo, 20 RIo, and 40 RIo, and then dwell at 80 RIo for the remainder of an HST orbit (up to 20 min). Purpose is to identify furthest detectable emissions and understand distributions of escaping atmospheric gases. Directionality of the scan is best described in the Jupiter satellite orbital plane reference, or Ecliptic coordinates. A variable rate COS drift-scan would also achieve our goals, starting at higher angular rate than ending in a slew from 0 to 80 Io radii (roughly 80 arcsec) away.~1 min * 2N each for 0pt (on Io), 5 RIo, 10 RIo, 20 RIo, and 40 RIo, and then dwell at 80 RIo for the remainder of an HST orbit (up to 20 min). Two "LINE" entries, orthogonal to each other. 0 and 1, but -1 works fine too. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. LINE false false 6 1 LINE 4 false POS-TARG MOSAIC DITHER 0.1 This pattern can begin offset from the target, or can begin on the target. The Target Position Requirements indicate how far (perpendicular to the slit) from the center of the target the slit pointing pattern should begin. STIS-ALONG-SLIT false true 4 0.0 POS-TARG STIS-PERP-TO-SLIT 90.0 5 false POS-TARG MOSAIC DITHER 0.2 For STIS NUV transit scan with central wavelength 2659. We'll aim for less spatial resolution than with pattern 5 and more coverage of the disk instead with five 0.2 arcsec steps instead of 4 at 0.1. The signal from Jupiter at this wavelength is likely too high with the 0.5" slit, so we need to use a narrower slit and more steps. Kurt reply: Using the G230M mode decreases throughput by increasing dispersion, so if you compared the flux from the G230L and 52x0.2 slit to infer this, then the x2 drop in throughput with M vs L should help account for that. Best to check with ETC, agree, and using a Jupiter spectrum not a solar analog. STIS-ALONG-SLIT false true 5 0.0 POS-TARG STIS-PERP-TO-SLIT 90.0 6 false POS-TARG MOSAIC DITHER 0.5 STIS offset by the 0.5" slit width for the near-Io plasma torus scans. Three steps covers 1.5 arcsec and almost all of near-Io features with less gap-time lost. STIS-ALONG-SLIT false true 3 0.0 POS-TARG STIS-PERP-TO-SLIT 90.0 7 false CELESTIAL OTHER 5 COS offsets for the near-Europa cloud scans with custom pattern ~10 min * 2N each for 0pt (on Europa), 5 arcsec (COS aperture size), and 10 arcsec. Purpose is to identify furthest detectable emissions in Hill sphere radius and understand distributions of escaping atmospheric gases. Directionality of the scan is best described in the Jupiter satellite orbital plane reference, or Ecliptic coordinates. A constant rate COS drift-scan would also achieve our goals. Two "LINE" entries, orthogonal to each other. 0 and 1, but -1 works fine too. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. LINE false false 3 0 LINE 8 false CELESTIAL OTHER 5 COS offsets for the near-Europa cloud scans with custom pattern ~10 min * 2N each for 0pt (on Eruopa), 5 arcsec (COS aperture size), and 10 arcsec. Purpose is to identify furthest detectable emissions in Hill sphere radius and understand distributions of escaping atmospheric gases. Directionality of the scan is best described in the Jupiter satellite orbital plane reference, or Ecliptic coordinates. A constant rate COS drift-scan would also achieve our goals. Two "LINE" entries, orthogonal to each other. 0 and 1, but -1 works fine too. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. LINE false false 3 1 LINE 9 false POS-TARG MOSAIC DITHER 0.1 STIS-ALONG-SLIT false false 3 0.0 POS-TARG STIS-PERP-TO-SLIT 90.0 10 false POS-TARG DITHER 0.135 Need to update angles with NPPA once scheduled. LINE false false 3 46.84 WFC3-UVIS-DITHER-LINE-3PT 11 false POS-TARG MOSAIC 3 For the COS-NUV Transit on-Jupiter measurements, searching for extended SO2 north (or south) of Io within the Hill sphere. LINE false false 2 1 LINE 12 false POS-TARG BACKGROUND 10 For the COS-NUV Transit on-Jupiter background measurements. Needs to be East of Io, covering where the Io exposure had previously been. LINE false false 2 0 LINE 13 false POS-TARG MOSAIC DITHER 0.1 This pattern can begin offset from the target, or can begin on the target. The Target Position Requirements indicate how far (perpendicular to the slit) from the center of the target the slit pointing pattern should begin. For IO-SURFACE-STIS-FUV to catch other half of disk in 2nd orbit, where first orbit uses pattern 5 with four step sub-exposures. STIS-ALONG-SLIT false true 5 0.0 POS-TARG STIS-PERP-TO-SLIT 90.0 14 false 1729104808302 Using ephemeris for target 17470-01-IO-NCLOUD-SUBJUPITER ephemeris data for target 17470-01-IO-NCLOUD-SUBJUPITER does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.121. ephemeris interval: 24.121 to 26.121 Timing link suitability includes constraints ([Group (01 1A) Within 0.1 days]) The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. 40.6 /System/Volumes/Data/solaris/user1/williamj/hst/work/cycle31/OP-cache/17470-v01.xml Scans are implemented using POS TARG positions with X = [0",2.5",5",10",20",40"] and Y = 0" for the second orbit, and of X = 0" and Y = [0",2.4",5",10",20",40"] for the first orbit. (One arcsecond is roughly two R_Io) We can change the signs of the x or y as needed to help scheduling (e.g., avoiding Jupiter in sub- and anti- cases). Since the POS TARG offsets occur in HST coordinates rather than ecliptic or Jupiter satellite plane coordinates, the orientat and NPPA of the spacecraft will naturally vary for all the different sets. That'll be ok, and precludes us from specifying negative offest values. 1730750186000 251.52222138190473 (Tic-Visit :proposal-id 17470 :visit-id "01" :proposal-version -1 :trans-version "20240627" :date "16-Oct-2024 14:53:28.0" :trans-errors '(:WARNINGS 8 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 226272 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "01" :obset-id "01" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "01" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2054 :al-overhead-at-end 0 :internal-dur-at-end 76 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2436.0 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "01" :orbit-number 2 :pcs-time 380 :si-vis-utilization 1977 :al-overhead-at-end 0 :internal-dur-at-end 417 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2436.0 :pcs-gap 0 ) false 2 0 This acquisition mode/setup was used successfully used in program 15147 We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. 1725038047124 Using ephemeris for target 17470-1A-IO-NCLOUD-SUBJUPITER ephemeris data for target 17470-1A-IO-NCLOUD-SUBJUPITER does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.121. ephemeris interval: 24.121 to 26.121 Timing link suitability includes constraints ([Group (01 1A) Within 0.1 days]) The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. 1730726818000 266.6505426127614 (Tic-Visit :proposal-id 17470 :visit-id "1A" :proposal-version -1 :trans-version "20240604" :date "30-Aug-2024 12:14:06.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 383280 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "1A" :obset-id "1A" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "1A" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "1A" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 623 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 At the time of PJ57 (2023-12-31), Io's diameter is 1.125 arcesc. Thus the checkbox is set to 1.125/0.05 = 25 pixels here. 1706301619819 Using ephemeris for target 17470-02-IO-NCLOUD-LEADING ephemeris data for target 17470-02-IO-NCLOUD-LEADING does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.089. ephemeris interval: 23.365 to 26.001 The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. 1708745756000 67.7274421980378 (Tic-Visit :proposal-id 17470 :visit-id "02" :proposal-version -1 :trans-version "20230626" :date "26-Jan-2024 14:40:19.0" :trans-errors '(:WARNINGS 20 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 226528 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "02" :obset-id "02" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "02" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2110 :al-overhead-at-end 0 :internal-dur-at-end 57 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "02" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 417 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 This acquisition mode/setup was used successfully used in program 15147 We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. 1706296302914 Using ephemeris for target 17470-2A-IO-NCLOUD-LEADING ephemeris data for target 17470-2A-IO-NCLOUD-LEADING does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.089. ephemeris interval: 23.365 to 26.001 The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. Updated to remove step pattern in orbit 1, owing to lack of exposure times following TA 1708888062000 72.20611865435171 (Tic-Visit :proposal-id 17470 :visit-id "2A" :proposal-version -1 :trans-version "20230626" :date "26-Jan-2024 13:11:42.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 591904 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "2A" :obset-id "2A" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "2A" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2110 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "2A" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2160 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 At the time of PJ57 (2023-12-31), Io's diameter is 1.125 arcesc. Thus the checkbox is set to 1.125/0.05 = 25 pixels here. On Feb. 24-25, 2024 Io's diameter is 0.95 arcsec. Thus the checkbox is set to 0.95/0.05 = 23 pixels here. 1724853927566 Using ephemeris for target 17470-03-IO-NCLOUD-ANTIJUPITER ephemeris data for target 17470-03-IO-NCLOUD-ANTIJUPITER does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.121. ephemeris interval: 24.121 to 26.121 The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. 1730800673000 284.5120173219775 (Tic-Visit :proposal-id 17470 :visit-id "03" :proposal-version -1 :trans-version "20240604" :date "28-Aug-2024 09:05:27.0" :trans-errors '(:WARNINGS 8 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 261056 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "03" :obset-id "03" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "03" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2171 :al-overhead-at-end 0 :internal-dur-at-end 86 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "03" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 426 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 This acquisition mode/setup was used successfully used in program 15147 We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. 1725038054948 Using ephemeris for target 17470-3A-IO-NCLOUD-ANTIJUPITER ephemeris data for target 17470-3A-IO-NCLOUD-ANTIJUPITER does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.121. ephemeris interval: 24.121 to 26.121 The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. 1730823206000 263.0 (Tic-Visit :proposal-id 17470 :visit-id "3A" :proposal-version -1 :trans-version "20240604" :date "30-Aug-2024 12:14:14.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 383280 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "3A" :obset-id "3A" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "3A" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "3A" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 623 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 At the time of PJ57 (2023-12-31), Io's diameter is 1.125 arcesc. Thus the checkbox is set to 1.125/0.05 = 25 pixels here. 1724853931298 Using ephemeris for target 17470-04-IO-NCLOUD-TRAILING ephemeris data for target 17470-04-IO-NCLOUD-TRAILING does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.121. ephemeris interval: 24.121 to 26.121 The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. 1764025431000 294.4537066022096 (Tic-Visit :proposal-id 17470 :visit-id "04" :proposal-version -1 :trans-version "20240604" :date "28-Aug-2024 09:05:31.0" :trans-errors '(:WARNINGS 8 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 261056 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "04" :obset-id "04" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "04" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2171 :al-overhead-at-end 0 :internal-dur-at-end 86 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "04" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 426 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 This acquisition mode/setup was used successfully used in program 15147 We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. 1725038059322 Using ephemeris for target 17470-4A-IO-NCLOUD-TRAILING ephemeris data for target 17470-4A-IO-NCLOUD-TRAILING does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.121. ephemeris interval: 24.121 to 26.121 The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. 1764036714000 273.2995045546665 (Tic-Visit :proposal-id 17470 :visit-id "4A" :proposal-version -1 :trans-version "20240604" :date "30-Aug-2024 12:14:19.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 383280 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "4A" :obset-id "4A" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "4A" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "4A" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 623 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 At 25-Nov-2025 (25.329) from 02:38 to 05:00, Io's diameter is 1.11 arcesc. Thus the checkbox is set to (1.11/0.05 = 22.1) 25 pixels here. 1724853935111 Using ephemeris for target 17470-05-IO-NCLOUD-LEADING ephemeris data for target 17470-05-IO-NCLOUD-LEADING does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.121. ephemeris interval: 24.121 to 26.121 The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. 1764110170000 294.4611563390308 (Tic-Visit :proposal-id 17470 :visit-id "05" :proposal-version -1 :trans-version "20240604" :date "28-Aug-2024 09:05:34.0" :trans-errors '(:WARNINGS 8 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 261056 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "05" :obset-id "05" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "05" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2171 :al-overhead-at-end 0 :internal-dur-at-end 86 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "05" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 426 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 This acquisition mode/setup was used successfully used in program 15147 We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. 1725038063808 Using ephemeris for target 17470-5A-IO-NCLOUD-LEADING ephemeris data for target 17470-5A-IO-NCLOUD-LEADING does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.121. ephemeris interval: 24.121 to 26.121 The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. 1764121449000 272.6 (Tic-Visit :proposal-id 17470 :visit-id "5A" :proposal-version -1 :trans-version "20240604" :date "30-Aug-2024 12:14:23.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 383280 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "5A" :obset-id "5A" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "5A" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "5A" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 623 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 Nov. 17 Io's diameter is 21.7 pixels. Dec. 24, 2025 the size is 23.6 pixels. Thus the checkbox is left at 25 pixels here. 1724853937982 Using ephemeris for target 17470-06-IO-NCLOUD-TRAILING ephemeris data for target 17470-06-IO-NCLOUD-TRAILING does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.121. ephemeris interval: 24.121 to 26.121 The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. 1764641312000 292.4702646598819 (Tic-Visit :proposal-id 17470 :visit-id "06" :proposal-version -1 :trans-version "20240604" :date "28-Aug-2024 09:05:37.0" :trans-errors '(:WARNINGS 8 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 261056 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "06" :obset-id "06" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "06" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2171 :al-overhead-at-end 0 :internal-dur-at-end 86 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "06" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 426 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 This acquisition mode/setup was used successfully used in program 15147 We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. 1725038070745 Using ephemeris for target 17470-6A-IO-NCLOUD-TRAILING ephemeris data for target 17470-6A-IO-NCLOUD-TRAILING does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.121. ephemeris interval: 24.121 to 26.121 The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. 1764652605000 273.2828128405225 (Tic-Visit :proposal-id 17470 :visit-id "6A" :proposal-version -1 :trans-version "20240604" :date "30-Aug-2024 12:14:30.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 383280 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "6A" :obset-id "6A" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "6A" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "6A" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 623 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 Dec. 23, 2025 the size is 23.6 pixels. Thus the checkbox is left at 25 pixels here. On 02-Dec-2025 (25.336) the size is 22.68 pixels, so we have a 2-pixel margin for good measure. 1724345302977 Using ephemeris for target 17470-07-IO-PLASMATORUS-LEADING The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. (Tic-Visit :proposal-id 17470 :visit-id "07" :proposal-version -1 :trans-version "20240604" :date "22-Aug-2024 11:48:22.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 870176 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "07" :obset-id "07" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "07" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2532 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "07" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2533 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 2 0 At the time of PJ57 (2023-12-31), Io's diameter is 1.125 arcesc. Thus the checkbox is set to 1.125/0.05 = 25 pixels here. To be modified as the timing is determined. 1724345307380 Using ephemeris for target 17470-08-IO-PLASMATORUS-TRAILING The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. (Tic-Visit :proposal-id 17470 :visit-id "08" :proposal-version -1 :trans-version "20240604" :date "22-Aug-2024 11:48:27.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 870176 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "08" :obset-id "08" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "08" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2532 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "08" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2533 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 2 0 At the time of PJ57 (2023-12-31), Io's diameter is 1.125 arcesc. Thus the checkbox is set to 1.125/0.05 = 25 pixels here. To be modified as the timing is determined. 1761830122174 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. /System/Volumes/Data/solaris/user1/williamj/hst/work/cycle31/OP-cache/17470-v09.xml 1764499721000 260.7696523850749 (Tic-Visit :proposal-id 17470 :visit-id "09" :proposal-version -1 :trans-version "20250624" :date "30-Oct-2025 09:15:22.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 321792 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "09" :obset-id "09" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "09" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2127 :al-overhead-at-end 0 :internal-dur-at-end 114 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2507 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "09" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2126 :al-overhead-at-end 0 :internal-dur-at-end 434 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2507 :pcs-gap 0 ) false 2 0 Io's orbital distance from Jupiter is 422,000 km. For example, offset from Callisto on Nov. 30, 2025 at 12:00. With Io's 1.7 day orbit we have a good window to try the opposite side, 1723652247777 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. (Tic-Visit :proposal-id 17470 :visit-id "10" :proposal-version -1 :trans-version "20240604" :date "14-Aug-2024 11:17:27.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 330528 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "10" :obset-id "10" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "10" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 38 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "10" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 436 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 1695212004914 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. /System/Volumes/Data/solaris/user1/williamj/hst/work/cycle31/OP-cache/17470-v11.xml (Tic-Visit :proposal-id 17470 :visit-id "11" :proposal-version -1 :trans-version "20230626" :date "20-Sep-2023 08:13:24.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 330496 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "11" :obset-id "11" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "11" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2110 :al-overhead-at-end 0 :internal-dur-at-end 124 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "11" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 436 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 1695212005195 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. /System/Volumes/Data/solaris/user1/williamj/hst/work/cycle31/OP-cache/17470-v12.xml (Tic-Visit :proposal-id 17470 :visit-id "12" :proposal-version -1 :trans-version "20230626" :date "20-Sep-2023 08:13:25.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 330496 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "12" :obset-id "12" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "12" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2110 :al-overhead-at-end 0 :internal-dur-at-end 124 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "12" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 436 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 1695212005570 Using ephemeris for target 17470-17-IO-NCLOUD-TRAILING-NUV The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. /System/Volumes/Data/solaris/user1/williamj/hst/work/cycle31/OP-cache/17470-v17.xml Search for Mg at and around Io, NUV reflectance spectra 1703140620000 71.1346241000092 (Tic-Visit :proposal-id 17470 :visit-id "17" :proposal-version -1 :trans-version "20230626" :date "20-Sep-2023 08:13:25.0" :trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "32" :si-bright-earth-limb-angle 20.0 :data-volume 347936 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "17" :obset-id "17" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "17" :orbit-number 1 :pcs-time 383 :si-vis-utilization 2530 :al-overhead-at-end 0 :internal-dur-at-end 105 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "17" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2522 :al-overhead-at-end 0 :internal-dur-at-end 388 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 2 1 This acquisition mode/setup was used successfully used in program 15147. 1725038080017 Could not find ephemeris C:\Users\kretherford\OneDrive - SWRI\Documents\HSTprops\Io31JunoProject\APTfilesIoCampaignCy31\visit-planner\17470_10.trh for target 17470-18-EUROPA-NCLOUD-EASTANSA. Using default ephemeris C:\Users\kretherford\APT_2023.7.3\LispPrograms\casm\casmfiles\moss\jupiter.trh for JUPITER. Moss Window file C:\Users\kretherford\OneDrive - SWRI\Documents\HSTprops\Io31JunoProject\APTfilesIoCampaignCy31\visit-planner\17470_10.wnd is missing. Assuming Schedulability everywhere. Please contact your PC if you need to obtain a target specific window file. Using ephemeris for target 17470-18-IO-NCLOUD-LEADING ephemeris data for target 17470-18-IO-NCLOUD-LEADING does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.089. ephemeris interval: 23.365 to 26.001 The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. These Europa COS and STIS visits with 4 orbits can be split into 2 visits with 2 orbits each instrument if it helps scheduling or reduces risk of gyro problems. (Tic-Visit :proposal-id 17470 :visit-id "18" :proposal-version -1 :trans-version "20240604" :date "30-Aug-2024 12:14:39.0" :trans-errors '(:WARNINGS 8 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 4 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 687200 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "18" :obset-id "18" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "18" :obset-id "A8" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "18" :obset-id "B8" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "18" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2170 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "18" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 398 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "18" :orbit-number 3 :pcs-time 380 :si-vis-utilization 1796 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "18" :orbit-number 4 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 623 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 4 0 This acquisition mode/setup was used successfully used in program 15147 We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. 1725038088142 Could not find ephemeris C:\Users\kretherford\OneDrive - SWRI\Documents\HSTprops\Io31JunoProject\APTfilesIoCampaignCy31\visit-planner\17470_11.trh for target 17470-19-EUROPA-NCLOUD-WESTANSA. Using default ephemeris C:\Users\kretherford\APT_2023.7.3\LispPrograms\casm\casmfiles\moss\jupiter.trh for JUPITER. Moss Window file C:\Users\kretherford\OneDrive - SWRI\Documents\HSTprops\Io31JunoProject\APTfilesIoCampaignCy31\visit-planner\17470_11.wnd is missing. Assuming Schedulability everywhere. Please contact your PC if you need to obtain a target specific window file. Using ephemeris for target 17470-19-IO-NCLOUD-LEADING ephemeris data for target 17470-19-IO-NCLOUD-LEADING does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.089. ephemeris interval: 23.365 to 26.001 The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. These Europa COS and STIS visits with 4 orbits can be split into 2 visits with 2 orbits each instrument if it helps scheduling or reduces risk of gyro problems. (Tic-Visit :proposal-id 17470 :visit-id "19" :proposal-version -1 :trans-version "20240604" :date "30-Aug-2024 12:14:47.0" :trans-errors '(:WARNINGS 8 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 4 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 687200 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "19" :obset-id "19" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "19" :obset-id "A9" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "19" :obset-id "B9" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "19" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2170 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "19" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 398 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "19" :orbit-number 3 :pcs-time 380 :si-vis-utilization 1796 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "19" :orbit-number 4 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 623 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 4 0 This acquisition mode/setup was used successfully used in program 15147 We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. Notes from ProjID=11539: ETC: COS78468 Used 3 strongest lines in this waveband (excluding Lyman alpha) from HST/FOS measurements by Clarke et al 1994, JGR 99., along with high airglow. Gives buffer time of 2/3 of 2919. We decrease this to 800s to allow for continuum or scatter. The grating setting is chosen to detect the Io emission lines at 1256, 1304, 1356, 1389, and 1429 A. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. HOWEVER we should choose the best single FP-POS value, to avoid (if possible) putting emission lines of interest on known problem areas of the detector. ProjID 15848 and others use the c1291 instead of c1327 which has restrictions on lifetime position due to gain sag, and I Carl recalls that we couldn't use it under the COS 2025 restrictions. 1695212008871 Using ephemeris for target 17470-20-IO-AURORA-PJ57 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. /System/Volumes/Data/solaris/user1/williamj/hst/work/cycle31/OP-cache/17470-v20.xml This visit is to be scheduled at close in time as possible to the flyby at Io by Juno with clostest approach on 2023-12-30 (08:35 UTC Juno time) 1706683781000 71.1909652832014 (Tic-Visit :proposal-id 17470 :visit-id "20" :proposal-version -1 :trans-version "20230626" :date "20-Sep-2023 08:13:28.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 3 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 591984 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "20" :obset-id "20" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "20" :orbit-number 1 :pcs-time 383 :si-vis-utilization 2170 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "20" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 361 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "20" :orbit-number 3 :pcs-time 392 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 3 0 At the time of PJ57 (2023-12-31), Io's diameter is 1.125 arcesc. Thus the checkbox is set to 1.13/0.05 = 23 pixels here. 1721422511276 Using ephemeris for target 17470-21-IO-AURORA-PJ57 ephemeris data for target 17470-21-IO-AURORA-PJ57 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.089. ephemeris interval: 23.365 to 26.001 The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. This visit is to be scheduled at close in time as possible to the flyby at Io by Juno with clostest approach on 2023-12-30 (08:35 UTC Juno time); Let's reschedule for PJ64 proximity in Aug 20 (24.233) 22:52 to Aug 21 (24.234) 01:13 1724194129000 260.8587260267016 (Tic-Visit :proposal-id 17470 :visit-id "21" :proposal-version -1 :trans-version "20240604" :date "19-Jul-2024 15:55:10.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 3 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 591952 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "21" :obset-id "21" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "21" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2150 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "21" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 361 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "21" :orbit-number 3 :pcs-time 380 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 3 0 At the time of PJ57 (2023-12-31), Io's diameter is 1.125 arcesc. Thus the checkbox is set to 1.13/0.05 = 23 pixels here. 1724338297170 Using ephemeris for target 17470-22-IO-AURORA-UVS1 ephemeris data for target 17470-22-IO-AURORA-UVS1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.089. ephemeris interval: 23.365 to 26.001 The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. This visit is to be scheduled at close in time as possible to a time when Juno-UVS observes Io around PJ67 (starting around 2024-11-24 13:05) (Tic-Visit :proposal-id 17470 :visit-id "22" :proposal-version -1 :trans-version "20240604" :date "22-Aug-2024 09:51:37.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 383280 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "22" :obset-id "22" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "22" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "22" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 623 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 November 2nd, 2025 Io is 20.8 pixels diameter. So checkbox 23. 1721316444578 Using ephemeris for target 17470-23-IO-AURORA-PJ58 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. /System/Volumes/Data/solaris/user1/williamj/hst/work/cycle31/OP-cache/17470-v23.xml This visit is to be scheduled at close in time as possible to the flyby at Io by Juno with clostest approach on 2024-02-03 (17:48 UTC Juno time) 1706769211000 67.76364688313899 (Tic-Visit :proposal-id 17470 :visit-id "23" :proposal-version -1 :trans-version "20240627" :date "18-Jul-2024 11:27:24.0" :trans-errors '(:WARNINGS 2 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 3 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 591952 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "23" :obset-id "23" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "23" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2170 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "23" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 361 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "23" :orbit-number 3 :pcs-time 392 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 3 1 At the time of PJ57 (2024-02-03), Io's diameter is 1.005 arcesc. Thus the checkbox is set to 1.005/0.05 = 21 pixels here. 1723839072231 HOPR repeat of visit 23 This visit is to be scheduled at close in time as possible to the flyby at Io by Juno with clostest approach on 2024-10-22 1728103329000 248.26361843481436 (Tic-Visit :proposal-id 17470 :visit-id "92" :proposal-version -1 :trans-version "20240604" :date "16-Aug-2024 15:11:12.0" :trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 3 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 591952 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "92" :obset-id "92" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "92" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2190 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "92" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 361 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "92" :orbit-number 3 :pcs-time 380 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 3 1 At the time of PJ57 (2024-02-03), Io's diameter is 1.005 arcesc. Thus the checkbox is set to 1.005/0.05 = 21 pixels here. Before Sept. 21 Io checkbox 21. Before Oct. 21 Io checkbox 23. After, 25. 1695212011234 Using ephemeris for target 17470-24-IO-AURORA-PJ58 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. /System/Volumes/Data/solaris/user1/williamj/hst/work/cycle31/OP-cache/17470-v24.xml This visit is to be scheduled at close in time as possible to the flyby at Io by Juno with clostest approach on 2024-02-03 (17:48 UTC Juno time) 1706854643000 69.35014297655431 (Tic-Visit :proposal-id 17470 :visit-id "24" :proposal-version -1 :trans-version "20230626" :date "20-Sep-2023 08:13:31.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 3 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 591952 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "24" :obset-id "24" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "24" :orbit-number 1 :pcs-time 383 :si-vis-utilization 2170 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "24" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 361 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "24" :orbit-number 3 :pcs-time 392 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 3 0 At the time of PJ57 (2024-02-03), Io's diameter is 1.005 arcesc. Thus the checkbox is set to 1.005/0.05 = 21 pixels here. 1695212011736 Using ephemeris for target 17470-25-IO-AURORA-PJ59 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. /System/Volumes/Data/solaris/user1/williamj/hst/work/cycle31/OP-cache/17470-v25.xml This visit is to be scheduled at close in time as possible to the flyby at Io by Juno with clostest approach on 2024-03-07 1709656763000 72.72494719473119 (Tic-Visit :proposal-id 17470 :visit-id "25" :proposal-version -1 :trans-version "20230626" :date "20-Sep-2023 08:13:31.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 383216 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "25" :obset-id "25" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "25" :orbit-number 1 :pcs-time 383 :si-vis-utilization 2170 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "25" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 623 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 At the time of PJ59 (2024-03-07), Io's diameter is 0.91 arcesc. Thus the checkbox is set to 0.91/0.05 <= 19 pixels here. 1721422546929 HOPR repeat of second orbit from visit 25 This visit is to be scheduled at close in time as possible to the flyby at Io by Juno with clostest approach on 2024-10-22 1729710621000 281.3185237016409 (Tic-Visit :proposal-id 17470 :visit-id "93" :proposal-version -1 :trans-version "20240604" :date "19-Jul-2024 15:55:46.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 383216 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "93" :obset-id "93" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "93" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2170 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "93" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 623 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 At the time of PJ59 (2024-03-07), Io's diameter is 0.91 arcesc. Thus the checkbox is set to 0.91/0.05 <= 19 pixels here. 1695212012238 Using ephemeris for target 17470-26-IO-AURORA-PJ59 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. /System/Volumes/Data/solaris/user1/williamj/hst/work/cycle31/OP-cache/17470-v26.xml This visit is to be scheduled at close in time as possible to the flyby at Io by Juno with clostest approach on 2024-03-07 1709668151000 72.7345393183898 (Tic-Visit :proposal-id 17470 :visit-id "26" :proposal-version -1 :trans-version "20230626" :date "20-Sep-2023 08:13:32.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 383216 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "26" :obset-id "26" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "26" :orbit-number 1 :pcs-time 383 :si-vis-utilization 2170 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "26" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 623 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 At the time of PJ59 (2024-03-07), Io's diameter is 0.91 arcesc. Thus the checkbox is set to 0.91/0.05 <= 19 pixels here. 1723653100170 This visit is to be scheduled when Io is emerging from eclipse, and as close in time as possible to PJ66 (2024-10-22); I'll rethink this with Lorenz. If no HST availability post opposition on Dec. 7 we might need to push this till next availability window or rethink the egress plan and do an ingress instead. No longer calling this an EGRESS attempt. Given gyro constraints. (Tic-Visit :proposal-id 17470 :visit-id "27" :proposal-version -1 :trans-version "20240604" :date "14-Aug-2024 11:31:40.0" :trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 383248 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "27" :obset-id "27" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "27" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2206 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "27" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 623 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 1 At the time of PJ59 (2024-03-07), Io's diameter is 0.91 arcesc. Thus the checkbox is set to 0.91/0.05 <= 19 pixels here. At the time of UVS2 (2024-09-30), Io's diameter is 1.077 arcesc. Thus the checkbox is set to 1.077/0.05 = 21.5 pixels < 23 here. 1695212013231 Using ephemeris for target 17470-28-IO-AURORA-PJ64 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. /System/Volumes/Data/solaris/user1/williamj/hst/work/cycle31/OP-cache/17470-v28.xml This visit is to be scheduled at close in time as possible to the flyby at Io by Juno with clostest approach on 2024-08-18 1724040072000 262.0336358533142 (Tic-Visit :proposal-id 17470 :visit-id "28" :proposal-version -1 :trans-version "20230626" :date "20-Sep-2023 08:13:33.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 383216 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "28" :obset-id "28" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "28" :orbit-number 1 :pcs-time 383 :si-vis-utilization 2170 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "28" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 623 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 At the time of PJ57 (2024-08-18), Io's diameter is 0.93 arcesc. Thus the checkbox is set to 0.93/0.05 <= 19 pixels here. 1721422621275 Using ephemeris for target 17470-29-IO-AURORA-PJ64 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. This visit is to be scheduled at close in time as possible to the flyby at Io by Juno with clostest approach on 2024-08-18 1724051438000 262.0431211812486 (Tic-Visit :proposal-id 17470 :visit-id "29" :proposal-version -1 :trans-version "20240604" :date "19-Jul-2024 15:57:01.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 383216 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "29" :obset-id "29" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "29" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2170 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "29" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 623 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 At the time of PJ57 (2024-08-18), Io's diameter is 0.93 arcesc. Thus the checkbox is set to 0.93/0.05 <= 19 pixels here. 1723653234614 This visit is to be scheduled at close in time as possible to a time when Juno-UVS observes Io associated with PJ65 starting at 2024-09-20 02:29 and lasting 20-30 minutes. 1726745948000 255.5404651857944 (Tic-Visit :proposal-id 17470 :visit-id "30" :proposal-version -1 :trans-version "20240604" :date "14-Aug-2024 11:33:54.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 383248 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "30" :obset-id "30" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "30" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "30" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 623 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 0 At the time of PJ59 (2024-03-07), Io's diameter is 0.91 arcesc. Thus the checkbox is set to 0.91/0.05 <= 19 pixels here. sep. 19 angular diameter is 1.04 arcsec, with 20.8 pixels. 1723653241988 Using ephemeris for target 17470-31-IO-AURORA-PJ65 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. This visit is to be scheduled at close in time as possible to the flyby at Io by Juno with closest approach on 2024-10-22 1729614074000 281.3141245526177 (Tic-Visit :proposal-id 17470 :visit-id "31" :proposal-version -1 :trans-version "20240604" :date "14-Aug-2024 11:34:01.0" :trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 3 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 591952 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "31" :obset-id "31" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "31" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2190 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "31" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 361 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "31" :orbit-number 3 :pcs-time 380 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 3 1 At the time of PJ57 (2024-08-18), Io's diameter is 1.04 arcesc. Thus the checkbox is set to 1.04/0.05 <= 21 pixels here. october 24th is 23.1 pixels so use 25 1721422645090 Using ephemeris for target 17470-32-IO-AURORA-PJ65 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. This visit is to be scheduled at close in time as possible to the flyby at Io by Juno with closest approach on 2024-10-22 1729631116000 281.30593531164527 (Tic-Visit :proposal-id 17470 :visit-id "32" :proposal-version -1 :trans-version "20240604" :date "19-Jul-2024 15:57:24.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 3 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 591952 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "32" :obset-id "32" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "32" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2170 :al-overhead-at-end 0 :internal-dur-at-end 178 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "32" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 361 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "32" :orbit-number 3 :pcs-time 380 :si-vis-utilization 2161 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 3 0 Before Sept. 21 Io checkbox 21. Before Oct. 21 Io checkbox 23. After, 25. 1723613987382 Using ephemeris for target 17470-40-IO-TRANSIT-FUV ephemeris data for target 17470-40-IO-TRANSIT-FUV does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.213. ephemeris interval: 24.213 to 26.213 Timing link suitability includes constraints ([41 After 40 by at most 2.2 days]) The scheduling data was generated by CASM 32.1.1. CASM was run in Phase II mode. STIS FUV imaging of the plumes on the limb of Io while transiting Jupiter Visit 1 With Io|*|s 1.7 day orbital period roughly 60 (35) transit events are available early (late) in Cy31 (similarly but less so for eclipse events), with one and sometimes two HST orbits possible in each event. We search for plume gas variability in 4 events using STIS MAMA F25QTZ FUV imaging using the dither method implemented previously for Europa to obtain ~30 km/pix resolution elements with 1-orbit per event. Two additional orbits using the same longpass (>150 nm) F25QTZ filter would assess any faint auroral emission or disk reflectance PSF systematic features. 1725313295000 265.1407749832091 (Tic-Visit :proposal-id 17470 :visit-id "40" :proposal-version -1 :trans-version "20240604" :date "14-Aug-2024 07:39:47.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 1461216 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "40" :obset-id "40" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "40" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2168 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 1 0 Make sure to offset to Io once Europa is acquired 1723614022063 Using ephemeris for target 17470-41-IO-POSTTRANSIT-FUV ephemeris data for target 17470-41-IO-POSTTRANSIT-FUV does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.213. ephemeris interval: 24.213 to 26.213 Timing link suitability includes constraints ([41 After 40 by at most 2.2 days]) The scheduling data was generated by CASM 32.1.1. CASM was run in Phase II mode. STIS FUV imaging of the plumes on the limb post transit Use dither pattern Visit 1 1725318977000 265.1415768062081 (Tic-Visit :proposal-id 17470 :visit-id "41" :proposal-version -1 :trans-version "20240604" :date "14-Aug-2024 07:40:21.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 1461216 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "41" :obset-id "41" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "41" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2168 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 1 0 Make sure to offset to Io once Europa is acquired 1761334789816 Using ephemeris for target 17470-42-IO-TRANSIT-FUV ephemeris data for target 17470-42-IO-TRANSIT-FUV does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.213. ephemeris interval: 24.213 to 26.213 Timing link suitability includes constraints ([43 After 42 by at most 2.2 days]) The scheduling data was generated by CASM 32.1.1. CASM was run in Phase II mode. STIS FUV imaging of the plumes on the limb of Io while transiting Jupiter Visit 2 Using the Dither pattern used in Sparks' program for Europa Plumes - we'll need to iterate on the Level 3 definition of the target. 1764459961000 274.88791675640664 (Tic-Visit :proposal-id 17470 :visit-id "42" :proposal-version -1 :trans-version "20250624" :date "24-Oct-2025 14:39:49.0" :trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 1391632 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "42" :obset-id "42" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "42" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2128 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2507 :pcs-gap 0 ) false 1 1 1759866381703 Using ephemeris for target 17470-43-IO-POSTTRANSIT-FUV ephemeris data for target 17470-43-IO-POSTTRANSIT-FUV does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.213. ephemeris interval: 24.213 to 26.213 Timing link suitability includes constraints ([43 After 42 by at most 2.2 days]) The scheduling data was generated by CASM 32.1.1. CASM was run in Phase II mode. STIS FUV imaging of the plumes on the limb post transit Use dither pattern with Level 3. Using the Dither pattern used in Sparks' program for Europa Plumes - we'll need to iterate on the Level 3 definition of the target. Visit 2 1764471261000 274.8786483294115 (Tic-Visit :proposal-id 17470 :visit-id "43" :proposal-version -1 :trans-version "20250624" :date "07-Oct-2025 14:46:21.0" :trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 1669968 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "43" :obset-id "43" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "43" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2533 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2867 :pcs-gap 0 ) false 1 1 1759866974660 Using ephemeris for target 17470-44-EUROPA-ACQ Using ephemeris for target 17470-44-IO-TRANSIT-FUV The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. STIS FUV imaging of the plumes on the limb of Io while transiting Jupiter Visit 3 Originally had requirement of AFTER 02-AUG-2024:00:00:00. This was removed to pull early. Using the Dither pattern used in Sparks' program for Europa Plumes - we'll need to iterate on the Level 3 definition of the target. 1765222637000 299.8673488441659 (Tic-Visit :proposal-id 17470 :visit-id "44" :proposal-version -1 :trans-version "20250624" :date "07-Oct-2025 14:56:14.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 1391632 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "44" :obset-id "44" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "44" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2127 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2507 :pcs-gap 0 ) false 1 0 Skip the Europa acquisition and offset. Visits 40/41 look good. 1759866982978 Using ephemeris for target 17470-45-EUROPA-ACQ Using ephemeris for target 17470-45-IO-TRANSIT-FUV The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. STIS FUV imaging of the plumes on the limb of Io while transiting Jupiter Visit 4 Trying another detector but with same 25QTZ filter based on Kandis Lea and Lori's suggestion. (Tic-Visit :proposal-id 17470 :visit-id "45" :proposal-version -1 :trans-version "20250624" :date "07-Oct-2025 14:56:22.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 1391632 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "45" :obset-id "45" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "45" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2127 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2507 :pcs-gap 0 ) false 1 0 Skip the Europa acquisition and offset. Visits 40/41 look good. 1721316326727 Using ephemeris for target 17470-46-IO-TRANSIT-WFC3 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. /System/Volumes/Data/solaris/user1/williamj/hst/work/cycle31/OP-cache/17470-v46.xml Imaging mostly dust absorption at visible wavelengths, transit events near the beginning and end of Cy31 (1-orbit each) are planned with WFC3 filter sets (F225W, F275W, F336W, F343N, F390M, F390W, F467M, F502N, F555W). BEFORE timing requirement replaced with a BETWEEN of Nov 26 to Dec 9. This allows scheduling in 4 transits that are known to work and have no conflicts. - Januszewski If we have a few more seconds to optimize the orbit window then adding time evenly to F225W and F275W will be good. Implementing a 3-pt dither pattern with three exposures per filter setting. 1705117463000 52.69189804118051 (Tic-Visit :proposal-id 17470 :visit-id "46" :proposal-version -1 :trans-version "20240627" :date "18-Jul-2024 11:25:26.0" :trans-errors '(:WARNINGS 1 :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 123568 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "46" :obset-id "46" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "46" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2443 :al-overhead-at-end 0 :internal-dur-at-end 172 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 1 0 Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Replace F280N with F275W for better signal quality and bandpass coverage. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. 1721316326727 /System/Volumes/Data/solaris/user1/williamj/hst/work/cycle31/OP-cache/17470-v90.xml HOPR Repeat of visit 46. Imaging mostly dust absorption at visible wavelengths, transit events near the beginning and end of Cy31 (1-orbit each) are planned with WFC3 filter sets (F225W, F275W, F336W, F343N, F390M, F390W, F467M, F502N, F555W). BEFORE timing requirement replaced with a BETWEEN of Nov 26 to Dec 9. This allows scheduling in 4 transits that are known to work and have no conflicts. - Januszewski If we have a few more seconds to optimize the orbit window then adding time evenly to F225W and F275W will be good. Implementing a 3-pt dither pattern with three exposures per filter setting. 1732803835000 269.77846518047016 (Tic-Visit :proposal-id 17470 :visit-id "46" :proposal-version -1 :trans-version "20240627" :date "18-Jul-2024 11:25:26.0" :trans-errors '(:WARNINGS 1 :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 123568 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "46" :obset-id "46" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "46" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2443 :al-overhead-at-end 0 :internal-dur-at-end 172 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 1 0 Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Replace F280N with F275W for better signal quality and bandpass coverage. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. 1697219338519 Using ephemeris for target 17470-47-IO-TRANSIT-WFC3 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Imaging mostly dust absorption at visible wavelengths, transit events near the beginning and end of Cy31 (1-orbit each) are planned with WFC3 filter sets (F225W, F280N, F336W, F343N, F390W, F475W, F555W). 1726688703000 260.4516324645874 (Tic-Visit :proposal-id 17470 :visit-id "47" :proposal-version -1 :trans-version "20230626" :date "13-Oct-2023 12:48: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 123568 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "47" :obset-id "47" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "47" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2443 :al-overhead-at-end 0 :internal-dur-at-end 172 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 1 0 Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Replace F280N with F275W for better signal quality and bandpass coverage. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. Exposures parallel those in Program 17294 OPAL. Offers more complete wavelength coverage with all bands. 1698834494272 Using ephemeris for target 17470-48-GANYMEDE-ACQ Using ephemeris for target 17470-48-IO-TRANSIT-STISNUV The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Version of the NUV transit observation using central wavelength 2095 BETWEEN added to target a specific transit the PC knows will work. 1733110239000 250.56359824231083 (Tic-Visit :proposal-id 17470 :visit-id "48" :proposal-version -1 :trans-version "20230626" :date "01-Nov-2023 11:28:14.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 574496 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "48" :obset-id "48" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "48" :obset-id "A8" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "48" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2469 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 1 0 For acquisition with Europa on 25 November 2023: Europa diameter is 1.0.6 arcesc. Thus the checkbox is set to 1.06/0.05 = 21 pixels here. October 8-10, 2024 is 18.9 pixels for Europa, hend checkbox 19. 1724338335707 Using ephemeris for target 17470-49-GANYMEDE-ACQ Using ephemeris for target 17470-49-IO-TRANSIT-STISNUV The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Version of the NUV transit observation using central wavelength 2095 1761860018000 265.1175899376283 (Tic-Visit :proposal-id 17470 :visit-id "49" :proposal-version -1 :trans-version "20240604" :date "22-Aug-2024 09:52:15.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 574496 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "49" :obset-id "49" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "49" :obset-id "A9" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "49" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2531 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 1 0 Used the exposure time from previous programs (e.g.15419) 1724338348543 Using ephemeris for target 17470-50-GANYMEDE-ACQ Using ephemeris for target 17470-50-IO-TRANSIT-STISNUV The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Version of the NUV transit observation using central wavelength 2659 (Tic-Visit :proposal-id 17470 :visit-id "50" :proposal-version -1 :trans-version "20240604" :date "22-Aug-2024 09:52:28.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 713616 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "50" :obset-id "50" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "50" :obset-id "A0" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "50" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2532 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 1 0 Used the exposure time from previous programs (e.g.15419) 1724338365169 Using ephemeris for target 17470-51-GANYMEDE-ACQ Using ephemeris for target 17470-51-IO-TRANSIT-STISNUV The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Version of the NUV transit observation using central wavelength 2659 (Tic-Visit :proposal-id 17470 :visit-id "51" :proposal-version -1 :trans-version "20240604" :date "22-Aug-2024 09:52:45.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 713744 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "51" :obset-id "51" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "51" :obset-id "A1" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "51" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2529 :al-overhead-at-end 0 :internal-dur-at-end 440 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 1 0 Used the exposure time from previous programs (e.g.15419) For Ganymede, checkbox 37 if after Nov. 18, 2024. Checkbox 35 for Oct. 21 to Nov. 18, 2024. Checkbox 33 if before Oct. 21. Switch to a Europa offset and relevent checkboxes instead if feasible. Updated Target to Europa for a TA. 202 Europa-Acq2 is like 100 but for year 2. For Europa, checkbox TBC if after Nov, 2025. Checkbox TBC for Sept. to Nov., 2025. Checkbox TBC if before TBC 2025. 1759346770771 Using ephemeris for target 17470-52-IO-TRANSIT-COSNUV The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. With TIME-TAG mode. 1765833010000 274.78428229541 (Tic-Visit :proposal-id 17470 :visit-id "52" :proposal-version -1 :trans-version "20250624" :date "01-Oct-2025 14:26:10.0" :trans-errors '(:WARNINGS 4 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "32" :si-bright-earth-limb-angle 20.0 :data-volume 104464 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "52" :obset-id "52" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "52" :obset-id "A2" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "52" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2487 :al-overhead-at-end 0 :internal-dur-at-end 386 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2867 :pcs-gap 0 ) false 1 0 Offset from europa is ok. It seemed too hard for Bill to acquire on Io instead while sunlit, shortly before transit first contact. Changed from pattern to a POSTARG series. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. The NUV wavelengths are less critical to positioning for the gain-sag. First step is to stare while on Io itself. use postarg x=-3 and y=3 to offset in roughly east of Jupiter direction, assuming roll angle ~45 to Jupiter North as typical. This SO2 absorption at higher altitude away from Io is the primary objective. More like 4.2 arcsec offset with sqrt(2). use postarg x=-6 and y=6 to offset in roughly east of Jupiter direction, assuming roll angle ~45 to Jupiter North as typical. The 6 arcsec location provides more of a baseline without much SO2 absorption. More like 8.5 arcsec offset with sqrt(2). 1763582388514 Using ephemeris for target 17470-53-IO-TRANSIT-COSNUV The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. /System/Volumes/Data/solaris/user1/williamj/hst/work/cycle31/OP-cache/17470-v53.xml With TIME-TAG mode. With the 2nd event in the series we'll add a pre-transit observation in the preceeding orbit, without the Jupiter background Line13 pattern. (2 orbits total, unlike the 1 orbits for the others). We might trade the orbit for COSNUV-4 to do this two-orbit plan with COSNUV-3 as well, given the better exposure times and planning logic. 1766595618000 279.55662578128147 (Tic-Visit :proposal-id 17470 :visit-id "53" :proposal-version -1 :trans-version "20250624" :date "19-Nov-2025 14:59:48.0" :trans-errors '(:WARNINGS 6 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "32" :si-bright-earth-limb-angle 20.0 :data-volume 426160 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "53" :obset-id "53" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "53" :obset-id "A3" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "53" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2029 :al-overhead-at-end 0 :internal-dur-at-end 424 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2867 :pcs-gap 0 ) false 1 0 It will probably be best to acquire on Io instead while sunlit, shortly before transit first contact. A few of the pattern exposures while still in sunlight wouldn't be terrible. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. The NUV wavelengths are less critical to positioning for the gain-sag. First step is to stare while on Io itself. use postarg x=-3 and y=3 to offset in roughly east of Jupiter direction, assuming roll angle ~45 to Jupiter North as typical. This SO2 absorption at higher altitude away from Io is the primary objective. More like 4.2 arcsec offset with sqrt(2). use postarg x=-6 and y=6 to offset in roughly east of Jupiter direction, assuming roll angle ~45 to Jupiter North as typical. The 6 arcsec location provides more of a baseline without much SO2 absorption. More like 8.5 arcsec offset with sqrt(2). 1763733736249 Using ephemeris for target 17470-54-IO-TRANSIT-COSNUV The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. /System/Volumes/Data/solaris/user1/williamj/hst/work/cycle31/OP-cache/17470-v54.xml With TIME-TAG mode. 1766748254000 296.649263695798 (Tic-Visit :proposal-id 17470 :visit-id "54" :proposal-version -1 :trans-version "20250624" :date "21-Nov-2025 09:02:16.0" :trans-errors '(:WARNINGS 6 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "32" :si-bright-earth-limb-angle 20.0 :data-volume 426160 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "54" :obset-id "54" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "54" :obset-id "A4" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "54" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2029 :al-overhead-at-end 0 :internal-dur-at-end 424 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2867 :pcs-gap 0 ) false 1 0 It will probably be best to acquire on Io instead while sunlit, shortly before transit first contact. A few of the pattern exposures while still in sunlight wouldn't be terrible. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. The NUV wavelengths are less critical to positioning for the gain-sag. First step is to stare while on Io itself. use postarg x=-3 and y=3 to offset in roughly east of Jupiter direction, assuming roll angle ~45 to Jupiter North as typical. This SO2 absorption at higher altitude away from Io is the primary objective. More like 4.2 arcsec offset with sqrt(2). use postarg x=-6 and y=6 to offset in roughly east of Jupiter direction, assuming roll angle ~45 to Jupiter North as typical. The 6 arcsec location provides more of a baseline without much SO2 absorption. More like 8.5 arcsec offset with sqrt(2). 1759348531584 Using ephemeris for target 17470-55-IO-TRANSIT-COSNUV The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. With TIME-TAG mode. (Tic-Visit :proposal-id 17470 :visit-id "55" :proposal-version -1 :trans-version "20250624" :date "01-Oct-2025 14:55:31.0" :trans-errors '(:WARNINGS 4 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "32" :si-bright-earth-limb-angle 20.0 :data-volume 104464 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "55" :obset-id "55" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "55" :obset-id "A5" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "55" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2487 :al-overhead-at-end 0 :internal-dur-at-end 386 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2867 :pcs-gap 0 ) false 1 0 It will probably be best to acquire on Io instead while sunlit, shortly before transit first contact. A few of the pattern exposures while still in sunlight wouldn't be terrible. We prefer to have one long TIME-TAG exposure and simply move the pointing during the exposure, but I didn't see a good way to set this up. We do not vary FP-POS because we are looking for time variability and thus prefer to not change the instruments settings during the exposure. The NUV wavelengths are less critical to positioning for the gain-sag. First step is to stare while on Io itself. use postarg x=-3 and y=3 to offset in roughly east of Jupiter direction, assuming roll angle ~45 to Jupiter North as typical. This SO2 absorption at higher altitude away from Io is the primary objective. More like 4.2 arcsec offset with sqrt(2). use postarg x=-6 and y=6 to offset in roughly east of Jupiter direction, assuming roll angle ~45 to Jupiter North as typical. The 6 arcsec location provides more of a baseline without much SO2 absorption. More like 8.5 arcsec offset with sqrt(2). 1723838439622 Using ephemeris for target 17470-60-EUROPA-ACQ Using ephemeris for target 17470-60-IO-ECLIPSE-VIS-LOKI-STARE The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. 1726148916000 264.5913842797558 (Tic-Visit :proposal-id 17470 :visit-id "60" :proposal-version -1 :trans-version "20240604" :date "16-Aug-2024 15:00:39.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 166192 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "60" :obset-id "60" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "60" :obset-id "A0" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "60" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2173 :al-overhead-at-end 0 :internal-dur-at-end 585 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 1 0 Checkbox size may need to be adjusted to expected size of Europa. Europa is 17.4-17.5 pixels on Sept. 9-14 Added a wavecal and a Fringe flat. 1723733727271 Using ephemeris for target 17470-61-EUROPA-ACQ Using ephemeris for target 17470-61-IO-ECLIPSE-VIS-LOKI-SCAN The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Added a fringe flat, but skip the wavecal (visit 60 has a wavecal for cross-reference). 1760248827000 279.7196837011895 (Tic-Visit :proposal-id 17470 :visit-id "61" :proposal-version -1 :trans-version "20240604" :date "15-Aug-2024 09:55:27.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 166224 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "61" :obset-id "61" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "61" :obset-id "A1" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "61" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2169 :al-overhead-at-end 0 :internal-dur-at-end 585 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 1 0 Checkbox size may need to be adjusted to expected size of Europa. Europa is 16.68 pixels on Oct. 12. 1721226514650 Using ephemeris for target 17470-62-EUROPA-ACQ Using ephemeris for target 17470-62-IO-ECLIPSE-VIS-S2 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. 1731651861000 263.0 (Tic-Visit :proposal-id 17470 :visit-id "62" :proposal-version -1 :trans-version "20240604" :date "17-Jul-2024 09:28:34.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 92608 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "62" :obset-id "62" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "62" :obset-id "A2" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "62" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2164 :al-overhead-at-end 0 :internal-dur-at-end 399 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 1 0 Checkbox size may need to be adjusted to expected size of Europa. Europa is 17.4-17.5 pixels on Sept. 9-14 1721095647145 Using ephemeris for target 17470-63-EUROPA-ACQ Using ephemeris for target 17470-63-IO-ECLIPSE-VIS-NA-SCAN The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. 1763612407000 265.71620724278495 (Tic-Visit :proposal-id 17470 :visit-id "63" :proposal-version -1 :trans-version "20240604" :date "15-Jul-2024 21:07:26.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 129408 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "63" :obset-id "63" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "63" :obset-id "A3" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "63" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2166 :al-overhead-at-end 0 :internal-dur-at-end 439 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 1 0 Checkbox size may need to be adjusted to expected size of Europa. Europa is 17.4-17.5 pixels on Sept. 9-14 1758895281789 Using ephemeris for target 17470-64-EUROPA-ACQ Using ephemeris for target 17470-64-IO-ECLIPSE-VIS-HALPHA The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. /System/Volumes/Data/solaris/user1/williamj/hst/work/cycle31/OP-cache/17470-v64.xml 1763154722000 281.8000210815291 (Tic-Visit :proposal-id 17470 :visit-id "64" :proposal-version -1 :trans-version "20250624" :date "26-Sep-2025 10:01:21.0" :trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 92576 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "64" :obset-id "64" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "64" :obset-id "A4" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "64" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2148 :al-overhead-at-end 0 :internal-dur-at-end 399 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2507 :pcs-gap 0 ) false 1 1 Checkbox size may need to be adjusted to expected size of Europa. Europa is 17.4-17.5 pixels on Sept. 9-14 1723733261548 Using ephemeris for target 17470-65-EUROPA-ACQ Using ephemeris for target 17470-65-IO-ECLIPSE-VIS-K The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. 1763765166000 280.2084964827733 (Tic-Visit :proposal-id 17470 :visit-id "65" :proposal-version -1 :trans-version "20240604" :date "15-Aug-2024 09:47:41.0" :trans-errors '(:WARNINGS 2 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 129408 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "65" :obset-id "65" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "65" :obset-id "A5" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "65" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2172 :al-overhead-at-end 0 :internal-dur-at-end 836 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 1 0 Checkbox size may need to be adjusted to expected size of Europa. Europa is 17.4-17.5 pixels on Sept. 9-14 1724853910847 Using ephemeris for target 17470-66-IO-ECLIPSE-INGRESS-COS-NUV Timing link suitability includes constraints ([68 After 66 by at most 2.2 days]) The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. (Tic-Visit :proposal-id 17470 :visit-id "66" :proposal-version -1 :trans-version "20240604" :date "28-Aug-2024 09:05:10.0" :trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "32" :si-bright-earth-limb-angle 20.0 :data-volume 313312 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "66" :obset-id "66" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "66" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2467 :al-overhead-at-end 0 :internal-dur-at-end 67 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "66" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2519 :al-overhead-at-end 0 :internal-dur-at-end 388 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 2 0 1724853913458 Using ephemeris for target 17470-67-EUROPA-ACQ Using ephemeris for target 17470-67-IO-ECLIPSE-EGRESS-COS-NUV The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. This observation requires acquisition from a sunlit moon, followed by a blind offset to a moon in shadow. Europa is used here, but Ganymede or Callisto should be used if Europa is too close to Jupiter. No longer able to do EGRESS's (Tic-Visit :proposal-id 17470 :visit-id "67" :proposal-version -1 :trans-version "20240604" :date "28-Aug-2024 09:05:13.0" :trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "32" :si-bright-earth-limb-angle 20.0 :data-volume 278496 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "67" :obset-id "67" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "67" :obset-id "A7" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "67" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2467 :al-overhead-at-end 0 :internal-dur-at-end 57 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "67" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2519 :al-overhead-at-end 0 :internal-dur-at-end 388 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 2 0 1723838557820 Using ephemeris for target 17470-68-EUROPA-ACQ Using ephemeris for target 17470-68-IO-ECLIPSE-STIS-NUV Timing link suitability includes constraints ([68 After 66 by at most 2.2 days]) The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. STIS NUV context for COS NUV ingress and egress observations. I have linked it to after ingress observation, could just as easily be before egress observation by 0 to 52 hr. We need to double check sensitivity of long wavelength S2 aurora emissions with CCD versus MAMA. Might switch to MAMA. (Tic-Visit :proposal-id 17470 :visit-id "68" :proposal-version -1 :trans-version "20240604" :date "16-Aug-2024 15:02:37.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 55648 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "68" :obset-id "68" :pcs-mode "FGS" ) (Tic-Obset :proposal-id 17470 :visit-id "68" :obset-id "A8" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "68" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2172 :al-overhead-at-end 0 :internal-dur-at-end 360 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 1 0 Make sure to offset to Io once Europa is acquired 1699603562470 Using ephemeris for target 17470-80-IO-SURFACE-STIS-VIS-LEADING ephemeris data for target 17470-80-IO-SURFACE-STIS-VIS-LEADING does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.274 to 25.089. ephemeris interval: 23.304 to 25.305 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. (Tic-Visit :proposal-id 17470 :visit-id "80" :proposal-version -1 :trans-version "20230626" :date "10-Nov-2023 09:06:01.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 153984 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "80" :obset-id "80" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "80" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2447 :al-overhead-at-end 0 :internal-dur-at-end 301 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "80" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2501 :al-overhead-at-end 0 :internal-dur-at-end 339 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 2 0 Visit planned for Dec 4, 2023. Io diameter is 1.22 and CHECKBOX thus 1.22/0.05 = 24.4 ~ 25 1723732640422 Using ephemeris for target 17470-8B-IO-SURFACE-STIS-VIS-LEADING ephemeris data for target 17470-8B-IO-SURFACE-STIS-VIS-LEADING does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.089. ephemeris interval: 24.031 to 26.032 The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. This is a duplicate of visit 80 with longer science exposures in orbit 1 and the G750L wavecal pushed into occultation. 1708899449000 72.21513188842371 (Tic-Visit :proposal-id 17470 :visit-id "8B" :proposal-version -1 :trans-version "20240604" :date "15-Aug-2024 09:37:19.0" :trans-errors '(:WARNINGS 3 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 139744 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "8B" :obset-id "8B" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "8B" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2186 :al-overhead-at-end 0 :internal-dur-at-end 301 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "8B" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2180 :al-overhead-at-end 0 :internal-dur-at-end 323 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2553 :pcs-gap 0 ) false 2 2 Visit planned for Dec 4, 2023. Io diameter is 1.22 and CHECKBOX thus 1.22/0.05 = 24.4 ~ 25 1703604110244 Using ephemeris for target 17470-81-IO-SURFACE-STIS-VIS-TRAILING ephemeris data for target 17470-81-IO-SURFACE-STIS-VIS-TRAILING does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.089. ephemeris interval: 23.365 to 26.001 The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. /System/Volumes/Data/solaris/user1/williamj/hst/work/cycle31/OP-cache/17470-v81.xml 1705305457000 70.46001054380079 (Tic-Visit :proposal-id 17470 :visit-id "81" :proposal-version -1 :trans-version "20230626" :date "26-Dec-2023 10:21:49.0" :trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 153952 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "81" :obset-id "81" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "81" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2539 :al-overhead-at-end 0 :internal-dur-at-end 301 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "81" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2501 :al-overhead-at-end 0 :internal-dur-at-end 339 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 2 1 1759428520360 /System/Volumes/Data/solaris/user1/williamj/hst/work/cycle31/OP-cache/17470-v91.xml HOPR repeat of visit 81 (Tic-Visit :proposal-id 17470 :visit-id "91" :proposal-version -1 :trans-version "20250624" :date "02-Oct-2025 14:08:38.0" :trans-errors '(:WARNINGS 2 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 153952 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "91" :obset-id "91" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "91" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2539 :al-overhead-at-end 0 :internal-dur-at-end 301 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2867 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "91" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2521 :al-overhead-at-end 0 :internal-dur-at-end 339 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2867 :pcs-gap 0 ) false 2 2 1724338216379 Using ephemeris for target 17470-82-IO-SURFACE-STIS-FUV-45 ephemeris data for target 17470-82-IO-SURFACE-STIS-FUV-45 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.089. ephemeris interval: 23.365 to 26.001 The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. (Tic-Visit :proposal-id 17470 :visit-id "82" :proposal-version -1 :trans-version "20240604" :date "22-Aug-2024 09:50:16.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 661680 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "82" :obset-id "82" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "82" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2533 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "82" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2530 :al-overhead-at-end 0 :internal-dur-at-end 450 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 2 0 Visit planned for Dec 2, 2023. Io diameter is 1.22 and CHECKBOX thus 1.22/0.05 = 24.4 ~ 25 1723838788244 Using ephemeris for target 17470-83-IO-SURFACE-STIS-FUV-135 ephemeris data for target 17470-83-IO-SURFACE-STIS-FUV-135 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.274 to 25.089. ephemeris interval: 23.304 to 25.305 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. 1708153533000 74.610508401158 (Tic-Visit :proposal-id 17470 :visit-id "83" :proposal-version -1 :trans-version "20240604" :date "16-Aug-2024 15:06:28.0" :trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 661648 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "83" :obset-id "83" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "83" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2467 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "83" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2520 :al-overhead-at-end 0 :internal-dur-at-end 450 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 2 0 1723838794073 Using ephemeris for target 17470-84-IO-SURFACE-STIS-FUV-225 ephemeris data for target 17470-84-IO-SURFACE-STIS-FUV-225 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.089. ephemeris interval: 23.365 to 26.001 The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. 1709571349000 69.95888035391201 (Tic-Visit :proposal-id 17470 :visit-id "84" :proposal-version -1 :trans-version "20240604" :date "16-Aug-2024 15:06:33.0" :trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 661648 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "84" :obset-id "84" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "84" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2439 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "84" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2495 :al-overhead-at-end 0 :internal-dur-at-end 450 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 2 0 1724338245251 Using ephemeris for target 17470-85-IO-SURFACE-STIS-FUV-315 ephemeris data for target 17470-85-IO-SURFACE-STIS-FUV-315 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.089. ephemeris interval: 23.365 to 26.001 The scheduling data was generated by CASM 32.0. CASM was run in Phase II mode. (Tic-Visit :proposal-id 17470 :visit-id "85" :proposal-version -1 :trans-version "20240604" :date "22-Aug-2024 09:50:45.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "24" :si-bright-earth-limb-angle 20.0 :data-volume 661648 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "85" :obset-id "85" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "85" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2531 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "85" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2530 :al-overhead-at-end 0 :internal-dur-at-end 450 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 2 0 1724763315820 Using ephemeris for target 17470-86-IO-SURFACE-COS-LEADING ephemeris data for target 17470-86-IO-SURFACE-COS-LEADING does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.325 to 25.213. ephemeris interval: 24.213 to 26.213 The scheduling data was generated by CASM 32.1.3. CASM was run in Phase II mode. 1726490012000 265.83228955144796 (Tic-Visit :proposal-id 17470 :visit-id "86" :proposal-version -1 :trans-version "20240627" :date "27-Aug-2024 14:55:15.0" :trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 295888 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "86" :obset-id "86" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "86" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2529 :al-overhead-at-end 0 :internal-dur-at-end 57 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "86" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2531 :al-overhead-at-end 0 :internal-dur-at-end 388 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 2 0 This acquisition mode/setup was used successfully used in program 15147 1721226622878 Using ephemeris for target 17470-87-IO-SURFACE-COS-TRAILING The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. 1723199049000 263.4870025008063 (Tic-Visit :proposal-id 17470 :visit-id "87" :proposal-version -1 :trans-version "20240604" :date "17-Jul-2024 09:30:22.0" :trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 278496 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17470 :visit-id "87" :obset-id "87" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17470 :visit-id "87" :orbit-number 1 :pcs-time 380 :si-vis-utilization 2528 :al-overhead-at-end 0 :internal-dur-at-end 57 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17470 :visit-id "87" :orbit-number 2 :pcs-time 380 :si-vis-utilization 2519 :al-overhead-at-end 0 :internal-dur-at-end 388 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2913 :pcs-gap 0 ) false 2 0 This acquisition mode/setup was used successfully used in program 15147.