This pattern is not used in this proposal.
POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant.
FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser
POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant.
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
POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant.
FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser
POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant.
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
POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant.
FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser
POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant.
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
POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant.
FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser
POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant.
FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser
POS TARG & PATTERN should be used carefully with WFC3 quad filters to avoid placing the target on the vignetted part of the field of view or moving it to another quadrant.
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 browserupdated visit 1 with timing notes for perijove 14 (july 2018). adjusted
quad filter POSTARG values for jupiter diameter = 39.7 arcsec.1297796819----- Attempting Submission 16 (Mon Jun 18 01:27:50 GMT 2018) -----explanations of problems:
PATTERN NOT USED: we store it for potential future use. if a visibility window
is shorter than normal, we would consider using this 2-step pattern instead
of a 3-step pattern.
FLASH LEVEL TOO LOW: the target is bright and extended. it will be surrounded
by a scattered-light halo. this halo serves to fill traps during readout, performing
the same function of post-flash.
POS-TARG/PATTERN WARNING: we have carefully calculated POS-TARG values
with respect to quad filter apertures, to try to reduce overall slews (and thus make
it easier to maintain guide stars). POS-TARG values are set so as to keep the
target away from areas affected by the quad filter edges.Wide Field Coverage for Juno (WFCJ): Jupiter's 2D Wind Field and Cloud StructureJuno will take novel measurements in the jovian system during HST Cycles 23, 24, and 25. This proposal supports Juno's neutral atmospheric investigation, which includes measurements with an IR imager/spectrometer (JIRAM) and the Microwave Radiometer (MWR). Both will achieve high spatial resolution as the orbiter swoops past Jupiter, in between the radiation belts and the cloud tops. But instrument fields of view are small compared to the planet, so HST observations would provide valuable context and complementary information.
We propose to measure Jupiter's 2D wind field, as well as UV/optical cloud colors (and their evolution). We will measure winds using sets of global maps that cover two of Juno's perijove passes, characterizing the time-varying dynamics of waves, jets, vortices, and storms. The remaining perijove passes will be covered by snapshot (1-orbit) visits, sufficient to characterize feature morphology along each Juno track at high resolution. These observations will give crucial context for MWR observations and enable more precise retrievals from MWR data.
Earth-based support is particularly important for Juno, due to its highly eccentric orbit and specialized instrumentation. WFC3/UVIS imaging can play an important role in the effort, since no other facility can obtain precise 2D wind fields and UV/optical photometry at high spatial resolution. Without the HST component of this campaign, key dynamical constraints will be missing.The name/label of each visit gives:
* PJ (Juno perijove) number
* SNAPshot or GLOBal map type observation
* sequence (A-K or A-Q for global maps)
* subarray size (1K or 2K)
Juno perijove timing information as of 21 July 2016 is used in this version of the Phase II. Observations are timed so that the longitude of each Juno perijove pass is observed by HST near disk center. If this timing doesn't work out for the same jovian rotation as the perijove pass, then observations may be taken 10 hours before or after, to catch the perijove longitude one jovian rotation before or after the perijove pass. Comments on the first visit of each PJ give some timing details for each perijove.
SNAPshot observations consist of a single visit, to image the perijove longitude with HST.
GLOBal map sequences use 11 orbits (PJ6) or 17 orbits (PJ8) to measure zonal winds using multiple global maps. In each global map sequence, visits are labeled A-K or A-Q in order.
Subarrays are used to reduce buffer dumps. When Jupiter's diameter is < 39.5", we use 1K subarrays. When Jupiter's apparent size is larger, we use 2K subarrays.
Jupiter's rotation blurs the image by about 1 pixel in a 12-sec exposure. So for filters requiring long exposure times, we try to take multiple frames to reduce rotational blurring. We do not dither frames to improve PSF sampling; instead, we let the planet's rotation dither the map data for us.
We do not use pre-flash because the target is extended and PSF wings create a halo of light around the target. This serves the same purpose as flash.Solar System6falsefalsefalsefalsefalsefalsefalseAVAILABLESOLAR SYSTEMYESPLANETJupiter atmosphereSTD=JUPITEREARTHWFC3/UVISImagingNoNoF225WWFC3/UVISImagingNoNoF275WWFC3/UVISImagingNoNoF343NWFC3/UVISImagingNoNoF395NWFC3/UVISImagingNoNoF502NWFC3/UVISImagingNoNoF631NWFC3/UVISImagingNoNoFQ727NWFC3/UVISImagingNoNoFQ750NWFC3/UVISImagingNoNoFQ889NWFC3/UVISImagingNoNoF225WWFC3/UVISImagingNoNoF275WWFC3/UVISImagingNoNoF343NWFC3/UVISImagingNoNoF395NWFC3/UVISImagingNoNoF502NWFC3/UVISImagingNoNoF631NWFC3/UVISImagingNoNoFQ727NWFC3/UVISImagingNoNoFQ750NWFC3/UVISImagingNoNoFQ889NWFC3/UVISImagingNoNoF225WWFC3/UVISImagingNoNoF275WWFC3/UVISImagingNoNoF343NWFC3/UVISImagingNoNoF395NWFC3/UVISImagingNoNoF502NWFC3/UVISImagingNoNoF631NWFC3/UVISImagingNoNoFQ727NWFC3/UVISImagingNoNoFQ750NWFC3/UVISImagingNoNoFQ889NWFC3/UVISImagingNoNoF225WWFC3/UVISImagingNoNoF275WWFC3/UVISImagingNoNoF343NWFC3/UVISImagingNoNoF395NWFC3/UVISImagingNoNoF502NWFC3/UVISImagingNoNoF631NWFC3/UVISImagingNoNoFQ727NWFC3/UVISImagingNoNoFQ750NWFC3/UVISImagingNoNoFQ889NPOS-TARGDITHER0.135LINEfalsefalse346.84WFC3-UVIS-DITHER-LINE-3PT1falsePOS-TARGDITHER0.145LINEfalsefalse246.84WFC3-UVIS-DITHER-LINE2falsePJ 19, UT time and CML:
2019-04-06 12:14:00 99.7(Tic-Visit
:proposal-id 15159
:visit-id "52"
:proposal-version -1
:trans-version "20181130"
:date "13-Mar-2019 17:35:16.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 703872
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15159
:visit-id "52"
:obset-id "52"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15159
:visit-id "52"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2482
:al-overhead-at-end 0
:internal-dur-at-end 652
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3142
:pcs-gap 0
)false10PJ 19, UT time and CML:
2019-04-06 12:14:00 99.7(Tic-Visit
:proposal-id 15159
:visit-id "53"
:proposal-version -1
:trans-version "20181130"
:date "13-Mar-2019 17:35:22.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 703872
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15159
:visit-id "53"
:obset-id "53"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15159
:visit-id "53"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2482
:al-overhead-at-end 0
:internal-dur-at-end 652
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3142
:pcs-gap 0
)false10PJ 19, UT time and CML:
2019-04-06 12:14:00 99.7(Tic-Visit
:proposal-id 15159
:visit-id "54"
:proposal-version -1
:trans-version "20181130"
:date "13-Mar-2019 17:35:29.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 703872
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15159
:visit-id "54"
:obset-id "54"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15159
:visit-id "54"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2482
:al-overhead-at-end 0
:internal-dur-at-end 652
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3142
:pcs-gap 0
)false10Using ephemeris for target 15159-01-JUPITERephemeris data for target 15159-01-JUPITER does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 17.213 to 19.152. ephemeris interval: 18.151 to 20.153The scheduling data was generated by CASM 26.0.CASM was run in Phase II mode.PJ 14, UT time and CML:
2018-07-16 05:18:44 74.50
Position the Juno perijove longitude near Jupiter disk center. Secondary option is a window +/-10 hours away, to image the same location on an adjacent Jupiter rotation.
Try for start times within an hour of these times:
2018-Jul-15 18:40
2018-Jul-16 04:35 (best one)
2018-Jul-16 14:30153174843000090.4774998552524(Tic-Visit
:proposal-id 15159
:visit-id "01"
:proposal-version -1
:trans-version "20180409"
:date "17-Jun-2018 21:21:33.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 703872
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15159
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15159
:visit-id "01"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2482
:al-overhead-at-end 0
:internal-dur-at-end 652
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)false10Gyro Bias update to be executed in the same orbit following visit 15159 02.false-1-1