Correction of a few typos. 998453773 Assigned ID: 1380 ----- Attempting Submission 1 (Sun Jan 31 00:57:40 GMT 2021) ----- HST Phase I Proposal 1380 successfully submitted. Receipt: # 1380-1 ----- Attempting Submission 2 (Sun Jan 31 02:27:09 GMT 2021) ----- - This version splits up orbit 3 of visit 1 and orbit 1 of visit 2 into two science exposures, each. It uses WAVECAL = NO to reduce overhead. - New Version: TARGET = WAVE is added at the end of each orbit during visit 1 2115023835 ----- Attempting Submission 1 (Wed Mar 24 20:56:26 GMT 2021) ----- ----- Attempting Submission 2 (Wed May 05 22:20:02 GMT 2021) ----- HST Phase II Proposal 16499 successfully submitted. Receipt: # 16499-2 ----- Attempting Submission 3 (Sun May 09 22:02:49 GMT 2021) ----- HST Phase II Proposal 16499 successfully submitted. Receipt: # 16499-3 ----- Attempting Submission 4 (Wed May 12 22:58:42 GMT 2021) ----- Providing Context for Juno's only Close Ganymede Flyby Jupiter's planet-sized satellite Ganymede is the only known moon with a mini-magnetosphere and two auroral ovals. In its only close flyby of Ganymede, NASA's Juno spacecraft is scheduled to pass through the satellite's magnetotail on June 7, 2021. The magnetotail is the region where magnetic reconnection and energization is expected to be strongest. Juno's flyby provides a unique opportunity to make significant progress about the poorly understood processes which energize Ganymede's magnetosphere and power its auroral emissions. The flyby occurs over a short time-span of only approximately 30 minutes. We propose 6 HST orbits to observe Ganymede's aurora which will provide important context and assist with the interpretation of the Juno observations. We request three HST orbits before the Juno flyby to establish the state of the aurora prior to the flyby and three additional orbits after the Juno flyby to monitor the changes in Ganymede's aurora after the flyby. The moon's aurora is known to vary on timescales of Juno's flyby and the proposed HST observations. The collection of HST observations over these timescales will enable an investigation of how conditions and events observed by Juno are related to changes in Ganymede's aurora observed by HST. The Juno flyby provides a very important and unique opportunity for HST to complement investigations of NASA's solar system exploration program and improve our understanding of the only magnetosphere in the solar system without a bow shock. We plan 2 visits of 3 orbits each with STIS to observe Ganymede at western elongation in coordination with the Juno flyby on June 7, 2021. We will use STIS with grating G140L at central wavelength 1425 A and a slit of 2.0 arcsec width. The size of Ganymede is slightly less than 2.0 arcsec and thus Ganymede's aurora can be completely observed. We will observe in TIMETAG mode to resolve temporal variability and to remove any parts of the orbits highly contaminated by geocoronal noise. The scheduling is dictated by the timing of the Juno flyby. We ask for three HST orbits before the Juno flyby and three orbits after the Juno flyby. Depending on the availabilty of the Hydro Mode for HST's guiding modes, the three orbits of each visit will be executed consecutively or will be split up into one visit with two consecutive orbits and one visit with only one orbit. If the Hydro Mode is available, we chose for the visit after the Juno flyby three orbits (#4,5,6) the ones immediately available after closest approach. The orbits before the Juno flyby (#1,2,3) we chose to be close, but at the same time symmetric with respect to Ganymede's position in the plasma sheet similar to the orbits #4,5,6. Therefore we plan not to observe during the last available HST orbit just before HST enters the phase impaired by the SAA. Depending on the results of the final timing and the availabilities of orbits in the time leading up the Ganymede flyby, we might choose different combinations for the orbits #1,2,3. We will weigh between proximity to the time of the flyby and symmetry with orbits #4,5,6. The team possess the expertise to successfully carry out the proposed investigation: PI Saur has been PI on 5 HST proposal in the past. He and his group including Co-Is Willmes and Wennmacher also work on models of Ganymede's mini-magnetosphere. Co-Is Roth, Bonfond, Grodent, Retherford and Hansen are experienced HST observers and will provide expertise in the data analysis. Co-I Strobel is an expert on aeronomy of atmospheres on planets and moons. Co-I Rymer works on energetic particles in the Jovian system. The team consists of various members from the Juno team or affiliated with the Juno team who will help with the coordination and interpretation of the science results. These are Juno's PI Bolton and team members Bagenal, Gladstone, Hansen, Clark, and Orton. The described expertise of the team is demonstrated through a large number of publications in their respective fields. Solar System Astronomy 6 false false true false false false false SUPPORTED SOLAR SYSTEM SATELLITE Satellite Ganymede STD=JUPITER STD=GANYMEDE NOT OCC OF GANYMEDE-PJ34 BY JUPITER FROM EARTH, SEP OF GANYMEDE-PJ34 IO FROM EARTH GT 10", SEP OF GANYMEDE-PJ34 EUROPA FROM EARTH GT 10", SEP OF GANYMEDE-PJ34 CALLISTO FROM EARTH GT 10" EARTH STIS/FUV-MAMA Spectroscopic No No G140L 1425 Using ephemeris for target 16499-01-GANYMEDE-PJ34 ephemeris data for target 16499-01-GANYMEDE-PJ34 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 20.214 to 22.121. ephemeris interval: 21.120 to 23.121 The scheduling data was generated by CASM 29.0. CASM was run in Phase II mode. 46 /Users/saur/Organisation/Proposals/2021_01_HST_Ganymede/2021_Phase_II_c/OP-cache/16499-v01.xml (Tic-Visit :proposal-id 16499 :visit-id "01" :proposal-version -1 :trans-version "20200619" :date "13-May-2021 00:41:16.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 1026944 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 16499 :visit-id "01" :obset-id "01" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 16499 :visit-id "01" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2367 :al-overhead-at-end 0 :internal-dur-at-end 367 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2760.0 :pcs-gap 0 ) (Tic-Orbit :proposal-id 16499 :visit-id "01" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2368 :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 2760.0 :pcs-gap 0 ) (Tic-Orbit :proposal-id 16499 :visit-id "01" :orbit-number 3 :pcs-time 0 :si-vis-utilization 2368 :al-overhead-at-end 0 :internal-dur-at-end 629 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2760.0 :pcs-gap 0 ) true 3 0 Using ephemeris for target 16499-02-GANYMEDE-PJ34 ephemeris data for target 16499-02-GANYMEDE-PJ34 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 20.214 to 22.121. ephemeris interval: 21.120 to 23.121 Timing link suitability includes constraints ([2A After 02 by 0.1 to 0.1 days]) The scheduling data was generated by CASM 29.0. CASM was run in Phase II mode. /Users/saur/Organisation/Proposals/2021_01_HST_Ganymede/2021_Phase_II_c/OP-cache/16499-v02.xml (Tic-Visit :proposal-id 16499 :visit-id "02" :proposal-version -1 :trans-version "20200619" :date "13-May-2021 00:41: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 296352 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 16499 :visit-id "02" :obset-id "02" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 16499 :visit-id "02" :orbit-number 1 :pcs-time 301 :si-vis-utilization 2617 :al-overhead-at-end 0 :internal-dur-at-end 629 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2918 :pcs-gap 0 ) true 1 0 Using ephemeris for target 16499-2A-GANYMEDE-PJ34 ephemeris data for target 16499-2A-GANYMEDE-PJ34 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 20.214 to 22.121. ephemeris interval: 21.120 to 23.121 Timing link suitability includes constraints ([2A After 02 by 0.1 to 0.1 days]) The scheduling data was generated by CASM 29.0. CASM was run in Phase II mode. 46 /Users/saur/Organisation/Proposals/2021_01_HST_Ganymede/2021_Phase_II_c/OP-cache/16499-v2A.xml (Tic-Visit :proposal-id 16499 :visit-id "2A" :proposal-version -1 :trans-version "20200619" :date "13-May-2021 00:41:35.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 16499 :visit-id "2A" :obset-id "2A" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 16499 :visit-id "2A" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2367 :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 2760.0 :pcs-gap 0 ) (Tic-Orbit :proposal-id 16499 :visit-id "2A" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2368 :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 2760.0 :pcs-gap 0 ) true 2 0 Using ephemeris for target 16499-03-GANYMEDE-PJ34 ephemeris data for target 16499-03-GANYMEDE-PJ34 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 20.214 to 22.121. ephemeris interval: 21.120 to 23.121 The scheduling data was generated by CASM 29.0. CASM was run in Phase II mode. /private/var/folders/8n/b6y3vv413c32g8cdfrt_339h0000gq/T/OPVisit10357188368625233255.xml (Tic-Visit :proposal-id 16499 :visit-id "03" :proposal-version -1 :trans-version "20200619" :date "13-May-2021 00:51: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 661680 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 16499 :visit-id "03" :obset-id "03" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 16499 :visit-id "03" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2525 :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 2918 :pcs-gap 0 ) (Tic-Orbit :proposal-id 16499 :visit-id "03" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2526 :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 2918 :pcs-gap 0 ) true 2 0 In case Hybrid Mode is not available, i.e. 3 consecutive orbits cannot be executed, we split visit 'Consec: Before JUNO C/A' into 2 visits with 1 and 2 orbits each. They are labeled 'Non-consec: Before Juno C/A'. This visit contains two orbits. I Using ephemeris for target 16499-04-GANYMEDE-PJ34 ephemeris data for target 16499-04-GANYMEDE-PJ34 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 20.214 to 22.121. ephemeris interval: 21.120 to 23.121 The scheduling data was generated by CASM 29.0. CASM was run in Phase II mode. /private/var/folders/8n/b6y3vv413c32g8cdfrt_339h0000gq/T/OPVisit8277666897095655686.xml (Tic-Visit :proposal-id 16499 :visit-id "04" :proposal-version -1 :trans-version "20200619" :date "13-May-2021 00:51:06.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 296384 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 16499 :visit-id "04" :obset-id "04" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 16499 :visit-id "04" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2525 :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 2918 :pcs-gap 0 ) true 1 0 In case Hybrid Mode is not available, i.e., 3 consequtive orbits cannot be executed, we split visit 1 into two plus one visit labeled Non-conseq: Before Juno C/A'. This visit contains one orbit. Using ephemeris for target 16499-05-GANYMEDE-PJ34 ephemeris data for target 16499-05-GANYMEDE-PJ34 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 20.214 to 22.121. ephemeris interval: 21.120 to 23.121 The scheduling data was generated by CASM 29.0. CASM was run in Phase II mode. /private/var/folders/8n/b6y3vv413c32g8cdfrt_339h0000gq/T/OPVisit15540474707905500302.xml (Tic-Visit :proposal-id 16499 :visit-id "05" :proposal-version -1 :trans-version "20200619" :date "13-May-2021 00:51:11.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 296384 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 16499 :visit-id "05" :obset-id "05" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 16499 :visit-id "05" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2525 :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 2918 :pcs-gap 0 ) true 1 0 In case Hybrid Mode is not available, i.e., 3 consequtive orbits cannot be executed, we split visit 2 into two plus one visit labeled 'Non-conseq: After Juno C/A'. This visit contains only one orbit. Using ephemeris for target 16499-06-GANYMEDE-PJ34 ephemeris data for target 16499-06-GANYMEDE-PJ34 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 20.214 to 22.121. ephemeris interval: 21.120 to 23.121 The scheduling data was generated by CASM 29.0. CASM was run in Phase II mode. /private/var/folders/8n/b6y3vv413c32g8cdfrt_339h0000gq/T/OPVisit11198271617624768473.xml (Tic-Visit :proposal-id 16499 :visit-id "06" :proposal-version -1 :trans-version "20200619" :date "13-May-2021 00:51:15.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 16499 :visit-id "06" :obset-id "06" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 16499 :visit-id "06" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2525 :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 2918 :pcs-gap 0 ) (Tic-Orbit :proposal-id 16499 :visit-id "06" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2526 :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 2918 :pcs-gap 0 ) true 2 0 In case Hybrid Mode is not available, i.e., 3 consequtive orbits cannot be executed, we split visit 2 into two plus one visit labeled Non-conseq: After Juno C/A'. This visit contains two orbits in a row.