Unraveling electron acceleration mechanisms in Ganymede's space environment through N-S conjugate imagery of Jupiter's aurora
There is strong scientific interest in Ganymede (Jupiter's third Galilean moon) and its surrounding environment, which stems from the likely presence of a liquid water ocean underneath its icy crust and from its internally driven magnetic field. The interaction of the latter with Jupiter's magnetospheric plasma and its magnetic field gives rise to a unique situation in our solar system implying a mini-magnetosphere embedded within a giant-magnetosphere. This interaction generates Ganymede's ultraviolet auroral footprint in Jupiter's atmosphere. We propose to investigate the strong auroral connection between Jupiter and Ganymede and the variable characteristics of Ganymede's magnetosphere with an innovative approach, taking advantage of the large scale north-south asymmetries of Jupiter's magnetic field. The results obtained for Ganymede will be compared with the case of small injected hot plasma bubbles observed by the Galileo spacecraft and whose size and location are similar to those of Ganymede's magnetosphere. HST is currently the sole instrument capable of obtaining this information which pins down the proposed mechanisms linking the source and sink regions of auroral particles in the giant planets' magnetospheres.
We use 9 HST orbits to observe Jupiter's northern and southern auroral UV emissions with the time tag mode of the STIS UV-MAMA Ly-alpha free (F25SRF2 filter). The visibility of Ganymede's footprint principally depends on its orbital phase angle. Accordingly, the proposed scheduling will ensure that GFP is always visible from HST for each orbit.
Each individual orbit is designed as follows: a first uninterrupted time tagged image (~700s) of the southern hemisphere followed by a time tag image (~700s) of the north; this set is then repeated once in order to get a S-N-S-N sequence during a single orbit. The first image is obtained when the CML is lowest, which favors viewing of the southern hemisphere, while at the end of the orbit the larger CML will favor the northern hemisphere. This orbit design is executed 9 times at least two Jovian rotations apart (2*10hrs, ~1 day) in order to sample different magnetospheric conditions and increase the chances to observe injection signatures. As a result, the 9 orbits may be considered independent orbits.
Short Time-tag sequences with the F25SRF2 filter have been acquired several times in previous programs without any risk for the FUV MAMA detector. In several sequences, gaps occurred as a consequence of buffer overflows. These only occur when too large a fraction of the Jovian disk appears on the image. However, past experience (GO-11649) shows that the count rate is lowered down to less than 16,000 counts per second (cps) using appropriate pointing such that only the polar region is in the field of view. Since the count rate can be kept below 20,000 cps, sequences as long as 2700s can be acquired without data gaps while we request sequences of ~700s.
SOLAR SYSTEM
12
false
false
0.0
0.0
false
false
false
SUPPORTED
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD and ANG are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS repel wire should be ~parallel to the equator in order to prevent it from masking the auroral region of interest.
PLANET
Jupiter southern aurora 1
STD=JUPITER
TYPE=POS_ANGLE,RAD=28,ANG=170,REF=NORTH
CML OF JUPITER FROM EARTH BETWEEN 80 110,
OLG OF GANYMEDE BETWEEN 110 200
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD and ANG are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS repel wire should be ~parallel to the equator in order to prevent it from masking the auroral region of interest.
PLANET
Jupiter southern aurora 1
STD=JUPITER
TYPE=POS_ANGLE,RAD=26,ANG=190,REF=NORTH
CML OF JUPITER FROM EARTH BETWEEN 100 130,
OLG OF GANYMEDE BETWEEN 110 200
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD and ANG are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS repel wire should be ~parallel to the equator in order to prevent it from masking the auroral region of interest.
PLANET
Jupiter southern aurora 1
STD=JUPITER
TYPE=POS_ANGLE,RAD=26,ANG=190,REF=NORTH
CML OF JUPITER FROM EARTH BETWEEN 100 130,
OLG OF GANYMEDE BETWEEN 110 200
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD and ANG are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS repel wire should be ~parallel to the equator in order to prevent it from masking the auroral region of interest.
PLANET
Jupiter southern aurora 1
STD=JUPITER
TYPE=POS_ANGLE,RAD=20.7,ANG=171,REF=NORTH
CML OF JUPITER FROM EARTH BETWEEN 80 110,
OLG OF GANYMEDE BETWEEN 110 200
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD and ANG are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS repel wire should be ~parallel to the equator in order to prevent it from masking the auroral region of interest.
PLANET
Jupiter southern aurora 1
STD=JUPITER
TYPE=POS_ANGLE,RAD=20.7,ANG=171,REF=NORTH
CML OF JUPITER FROM EARTH BETWEEN 80 110,
OLG OF GANYMEDE BETWEEN 110 200
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD and ANG are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS repel wire should be ~parallel to the equator in order to prevent it from masking the auroral region of interest.
PLANET
Jupiter southern aurora 1
STD=JUPITER
TYPE=POS_ANGLE,RAD=20.7,ANG=171,REF=NORTH
CML OF JUPITER FROM EARTH BETWEEN 80 110,
OLG OF GANYMEDE BETWEEN 110 200
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD and ANG are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS repel wire should be ~parallel to the equator in order to prevent it from masking the auroral region of interest.
PLANET
Jupiter southern aurora 1
STD=JUPITER
TYPE=POS_ANGLE,RAD=20.7,ANG=171,REF=NORTH
CML OF JUPITER FROM EARTH BETWEEN 80 110,
OLG OF GANYMEDE BETWEEN 110 200
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD and ANG are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS repel wire should be ~parallel to the equator in order to prevent it from masking the auroral region of interest.
PLANET
Jupiter northern aurora 1
STD=JUPITER
TYPE=POS_ANGLE,RAD=26,ANG=0,REF=NORTH
CML OF JUPITER FROM EARTH BETWEEN 80 120,
OLG OF GANYMEDE BETWEEN 110 210
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD and ANG are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS repel wire should be ~parallel to the equator in order to prevent it from masking the auroral region of interest.
PLANET
Jupiter northern aurora 1
STD=JUPITER
TYPE=POS_ANGLE,RAD=24,ANG=10,REF=NORTH
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD and ANG are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS repel wire should be ~parallel to the equator in order to prevent it from masking the auroral region of interest.
PLANET
Jupiter northern aurora 1
STD=JUPITER
TYPE=POS_ANGLE,RAD=24,ANG=10,REF=NORTH
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD and ANG are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS repel wire should be ~parallel to the equator in order to prevent it from masking the auroral region of interest.
PLANET
Jupiter northern aurora 1
STD=JUPITER
TYPE=POS_ANGLE,RAD=20.0,ANG=6,REF=NORTH
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD and ANG are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS repel wire should be ~parallel to the equator in order to prevent it from masking the auroral region of interest.
PLANET
Jupiter northern aurora 1
STD=JUPITER
TYPE=POS_ANGLE,RAD=20.0,ANG=6,REF=NORTH
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD and ANG are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS repel wire should be ~parallel to the equator in order to prevent it from masking the auroral region of interest.
PLANET
Jupiter northern aurora 1
STD=JUPITER
TYPE=POS_ANGLE,RAD=20.0,ANG=6,REF=NORTH
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD and ANG are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS repel wire should be ~parallel to the equator in order to prevent it from masking the auroral region of interest.
PLANET
Jupiter northern aurora 1
STD=JUPITER
TYPE=POS_ANGLE,RAD=20.0,ANG=6,REF=NORTH
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD and ANG are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS repel wire should be ~parallel to the equator in order to prevent it from masking the auroral region of interest.
PLANET
Jupiter southern aurora 1
STD=JUPITER
TYPE=POS_ANGLE,RAD=28,ANG=170,REF=NORTH
CML OF JUPITER FROM EARTH BETWEEN 80 130,
OLG OF GANYMEDE BETWEEN 110 220
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD and ANG are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS repel wire should be ~parallel to the equator in order to prevent it from masking the auroral region of interest.
PLANET
Jupiter southern aurora 1
STD=JUPITER
TYPE=POS_ANGLE,RAD=20.7,ANG=171,REF=NORTH
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD and ANG are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS repel wire should be ~parallel to the equator in order to prevent it from masking the auroral region of interest.
PLANET
Jupiter southern aurora 1
STD=JUPITER
TYPE=POS_ANGLE,RAD=20.7,ANG=171,REF=NORTH
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD and ANG are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS repel wire should be ~parallel to the equator in order to prevent it from masking the auroral region of interest.
PLANET
Jupiter southern aurora 1
STD=JUPITER
TYPE=POS_ANGLE,RAD=20.7,ANG=171,REF=NORTH
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD and ANG are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS repel wire should be ~parallel to the equator in order to prevent it from masking the auroral region of interest.
PLANET
Jupiter southern aurora 1
STD=JUPITER
TYPE=POS_ANGLE,RAD=20.7,ANG=171,REF=NORTH
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD, ANG and R_RAD are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS spectral slit should be almost parallel (+/-30°) to the equatorial plane
PLANET
Jupiter northern aurora SPECTRO
STD=JUPITER
TYPE=POS_ANGLE,RAD=24,ANG=-20,REF=NORTH,R_RAD=-410.0,R_ANG=1709.0,EPOCH=16-JAN-2013:14:05:00,EpochTimeScale=UTC
CML OF JUPITER FROM EARTH BETWEEN 120 180,
OLG OF GANYMEDE BETWEEN 100 240
EARTH
SOLAR SYSTEM
Constraints on CML and OLG may be relaxed by +/-10°
POS_ANGLE RAD, ANG and R_RAD are date and ROLL dependent. Current values are suitable for 1-DEC-2012 +/- 1 month.
Ideally, STIS spectral slit should be almost parallel (+/-30°) to the equatorial plane
PLANET
Jupiter northern aurora SPECTRO
STD=JUPITER
TYPE=POS_ANGLE,RAD=23.2,ANG=-20,REF=NORTH,R_RAD=-400.0,R_ANG=1709.0,EPOCH=2013.024:10:32:00,EpochTimeScale=UTC
CML OF JUPITER FROM EARTH BETWEEN 120 180,
OLG OF GANYMEDE BETWEEN 100 240
EARTH
STIS/FUV-MAMA
Imaging
No
No
F25SRF2
STIS/FUV-MAMA
Imaging
No
No
F25SRF2
STIS/FUV-MAMA
Imaging
No
No
F25SRF2
STIS/FUV-MAMA
Imaging
No
No
F25SRF2
STIS/FUV-MAMA
Imaging
No
No
F25SRF2
STIS/FUV-MAMA
Imaging
No
No
F25SRF2
STIS/FUV-MAMA
Imaging
No
No
F25SRF2
STIS/FUV-MAMA
Imaging
No
No
F25SRF2
STIS/FUV-MAMA
Imaging
No
No
F25SRF2
Using ephemeris for target 12883-01-JUP-S-1
ephemeris data for target 12883-01-JUP-S-1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.212 to 14.092. ephemeris interval: 12.274 to 14.274
Using ephemeris for target 12883-01-JUP-N-1
ephemeris data for target 12883-01-JUP-N-1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.212 to 14.092. ephemeris interval: 12.274 to 14.274
Using ephemeris for target 12883-01-JUP-S-2
ephemeris data for target 12883-01-JUP-S-2 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.212 to 14.092. ephemeris interval: 12.274 to 14.274
The scheduling data was generated by CASM 20.2.
CASM was run in Phase II mode.
Each orbit may be considered independently. Ideally, each orbit should be executed at least 1 day apart.
For Timing Requirements, the 1-Oct-2012 1-Feb-2013 window is more favorable than the 28-Aug-2013 30-Sep-2013 window.
1352911361000
265.34778469427704
(Tic-Visit
:proposal-id 12883
:visit-id "01"
:proposal-version -1
:trans-version "20120802"
:date "17-Oct-2012 12:04:59.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 1182784
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 12883
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Obset
:proposal-id 12883
:visit-id "01"
:obset-id "A1"
:pcs-mode "FGS"
)
(Tic-Obset
:proposal-id 12883
:visit-id "01"
:obset-id "B1"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 12883
:visit-id "01"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2896
: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 3229
:pcs-gap 0
)
false
1
0
ETC estimated from GO 11649
ETC estimated from GO 11649
ETC estimated from GO 11649
Using ephemeris for target 12883-02-JUP-S-1
ephemeris data for target 12883-02-JUP-S-1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.212 to 14.092. ephemeris interval: 12.274 to 14.274
Using ephemeris for target 12883-02-JUP-N-1
ephemeris data for target 12883-02-JUP-N-1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.212 to 14.092. ephemeris interval: 12.274 to 14.274
Using ephemeris for target 12883-02-JUP-S-2
ephemeris data for target 12883-02-JUP-S-2 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.212 to 14.092. ephemeris interval: 12.274 to 14.274
The scheduling data was generated by CASM 20.2.
CASM was run in Phase II mode.
Each orbit may be considered independently. Ideally, each orbit should be executed at least 1 day apart.
For Timing Requirements, the 1-Oct-2012 1-Feb-2013 window is more favorable than the 28-Aug-2013 30-Sep-2013 window.
1360877783000
68.31809267298439
(Tic-Visit
:proposal-id 12883
:visit-id "02"
:proposal-version -1
:trans-version "20120802"
:date "17-Oct-2012 12:05:00.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 1182784
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 12883
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Obset
:proposal-id 12883
:visit-id "02"
:obset-id "A2"
:pcs-mode "FGS"
)
(Tic-Obset
:proposal-id 12883
:visit-id "02"
:obset-id "B2"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 12883
:visit-id "02"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2895
: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 3229
:pcs-gap 0
)
false
1
0
ETC estimated from GO 11649
ETC estimated from GO 11649
ETC estimated from GO 11649
Using ephemeris for target 12883-03-JUP-S-1
ephemeris data for target 12883-03-JUP-S-1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.212 to 14.092. ephemeris interval: 12.274 to 14.274
Using ephemeris for target 12883-03-JUP-N-1
ephemeris data for target 12883-03-JUP-N-1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.212 to 14.092. ephemeris interval: 12.274 to 14.274
Using ephemeris for target 12883-03-JUP-S-2
ephemeris data for target 12883-03-JUP-S-2 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.212 to 14.092. ephemeris interval: 12.274 to 14.274
The scheduling data was generated by CASM 20.2.
CASM was run in Phase II mode.
Each orbit may be considered independently. Ideally, each orbit should be executed at least 1 day apart.
For Timing Requirements, the 1-Oct-2012 1-Feb-2013 window is more favorable than the 28-Aug-2013 30-Sep-2013 window.
1361486498000
80.38196751924261
(Tic-Visit
:proposal-id 12883
:visit-id "03"
:proposal-version -1
:trans-version "20120802"
:date "17-Oct-2012 12:05:01.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 1182784
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 12883
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Obset
:proposal-id 12883
:visit-id "03"
:obset-id "A3"
:pcs-mode "FGS"
)
(Tic-Obset
:proposal-id 12883
:visit-id "03"
:obset-id "B3"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 12883
:visit-id "03"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2895
: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 3229
:pcs-gap 0
)
false
1
0
ETC estimated from GO 11649
ETC estimated from GO 11649
ETC estimated from GO 11649
Using ephemeris for target 12883-04-JUP-S-1
ephemeris data for target 12883-04-JUP-S-1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.212 to 14.092. ephemeris interval: 12.274 to 14.274
Using ephemeris for target 12883-04-JUP-N-1
ephemeris data for target 12883-04-JUP-N-1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.212 to 14.092. ephemeris interval: 12.274 to 14.274
Using ephemeris for target 12883-04-JUP-S-2
ephemeris data for target 12883-04-JUP-S-2 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.212 to 14.092. ephemeris interval: 12.274 to 14.274
The scheduling data was generated by CASM 20.2.
CASM was run in Phase II mode.
Each orbit may be considered independently. Ideally, each orbit should be executed at least 1 day apart.
For Timing Requirements, the 1-Oct-2012 1-Feb-2013 window is more favorable than the 28-Aug-2013 30-Sep-2013 window.
1359091725000
71.42754306601151
(Tic-Visit
:proposal-id 12883
:visit-id "04"
:proposal-version -1
:trans-version "20120802"
:date "17-Oct-2012 12:05:02.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 1182784
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 12883
:visit-id "04"
:obset-id "04"
:pcs-mode "FGS"
)
(Tic-Obset
:proposal-id 12883
:visit-id "04"
:obset-id "A4"
:pcs-mode "FGS"
)
(Tic-Obset
:proposal-id 12883
:visit-id "04"
:obset-id "B4"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 12883
:visit-id "04"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2895
: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 3229
:pcs-gap 0
)
false
1
0
ETC estimated from GO 11649
ETC estimated from GO 11649
ETC estimated from GO 11649
Using ephemeris for target 12883-05-JUP-S-1
ephemeris data for target 12883-05-JUP-S-1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.212 to 14.092. ephemeris interval: 12.274 to 14.274
Using ephemeris for target 12883-05-JUP-N-1
ephemeris data for target 12883-05-JUP-N-1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.212 to 14.092. ephemeris interval: 12.274 to 14.274
Using ephemeris for target 12883-05-JUP-S-2
ephemeris data for target 12883-05-JUP-S-2 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.212 to 14.092. ephemeris interval: 12.274 to 14.274
The scheduling data was generated by CASM 20.2.
CASM was run in Phase II mode.
Each orbit may be considered independently. Ideally, each orbit should be executed at least 1 day apart.
For Timing Requirements, the 1-Oct-2012 1-Feb-2013 window is more favorable than the 28-Aug-2013 30-Sep-2013 window.
1362807163000
79.14558129617012
(Tic-Visit
:proposal-id 12883
:visit-id "05"
:proposal-version -1
:trans-version "20120802"
:date "17-Oct-2012 12:05:04.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 1182784
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 12883
:visit-id "05"
:obset-id "05"
:pcs-mode "FGS"
)
(Tic-Obset
:proposal-id 12883
:visit-id "05"
:obset-id "A5"
:pcs-mode "FGS"
)
(Tic-Obset
:proposal-id 12883
:visit-id "05"
:obset-id "B5"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 12883
:visit-id "05"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2895
: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 3229
:pcs-gap 0
)
false
1
0
ETC estimated from GO 11649
ETC estimated from GO 11649
ETC estimated from GO 11649
Using ephemeris for target 12883-06-JUP-S-1
ephemeris data for target 12883-06-JUP-S-1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.288 to 14.274. ephemeris interval: 13.273 to 15.274
Using ephemeris for target 12883-06-JUP-N-1
ephemeris data for target 12883-06-JUP-N-1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.288 to 14.274. ephemeris interval: 13.273 to 15.274
The scheduling data was generated by CASM 21.2.
CASM was run in Phase II mode.
Each orbit may be considered independently. Ideally, each orbit should be executed at least 1 day apart.
For Timing Requirements, the 1-Oct-2012 1-Feb-2013 window is more favorable than the 28-Aug-2013 30-Sep-2013 window.
(Tic-Visit
:proposal-id 12883
:visit-id "06"
:proposal-version -1
:trans-version "20130502"
:date "11-Oct-2013 09:25:00.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 1530752
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 12883
:visit-id "06"
:obset-id "06"
:pcs-mode "FGS"
)
(Tic-Obset
:proposal-id 12883
:visit-id "06"
:obset-id "A6"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 12883
:visit-id "06"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2896
: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 3229
:pcs-gap 0
)
false
1
0
ETC estimated from GO 11649
ETC estimated from GO 11649
Using ephemeris for target 12883-07-JUP-S-1
ephemeris data for target 12883-07-JUP-S-1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.288 to 14.274. ephemeris interval: 13.273 to 15.274
Using ephemeris for target 12883-07-JUP-N-1
ephemeris data for target 12883-07-JUP-N-1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.288 to 14.274. ephemeris interval: 13.273 to 15.274
The scheduling data was generated by CASM 21.2.
CASM was run in Phase II mode.
Each orbit may be considered independently. Ideally, each orbit should be executed at least 1 day apart.
For Timing Requirements, the 1-Oct-2012 1-Feb-2013 window is more favorable than the 28-Aug-2013 30-Sep-2013 window.
(Tic-Visit
:proposal-id 12883
:visit-id "07"
:proposal-version -1
:trans-version "20130502"
:date "11-Oct-2013 09:27: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 1530752
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 12883
:visit-id "07"
:obset-id "07"
:pcs-mode "FGS"
)
(Tic-Obset
:proposal-id 12883
:visit-id "07"
:obset-id "A7"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 12883
:visit-id "07"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2896
: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 3229
:pcs-gap 0
)
false
1
0
ETC estimated from GO 11649
ETC estimated from GO 11649
Using ephemeris for target 12883-08-JUP-N-SPECTRO
ephemeris data for target 12883-08-JUP-N-SPECTRO does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.212 to 14.092. ephemeris interval: 12.274 to 14.274
The scheduling data was generated by CASM 20.2.
CASM was run in Phase II mode.
Each orbit may be considered independently. Ideally, each orbit should be executed at least 1 day apart.
One of the two G140L "sp orbits" should preferentially appear at the beginning of the program.
For Timing Requirements, the 1-Oct-2012 1-Feb-2013 window is more favorable than the 28-Aug-2013 30-Sep-2013 window.
1358344659000
75.3424401418682
(Tic-Visit
:proposal-id 12883
:visit-id "08"
:proposal-version -1
:trans-version "20120802"
:date "17-Oct-2012 12:05:08.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 1843984
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 12883
:visit-id "08"
:obset-id "08"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 12883
:visit-id "08"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2607
:al-overhead-at-end 0
:internal-dur-at-end 625
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3229
:pcs-gap 0
)
false
1
0
ETC estimated from GO 11649
Using ephemeris for target 12883-09-JUP-N-SPECTRO
ephemeris data for target 12883-09-JUP-N-SPECTRO does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 12.212 to 14.092. ephemeris interval: 12.274 to 14.274
The scheduling data was generated by CASM 20.2.
CASM was run in Phase II mode.
Each orbit may be considered independently. Ideally, each orbit should be executed at least 1 day apart.
One of the two G140L "sp orbits" should preferentially appear at the beginning of the program.
For Timing Requirements, the 1-Oct-2012 1-Feb-2013 window is more favorable than the 28-Aug-2013 30-Sep-2013 window.
1359022795000
94.52801066618417
(Tic-Visit
:proposal-id 12883
:visit-id "09"
:proposal-version -1
:trans-version "20120802"
:date "17-Oct-2012 12:05:09.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 1843984
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 12883
:visit-id "09"
:obset-id "09"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 12883
:visit-id "09"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2607
:al-overhead-at-end 0
:internal-dur-at-end 625
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3229
:pcs-gap 0
)
false
1
0
ETC estimated from GO 11649