0Assigned ID: 1229
----- Attempting Submission 1 (Fri Jan 17 23:23:09 GMT 2020) -----
----- Attempting Submission 2 (Sat Jan 18 04:41:00 GMT 2020) -----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
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
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
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
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
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 browserInitial Phase 2 submission, for Mid-Cycle 27 deadline March 19.324402679----- Attempting Submission 1 (Fri Mar 20 02:32:18 GMT 2020) -----FLASH warning - Diffuse light from the science target will be sufficient to compensate for CTE losses.
POS TARG + PATTERN warning - POS TARG is used in Quad frames (FQ619N) in order to minimize slew amount and allow same guide stars for the whole orbit. We have accounted for the size of the target, the size of the pattern, and the locations of regions affected by the quad filter edges in setting our POS TARG values. For the 512K subs, the pattern width is 0.145 arcsec, the target is < 2.5 arcsec, and the subarray FOV is 20.5", so the pattern is safe.The Disruption of a Dark Vortex on NeptuneNeptune's dark spot, named "NDS-2018" for its discovery date, is drifting toward the equator, while all previous Hubble-discovered dark spots have drifted poleward or remained fixed in latitude. It is thus the first dark spot behaving like the Great Dark Spot discovered by Voyager 2. Its drift resembles published numerical simulations, one of which predicts a planet-wide disturbance once the vortex crosses a critical latitude near 15 degrees.
The complete evolution of dark spots on Neptune is poorly understood due to sparse temporal sampling. There is only one other spot besides NDS-2018 whose origin can also be pinpointed (to within a year), and only two dark spots have been observed during their dissipation phases. The proposed observations would thus create the only complete record of the origin, evolution, and dissipation of a single neptunian dark vortex. This is also the first opportunity to observe the conjectured vortex dissipation pathway involving equatorward drift and disruption. HST Neptune observations in January 2020 provide an early indication of an imminent break-up (conjectured, but never observed).
New observations are urgently requested as soon as Neptune emerges from HST's solar exclusion zone, in May 2020. If the vortex is still present, observations would measure the morphology, position, and drift of the vortex prior to disruption. But the potential also exists to witness a never-before seen planetary-scale disturbance. Either way, observations are needed prior to anticipated annual Neptune imaging (Sept/Oct 2020) in order to give the first constraints on the dissipation timescale of a dark vortex.A set of 4-5 identical orbits, equally spaced in longitude over one Neptune rotation (16 hours). We need to cover all possible longitudes because the longitudinal drift rate of NDS-2018 varied between 2018 and 2019 data, leading to large uncertainties in the longitude at the time of observation. The program must be executed after conjunction (Neptune exceeds 55 deg from the Sun on 2020-May-05). We request observations as soon as feasible (but not disruptive) during the period after conjunction. All timing constraints are described in more detail in the Visit 1 comments.
We mitigate unstable pixels by dithering both spatially and temporally (i.e., using Neptune's changing rotational phase to dither). The F467M filter provides the highest contrast for dark spots, so we acquire the most frames per orbit in this filter. The frames will be spread evenly throughout the orbit, to maximize the range of longitudes covered at low emission angle.
F467M (512K SUB)
F547M (512K SUB)
F763M (512K SUB)
F845M (512K SUB)
FQ619NThe Team Expertise section is not required for Mid-Cycle proposals.Solar SystemPlanets and Planet Formation3falsefalsefalsefalsefalsefalsefalseSUPPORTEDSOLAR SYSTEMYESPLANETNeptuneSTD=NEPTUNEEARTHWFC3/UVISImagingNoNoF467MWFC3/UVISImagingNoNoF547MWFC3/UVISImagingNoNoF763MWFC3/UVISImagingNoNoF845MWFC3/UVISImagingNoNoFQ619NPOS-TARGDITHER0.145Standard WFC3/UVIS 2-pt line dither, for PSF sampling and bad-pix amelioration.LINEfalsefalse246.84WFC3-UVIS-DITHER-LINE1falseUsing ephemeris for target 16084-01-NEPTUNEephemeris data for target 16084-01-NEPTUNE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 19.213 to 21.091. ephemeris interval: 20.091 to 22.091Timing link suitability includes constraints ([Sequence (01 02 03 04 05) within 15.0 days] [02 After 01 by 0.1 to 0.1 days] [03 After 01 by 0.3 to 0.3 days] [04 After 01 by 0.4 to 0.4 days] [05 After 01 by 0.5 to 0.6 days])The scheduling data was generated by CASM 28.0.CASM was run in Phase II mode./solaris/user1/aroman/work/hst/OP-cache/16084-v01.xmlDesired visit timing is every other HST orbit. If this cannot be scheduled soon, then we can accept a pair of consecutive orbits (and thus a gap of 2 orbits) somewhere in the sequence. To capture this, we set a SEQ ALL VISITS WITHIN 15 HOURS condition.
Visit 5 must start 8 or 9 orbits after visit 1 (12:44 to 14:20 after), to span a full Neptune rotation, so we set a VISIT 5 AFTER VISIT 1 BY 12 TO 15 HOURS condition.
All visits must start after Neptune exceeds 55 deg solar elongation, so we set a AFTER 2020-May-05 condition on the first visit (but presumably this constraint is already covered by the HST planning system).(Tic-Visit
:proposal-id 16084
:visit-id "01"
:proposal-version -1
:trans-version "20191203"
:date "16-Apr-2020 11:02:06.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 223152
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 16084
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 16084
:visit-id "01"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2617
:al-overhead-at-end 0
:internal-dur-at-end 280
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3142
:pcs-gap 0
)true10Using ephemeris for target 16084-02-NEPTUNEephemeris data for target 16084-02-NEPTUNE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 19.213 to 21.091. ephemeris interval: 20.091 to 22.091Timing link suitability includes constraints ([Sequence (01 02 03 04 05) within 15.0 days] [02 After 01 by 0.1 to 0.1 days])The scheduling data was generated by CASM 28.0.CASM was run in Phase II mode./solaris/user1/aroman/work/hst/OP-cache/16084-v02.xml(Tic-Visit
:proposal-id 16084
:visit-id "02"
:proposal-version -1
:trans-version "20191203"
:date "16-Apr-2020 11:02:09.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 223152
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 16084
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 16084
:visit-id "02"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2617
:al-overhead-at-end 0
:internal-dur-at-end 280
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3142
:pcs-gap 0
)true10Using ephemeris for target 16084-03-NEPTUNEephemeris data for target 16084-03-NEPTUNE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 19.213 to 21.091. ephemeris interval: 20.091 to 22.091Timing link suitability includes constraints ([Sequence (01 02 03 04 05) within 15.0 days] [03 After 01 by 0.3 to 0.3 days])The scheduling data was generated by CASM 28.0.CASM was run in Phase II mode./solaris/user1/aroman/work/hst/OP-cache/16084-v03.xml(Tic-Visit
:proposal-id 16084
:visit-id "03"
:proposal-version -1
:trans-version "20191203"
:date "16-Apr-2020 11:02:12.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 223152
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 16084
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 16084
:visit-id "03"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2617
:al-overhead-at-end 0
:internal-dur-at-end 280
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3142
:pcs-gap 0
)true10Using ephemeris for target 16084-04-NEPTUNEephemeris data for target 16084-04-NEPTUNE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 19.213 to 21.091. ephemeris interval: 20.091 to 22.091Timing link suitability includes constraints ([Sequence (01 02 03 04 05) within 15.0 days] [04 After 01 by 0.4 to 0.4 days])The scheduling data was generated by CASM 28.0.CASM was run in Phase II mode./solaris/user1/aroman/work/hst/OP-cache/16084-v04.xml(Tic-Visit
:proposal-id 16084
:visit-id "04"
:proposal-version -1
:trans-version "20191203"
:date "16-Apr-2020 11:02:14.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 223152
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 16084
:visit-id "04"
:obset-id "04"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 16084
:visit-id "04"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2617
:al-overhead-at-end 0
:internal-dur-at-end 280
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3142
:pcs-gap 0
)true10Using ephemeris for target 16084-05-NEPTUNEephemeris data for target 16084-05-NEPTUNE does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 19.213 to 21.091. ephemeris interval: 20.091 to 22.091Timing link suitability includes constraints ([Sequence (01 02 03 04 05) within 15.0 days] [05 After 01 by 0.5 to 0.6 days])The scheduling data was generated by CASM 28.0.CASM was run in Phase II mode./solaris/user1/aroman/work/hst/OP-cache/16084-v05.xml(Tic-Visit
:proposal-id 16084
:visit-id "05"
:proposal-version -1
:trans-version "20191203"
:date "16-Apr-2020 11:02: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 223152
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 16084
:visit-id "05"
:obset-id "05"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 16084
:visit-id "05"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2617
:al-overhead-at-end 0
:internal-dur-at-end 280
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3142
:pcs-gap 0
)true10