Target JUPITER-NORTH-1: There is no need or capability to test the scheduling of observations of moving targets in Phase I. This warning will go away the next time the proposal is loaded.
Target JUPITER-NORTH-2: There is no need or capability to test the scheduling of observations of moving targets in Phase I. This warning will go away the next time the proposal is loaded.
Target JUPITER-NORTH-3: There is no need or capability to test the scheduling of observations of moving targets in Phase I. This warning will go away the next time the proposal is loaded.
Target JUPITER-NORTH-4: There is no need or capability to test the scheduling of observations of moving targets in Phase I. This warning will go away the next time the proposal is loaded.
Target JUPITER-NORTH-5: There is no need or capability to test the scheduling of observations of moving targets in Phase I. This warning will go away the next time the proposal is loaded.
Target JUPITER-NORTH-6: There is no need or capability to test the scheduling of observations of moving targets in Phase I. This warning will go away the next time the proposal is loaded.0Assigned ID: 4293
----- Attempting Submission 1 (Wed May 24 10:15:16 GMT 2023) -----
HST Phase I Proposal 4293 successfully submitted.
Receipt: # 4293-1These are related to the moving target.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.
Moss Ephemeris file "/Users/jdn4/Documents/Proposals/2023/HST/JointHST-JWST/visit-planner/17471_5.trh" is corrupted. Please contact your PC. Data in the file will not be used.
Sensitive exposures should have an ETC run number provided.This version changes Visit 05 to slew the slit as discussed. I note the error "Error (Visit Planner) Moss Ephemeris file "/Users/jdn4/Documents/Proposals/2023/HST/JointHST-JWST/visit-planner/17471_5.trh" is corrupted. Please contact your PC. Data in the file will not be used. The file is present but the data in the file is either missing or not in the expected format. Please check the file contents." I am not sure what this means - please advise?"-2084630956----- Attempting Submission 1 (Wed Sep 13 18:00:11 GMT 2023) -----
----- Attempting Submission 2 (Tue Dec 12 21:05:16 GMT 2023) -----I am not sure what the error "Error (Visit Planner): Moss Ephemeris file "/Users/jdn4/Documents/Proposals/2023/HST/JointHST-JWST/visit-planner/17471_5.trh" is corrupted. Please contact your PC. Data in the file will not be used.
Occurrence: 05
Explanation: The file is present but the data in the file is either missing or not in the expected format. Please check the file contents. " means. Please advise!Elucidating Jupiter's auroral processes with HST and JWSTThe unique partnership between HST and JWST available at this juncture presents an exciting new prospect to understand planetary auroral processes as never before, representing the most powerful remote sensing tool ever available to understand this phenomenon. We propose joint HST-JWST observations of Jupiter's prompt electron-excited far-ultraviolet (FUV) auroral emissions and near-infrared (NIR) H3+ thermal auroral emissions that will reveal the true nature and physics behind Jupiter's enigmatic and spectacular auroras. While the two observatories have observed Jupiter's auroras separately, they never observed them simultaneously. The next step in understanding the auroral processes is to compare simultaneous images of FUV and NIR emissions to address the following questions:
*How does the instantaneous FUV emission relate to the slower H3+ emission?
*How does the instantaneous energy input and temperature seen in FUV emission relate to H3+ thermal emissions?
*How do the H3+ thermal emissions relate to well-known FUV features, i.e. the main oval emission, polar emissions, satellite footprints, and dawn storms?
*What is the lifetime of H3+ ions in Jupiter's auroral ionosphere?
*What processes govern the energy balance in Jupiter's upper atmosphere?
Only HST can obtain the FUV high time- and spatial resolution auroral images and high-resolution spectra of Jupiter's FUV emissions, and only JWST can obtain the high time- and spatial resolution images and spectral images of Jupiter's polar H3+ emission required to address these science questions. These observations will yield high-profile discoveries and vital context for ongoing Juno observations of Jupiter's auroras.These observations will comprise 6 HST orbits using the STIS/FUV-MAMA instrument. Two groups of observations will be obtained, each comprising 3 visits of 1 orbit. All visits will observe the northern auroras. For the first group of observations, all observations will be STIS FUV auroral imaging, and will cover one interval when the northern auroras are presented toward Earth. Auroral images will be obtained using the F25SRF2 filter. Jupiter will be positioned using POS and ANG such that only the auroral region and nearby disc will be in the 25x25" field of view, and thus <1/4 of the detector is filled with the planet. We will obtain ~2200 s time-tagged exposures. The second set of observations will again observe one interval when the northern auroras are presented toward Earth, but will comprise 2 orbits of STIS imaging either side of one orbit of STIS FUV spectroscopy with the G140M grating at the 1222 A central wavelength and the 25 x 0.5 arcsec aperture with ~400s integrations. The aperture will be positioned across the auroral region and scanned across the auroral region in four ~400 s steps. The exact nature of this scan (i.e. slow smooth or stepped) will be determined once the guide star and ORIENT is known.The investigators on this proposal have unparalleled depth of experience studying the auroras of the outer planets, through HST and JWST observations, modelling, and spacecraft data analysis. In particular the team possesses through investigators Nichols and Clarke a significant history of HST/FUV observations, and the PI (Nichols) has previously successfully led as PI 8 HST programs of UV observations of Jupiter, Saturn, Ganymede and WASP-12b. The team posesses world-leading expertise of JWST observations of Jupiter's H3+ auroras; de Pater led the JWST ERS Outer Planets observing programme, on which Melin was a Co-I. Melin is a Science and Technology Facilities Council JWST Fellow, and has deep experience observing H3+ auroras of all the outer planets, and has experience with comparative IR and FUV studies of outer planet auroras using Cassini observations. Moore and Tao are experts in modelling the dynamics, structure and chemistry of Jupiter's auroral ionosphere and thermosphere, and in particular the relation between electron precipitation, FUV and H3+ emission. Nichols, Clarke, Melin and de Pater will reduce and analyse the auroral data. Moore and Tao will model the relation between the two emissions and the resulting inospheric dynamics and chemistry.Solar System Astronomy6falsefalsetruefalsefalsefalsefalse5.43trueSUPPORTEDSOLAR SYSTEMYESPLANETJupiter aurora northSTD=JUPITERTYPE=POS_ANGLE,RAD=23,ANG=355,REF=NORTHCML OF JUPITER FROM EARTH BETWEEN 100 240EARTHSOLAR SYSTEMYESPLANETJupiter aurora northSTD=JUPITERTYPE=POS_ANGLE,RAD=23,ANG=340,REF=NORTHCML OF JUPITER FROM EARTH BETWEEN 100 240EARTHSOLAR SYSTEMYESPLANETJupiter aurora northSTD=JUPITERTYPE=POS_ANGLE,RAD=23,ANG=328,REF=NORTHCML OF JUPITER FROM EARTH BETWEEN 100 260EARTHSOLAR SYSTEMYESPLANETJupiter aurora northSTD=JUPITERTYPE=POS_ANGLE,RAD=23,ANG=355,REF=NORTHCML OF JUPITER FROM EARTH BETWEEN 100 240EARTHSOLAR SYSTEMYESPLANETJupiter aurora northSTD=JUPITERTYPE=POS_ANGLE,RAD=20.3,ANG=339,REF=NORTH,R_RAD=-390,R_ANG=90,EPOCH=08-JAN-2024:00:25:00,EpochTimeScale=UTCCML OF JUPITER FROM EARTH BETWEEN 100 240EARTHSOLAR SYSTEMYESPLANETJupiter aurora northSTD=JUPITERTYPE=POS_ANGLE,RAD=23,ANG=325,REF=NORTHCML OF JUPITER FROM EARTH BETWEEN 100 260EARTHSTIS/FUV-MAMAImagingNoNoF25SRF2STIS/FUV-MAMAImagingNoNoF25SRF2STIS/FUV-MAMAImagingNoNoF25SRF2STIS/FUV-MAMAImagingNoNoF25SRF2STIS/FUV-MAMASpectroscopicNoNoG140M1222STIS/FUV-MAMAImagingNoNoF25SRF2Using ephemeris for target 17471-01-JUPITER-NORTH-1ephemeris data for target 17471-01-JUPITER-NORTH-1 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.334 to 25.335Timing link suitability includes constraints ([02 After 01 by at most 0.1 days])The scheduling data was generated by CASM 31.1.CASM was run in Phase II mode.Group 1, imaging observation 1. To execute simultaneously with Observation 1 of JWST proposal 4566. RAD and ANG are reasonable placeholders, and will be set once the orbit of HST is known.170348859000062.311021856410406(Tic-Visit
:proposal-id 17471
:visit-id "01"
:proposal-version -1
:trans-version "20230626"
:date "12-Dec-2023 20:52:42.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 1530800
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17471
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17471
:visit-id "01"
:orbit-number 1
:pcs-time 443
:si-vis-utilization 2270
: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 2713
:pcs-gap 0
)false10Using ephemeris for target 17471-02-JUPITER-NORTH-2ephemeris data for target 17471-02-JUPITER-NORTH-2 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.334 to 25.335Timing link suitability includes constraints ([02 After 01 by at most 0.1 days] [03 After 02 by at most 0.1 days])The scheduling data was generated by CASM 31.1.CASM was run in Phase II mode.Group 1, imaging observation 2. To execute simultaneously with Observation 1 of JWST proposal 4566. RAD and ANG are reasonable placeholders, and will be set once the orbit of HST is known.170349394600062.75949517995679(Tic-Visit
:proposal-id 17471
:visit-id "02"
:proposal-version -1
:trans-version "20230626"
:date "12-Dec-2023 20:52:43.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 1530800
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17471
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17471
:visit-id "02"
:orbit-number 1
:pcs-time 443
:si-vis-utilization 2270
: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 2713
:pcs-gap 0
)false10Using ephemeris for target 17471-03-JUPITER-NORTH-3ephemeris data for target 17471-03-JUPITER-NORTH-3 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.334 to 25.335Timing link suitability includes constraints ([03 After 02 by at most 0.1 days])The scheduling data was generated by CASM 31.1.CASM was run in Phase II mode.Group 1, imaging observation 3. To execute simultaneously with Observation 1 of JWST proposal 4566. RAD and ANG are reasonable placeholders, and will be set once the orbit of HST is known.170349964400063.29595458092291(Tic-Visit
:proposal-id 17471
:visit-id "03"
:proposal-version -1
:trans-version "20230626"
:date "12-Dec-2023 20:52:44.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 1530800
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17471
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17471
:visit-id "03"
:orbit-number 1
:pcs-time 443
:si-vis-utilization 2270
: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 2713
:pcs-gap 0
)false10Using ephemeris for target 17471-04-JUPITER-NORTH-4ephemeris data for target 17471-04-JUPITER-NORTH-4 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.334 to 25.335Timing link suitability includes constraints ([05 After 04 by at most 0.1 days])The scheduling data was generated by CASM 31.1.CASM was run in Phase II mode.Group 2, imaging observation 1. To execute simultaneously with Observation 2 of JWST proposal 4566. RAD and ANG are reasonable placeholders, and will be set once the orbit of HST is known.(Tic-Visit
:proposal-id 17471
:visit-id "04"
:proposal-version -1
:trans-version "20230626"
:date "14-Dec-2023 07:23: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 1530800
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17471
:visit-id "04"
:obset-id "04"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17471
:visit-id "04"
:orbit-number 1
:pcs-time 443
:si-vis-utilization 2270
: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 2713
:pcs-gap 0
)false10Could not find ephemeris /private/var/folders/zc/ljhf1lgn10b1yd9ytmwlp4jr00070l/T/visit-planner/17471_5.trh for target 17471-05-JUPITER-NORTH-5. Using default ephemeris /Applications/apt/CurrentHST/Mac/APT.app/Contents/MacOS/casm/casmfiles/moss/jupiter.trh for JUPITER.Timing link suitability includes constraints ([05 After 04 by at most 0.1 days] [06 After 05 by at most 0.1 days])The scheduling data was generated by CASM 31.1.CASM was run in Phase II mode.Group 2, spectral observation. To execute simultaneously with Observation 2 of JWST proposal 4566. RAD and ANG are reasonable placeholders, and will be set (along with RRAD and RANG if necessary) once the orbit of HST is known.(Tic-Visit
:proposal-id 17471
:visit-id "05"
:proposal-version -1
:trans-version "20230626"
:date "14-Dec-2023 07:23: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 156544
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17471
:visit-id "05"
:obset-id "05"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17471
:visit-id "05"
:orbit-number 1
:pcs-time 443
:si-vis-utilization 1958
: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 2713
:pcs-gap 0
)false10Using ephemeris for target 17471-06-JUPITER-NORTH-6ephemeris data for target 17471-06-JUPITER-NORTH-6 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.334 to 25.335Timing link suitability includes constraints ([06 After 05 by at most 0.1 days])The scheduling data was generated by CASM 31.1.CASM was run in Phase II mode.Group 2, imaging observation 2. To execute simultaneously with Observation 2 of JWST proposal 4566. RAD and ANG are reasonable placeholders, and will be set once the orbit of HST is known.(Tic-Visit
:proposal-id 17471
:visit-id "06"
:proposal-version -1
:trans-version "20230626"
:date "14-Dec-2023 07:23:42.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 1530800
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17471
:visit-id "06"
:obset-id "06"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17471
:visit-id "06"
:orbit-number 1
:pcs-time 443
:si-vis-utilization 2270
: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 2713
:pcs-gap 0
)false10