0Assigned ID: 6615
----- Attempting Submission 1 (Thu Apr 10 19:07:00 GMT 2025) -----Could not connect to APT Status Server
A target acquisition should probably be performed before doing
spectroscopy or coronography with STIS or COS.
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.
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.
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.Updated position angle and scan rate values for targets in visits 2 and 3 - will still need a small tweek once they are scheduled for a specific time.
Updated exposure order and wavecals after visibility period ends.
Updated scan rates for visit 2 and increases second exposure times to fill orbits in visits 2 and 3.1608904481----- Attempting Submission 3 (Mon Oct 13 19:09:11 GMT 2025) -----
----- Attempting Submission 4 (Fri Oct 24 14:46:57 GMT 2025) -----
----- Attempting Submission 5 (Tue Nov 25 13:30:46 GMT 2025) -----No target acq. is required and no ETC runs - exposure times are based on past observations.Identifying Auroral Currents at JupiterPrior to the arrival of JUNO at Jupiter, the acceleration of high energy charged particles producing the bright aurora was thought to be well understood. During its close passes, however, the expected magnetic field-aligned potential structures accelerating the electrons into Jupiter's atmosphere have not been found, even when flying through magnetic flux tubes of bright aurora. Things are more complicated than thought, and other processes have to involve the acceleration of ions and electrons below JUNO's altitude in the form of ionospheric currents in auroral regions. Ionospheric current systems strongly heat the neutral atmosphere, and HST can measure the H2 temperature at the emission altitudes by resolving H2 ro-vibrational emissions. High temperatures indicate Joule heating from electric currents, which are carried by ions across magnetic field lines (in the case of Jupiter, mainly protons). The strong heating locations can be identified across the auroral oval using HST/STIS with G140M. In addition, proton-excited auroral emissions can be identified through Doppler-shifted H Lyman-alpha emissions from charge exchange of fast protons with atmospheric neutrals. This is an emission signature that HST can measure, however there are only two prior observations with the spectral resolution and sensitivity to detect it. This proposal is to perform scans across Jupiter's northern auroral region to identify regions of ionospheric heating/currents and proton-excited aurora. The observations will be scheduled close in time to JUNO perijove passes, which will record the charged particle environment in Jupiter's auroral regions.The observations will use the STIS G140M grating with the 52 x 0.5 arc sec aperture positioned across the northern auroral zone on Jupiter. The nominal roll angles in the past have been good for these observations, since Jupiter is always near the ecliptic plane, and no added constraints are needed. In cycle 33 Jupiter is observable in reduced gyro mode (RGM) from 1 Nov. to mid-Dec. 2026 and again at the end of the cycle. Another criterion is to have a line of sight Doppler shift (mainly from the Earth orbital motion) greater than 10 km/sec to prevent geocoronal H atoms from scattering the line center photons from Jupiter. The observations will be scheduled as close in time as is practical to Juno perijove (PJ) passes for comparison of the Juno charged particle data with the HST spectra. During cycle 33 with HST in RGM the possible passes are PJ 78 (19 Nov. 2025), PJ 79 (21 Dec. 2025), and PJ 88 (11 Oct. 2026).
The counting rates with G140M spectra and STIS FUV imaging of Jupiter are well below the upper limits for the MAMA detectors. From past observations the count rate for G140M is 1.6 counts/sec-kiloRayleigh from a 1 arc sec area. Jupiter's aurora are a few hundred kiloRayleighs (kR) in brightness, and the resolution is .025 arc sec (about 100 km at Jupiter). We will coadd rows to increase the sensitivity, i.e. a 0.5 arc sec area along the aperture (2000 km at Jupiter) will give 480 counts/kR with the counts divided into H2 bands and H line emission. Counting ~ 25 bands in the spectrum in Fig. 1, this gives 200 counts/band for a 10 kR emission for a sensitivity limit. After years of FUV observations of Jupiter with HST / STIS the methods for bright object protection are well established. The auroral emission region will be placed in the lower half of the UV-MAMA detector active area to avoid the area of highest dark counts in the upper left quadrant.
The STIS G140M grating spectral resolution of 0.97 A (for diffuse emission filling the 0.5 arc sec aperture) resolves the H2 bands and allows for continuum detection (Fig. 2). Compared with model profiles (Fig. 1) this can also detect Doppler shifted Lyman-a emission down to ~ 100 eV energy for fast protons. In a 600 sec. integration time, the count rate of 200 counts/band for a 10 kR emission is sufficient to provide an accurate temperature measurement. It also provides a sensitive search for proton-excited emissions down to the level of a kilo-Rayleigh.
Each visit will consist of two orbits, and each orbit will have the G140M time-tagged spectral scan followed by a short (100 sec) STIS MAMA F25SRF2 image to establish the auroral brightness distribution. The rest of the time will be spent with G140M slowly scanned across the auroral emission region. The complete auroral oval is about 10 arc sec across, and the data can be divided into time steps depending in part on the angle of the aperture on the planet. To the extent that the aperture is aligned E/W on Jupiter, more of the emission region will fall in the aperture at each step, and longer segments can be used. We will determine the exact pattern of the scan once the date and angle of the aperture from the nominal HST roll angle are known. Assuming ~ 5 aperture positions in a given orbit, we will get 500 sec. per observation step. Assigning two HST orbits to each visit will greatly improve the sensitivity to the known highly variable auroral emissions.Several of the investigators are highly experienced with HST observation planning and data reduction (Clarke, Gerard, Grodent, Nichols, Bonfond). Theoretical modeling of the production of auroral emissions from incident protons is included (Gerard, Grodent) as well as radiative transfer modeling of Lyman-alpha emission in the auroral atmosphere (Chaufray, Gladstone). Co-I J.-C. Gerard has the code used to analyze the STIS spectra and fit temperatures to the data. Co-I T. Greathouse from the JUNO UVS team will be the point of contact for comparison of JUNO data with the HST data, along with R. Gladstone. J. Clarke and M. Rutala are expert in running the custom data reduction pipeline on the HST data. The proposers have collectively led more than 50 HST GO programs.Solar System Astronomy6falsefalsefalsefalsefalsefalsefalseSUPPORTEDSOLAR SYSTEMYESNumbers for POS_ANGLE offset and scan rate have been updated for the time of observation.PLANETPlanet Jupiter North AuroraSTD=JUPITERTYPE=POS_ANGLE,RAD=20,ANG=0,REF=NORTH,R_RAD=-60,R_ANG=90,EPOCH=18-NOV-2025:08:42:00,EpochTimeScale=UTCNOT OCC OF JUPITER-NORTH-SPEC-1 BY JUPITER FROM EARTH,
CML OF JUPITER FROM EARTH BETWEEN 140 260EARTHSOLAR SYSTEMYESNumbers for POS_ANGLE offset and scan rate are placeholders - actual values will depend on when visit is scheduled and can be updated then.PLANETPlanet Jupiter North AuroraSTD=JUPITERTYPE=POS_ANGLE,RAD=20,ANG=0,REF=NORTH,R_RAD=-30,R_ANG=45,EPOCH=19-DEC-2025:19:32:00,EpochTimeScale=UTCNOT OCC OF JUPITER-NORTH-SPEC-2 BY JUPITER FROM EARTH,
CML OF JUPITER FROM EARTH BETWEEN 140 260EARTHSOLAR SYSTEMYESNumbers for POS_ANGLE offset and scan rate are placeholders - actual values will depend on when visit is scheduled and can be updated then.PLANETPlanet Jupiter North AuroraSTD=JUPITERTYPE=POS_ANGLE,RAD=20,ANG=0,REF=NORTH,R_RAD=-60,R_ANG=90,EPOCH=11-DEC-2026:00:00:00,EpochTimeScale=UTCNOT OCC OF JUPITER-NORTH-SPEC-3 BY JUPITER FROM EARTH,
CML OF JUPITER FROM EARTH BETWEEN 140 260EARTHSTIS/FUV-MAMASpectroscopicNoNoG140M1222STIS/FUV-MAMAImagingNoNoF25SRF2STIS/FUV-MAMASpectroscopicNoNoG140M1222STIS/FUV-MAMAImagingNoNoF25SRF2STIS/FUV-MAMASpectroscopicNoNoG140M1222STIS/FUV-MAMAImagingNoNoF25SRF2Using ephemeris for target 18048-01-JUPITER-NORTH-SPEC-1ephemeris data for target 18048-01-JUPITER-NORTH-SPEC-1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.244 to 27.120. ephemeris interval: 25.273 to 27.274The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.BETWEEN range is set for 3 days closest to JUNO orbital pass by Jupiter. This includes 7 Jupiter CML windows. Window can be expanded if needed to schedule.
No target acquisition is needed for extended target - we derive pointing from image of Jupiter.
ETC not used for highly variable auroral brightness - modes and exp. times based on prior observations and not close to STIS count rate limit.1763454689000277.1216535860873(Tic-Visit
:proposal-id 18048
:visit-id "01"
:proposal-version -1
:trans-version "20250929"
:date "25-Nov-2025 08:27:50.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 591328
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18048
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18048
:visit-id "01"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2229
:al-overhead-at-end 0
:internal-dur-at-end 380
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2979
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18048
:visit-id "01"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2237
:al-overhead-at-end 0
:internal-dur-at-end 668
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2979
:pcs-gap 0
)false20Using ephemeris for target 18048-02-JUPITER-NORTH-SPEC-2ephemeris data for target 18048-02-JUPITER-NORTH-SPEC-2 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.291 to 27.120. ephemeris interval: 25.304 to 27.305The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.BETWEEN range is set for 3 days closest to JUNO orbital pass by Jupiter. This includes 7 Jupiter CML windows. Window can be expanded if needed to schedule.
No target acquisition is needed for extended target - we derive pointing from image of Jupiter.
ETC not used for highly variable auroral brightness - modes and exp. times based on prior observations and not close to STIS count rate limit.1766171990000293.2331134300499(Tic-Visit
:proposal-id 18048
:visit-id "02"
:proposal-version -1
:trans-version "20250929"
:date "25-Nov-2025 08:29:11.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 591328
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18048
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18048
:visit-id "02"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2589
:al-overhead-at-end 0
:internal-dur-at-end 380
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2979
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18048
:visit-id "02"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2587
:al-overhead-at-end 0
:internal-dur-at-end 668
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2979
:pcs-gap 0
)false20Using ephemeris for target 18048-03-JUPITER-NORTH-SPEC-3ephemeris data for target 18048-03-JUPITER-NORTH-SPEC-3 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.244 to 27.120. ephemeris interval: 25.273 to 27.274The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.BETWEEN range is set for 3 days closest to JUNO orbital pass by Jupiter. This includes 7 Jupiter CML windows. Window can be expanded if needed to schedule.
No target acquisition is needed for extended target - we derive pointing from image of Jupiter.
ETC not used for highly variable auroral brightness - modes and exp. times based on prior observations and not close to STIS count rate limit.(Tic-Visit
:proposal-id 18048
:visit-id "03"
:proposal-version -1
:trans-version "20250929"
:date "25-Nov-2025 08:29:40.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 591328
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18048
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18048
:visit-id "03"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2589
:al-overhead-at-end 0
:internal-dur-at-end 380
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2979
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18048
:visit-id "03"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2587
:al-overhead-at-end 0
:internal-dur-at-end 668
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2979
:pcs-gap 0
)false20