0Your proposal could not be saved.
Submission aborted.
Assigned ID: 1675
----- Attempting Submission 1 (Wed Mar 21 12:38:04 GMT 2018) -----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 browserUpdated "between" constraints for visit 5.1001228984----- Attempting Submission 1 (Mon May 21 08:18:44 GMT 2018) -----
----- Attempting Submission 2 (Thu Dec 13 08:38:50 GMT 2018) -----
----- Attempting Submission 3 (Mon Apr 15 09:06:37 GMT 2019) -----The flash warnings disappear in the ETC when using the zodiacal light model for the actual position of the target close to the ecliptic.The orbital evolution of binary main-belt comet 288P/300163We request 5 orbits of mid-cycle time, spaced at 50-day intervals between 2018, November and 2019, June, to continue studying the orbital evolution of the unique binary main-belt comet 288P/300163. HST/WFC3 observations from 2016/17 revealed that 288P is unusual due to its combination of nearly equal component size, wide separation, high eccentricity, and sublimation-driven activity. Possible formation scenarios include a collision, rotational break-up or a combination of both. The interrelation of activity and orbital evolution seems probable but is highly model-dependent and unconfirmed. In data from 2017/18, we find indications of a change of the orbital elements during the past year, which has significant consequences for modelling the past and future evolution of the system. We request renewed observations of 288P to investigate if the orbit change was induced by the several months of activity in 2016/17, or if the orbit keeps changing also without activity. In order to link the new data to those from previous arcs, the observations should start as soon as possible when 288P emerges from HST's solar exclusion zone in late October 2018, which is why we request mid-cycle time.The goal of the observations is to repeatedly measure the projected component separation of the binary asteroid 288P in order to derive the orbital elements of the binary system during Cycle 26. Five visits are the minimum requirement to contrain the orbital elements, assuming that the binary and heliocentric orbital planes are parallel.
We propose to observe the 288P system during 5 epochs in ~50-day intervals during the visibility period between 2018 October and 2019 June. The timing of each visit is flexible within +/-1 week. All five orbits will be suited to measure the absolute magnitude of the components and its rotational variability. We expect each component to have V~23, and component separations up to 0.03 arcsec. We will employ a subsampling dither box pattern combined with careful PSF-fitting to measure the sub-pixel component separations.
In each orbit, we will take 8 exposures of ~225s using the 1k subarray of WFC3 and perform a subsampling dither box pattern, obtaining 2 exposures at each dither point.
The orbital visibility for a solar system target near the ecliptic plane is 54 min (Section 6.3 of the HST Primer document). The described strategy provides a total exposure time of 1800s = 30 min, and estimated overheads of 6 min for guide-star acquisition, 2.6 min for the first exposure, a total of 14.7 min for the subsequent 7 exposures, and 1.5 min for the three spacecraft maneuvers required for dithering, which adds up to a total execution time of 54 min per orbit. This dither strategy is identical to the one employed successfully for this target during Cycles 24 and 25, ensuring maximum comparability of the data.
We will use the wide bandpass filter F606W for an optimum trade-off between sensitivity and highest resolution: the bandpass (475 - 700 nm) covers the maximum of the solar spectrum, and is in the wavelength range where the PSF is smallest (FWHM<0.07 arcsec, from the WFC3 Instrument Handbook for Cycle 25), such that we can optimally exploit our subsampling dither strategy. In addition, F606W is the same filter we used to observe 288P in GO 12597, 14790, 14864, 14884, and 15328, enabling a direct comparison of the data sets.
The WFC3 exposure time calculator returns for a solar-spectrum point source at V=22.3 (combined for both components), exposure time of 450 s, F606W filter, and default background values a signal-to-noise-ratio of 105 within a circle of 0.2 arcsec (ETC Request ID: WFC3UVIS.im.1154717). This signal will be sufficient to reliably fit the PSFs.Solar System3falsefalsefalsefalsefalsefalsefalseSUPPORTEDSOLAR SYSTEMNOCOMETCOMET 288P, ASTEROID 300163TYPE=COMET,Q=2.434091859832713,E=0.2011952883437459,I=3.240682641168021,O=83.19068811025544,W=281.2529259614446,T=08-NOV-2016:21:17:35,TTimeScale=TDB,EQUINOX=J2000,EPOCH=29-APR-2014:00:00:00,EpochTimeScale=TDBEARTHWFC3/UVISImagingNoNoF606WWFC3/UVISImagingNoNoF606WWFC3/UVISImagingNoNoF606WWFC3/UVISImagingNoNoF606WWFC3/UVISImagingNoNoF606WPOS-TARGDITHER0.173LINE0.112falsefalse81.785423.884WFC3-UVIS-DITHER-BOX1falseUsing ephemeris for target 15481-01-288Pephemeris data for target 15481-01-288P does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 18.286 to 20.092. ephemeris interval: 19.090 to 21.091The scheduling data was generated by CASM 27.0.CASM was run in Phase II mode./tmp/OPVisit10328454525999880717.xmlThe flash warning disappears when using the zodiacal light model for the actual position of the target close to the ecliptic.1542074321000294.5485533723235(Tic-Visit
:proposal-id 15481
:visit-id "01"
:proposal-version -1
:trans-version "20181130"
:date "15-Apr-2019 11:04: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 142608
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15481
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15481
:visit-id "01"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2674
:al-overhead-at-end 0
:internal-dur-at-end 192
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3142
:pcs-gap 0
)true10Using ephemeris for target 15481-02-288Pephemeris data for target 15481-02-288P does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 18.286 to 20.092. ephemeris interval: 19.090 to 21.091The scheduling data was generated by CASM 27.0.CASM was run in Phase II mode./tmp/OPVisit12208378503554103189.xmlThe flash warning disappears when using the zodiacal light model for the actual position of the target close to the ecliptic.1545448693000295.0(Tic-Visit
:proposal-id 15481
:visit-id "02"
:proposal-version -1
:trans-version "20181130"
:date "15-Apr-2019 11:04: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 142608
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15481
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15481
:visit-id "02"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2674
:al-overhead-at-end 0
:internal-dur-at-end 192
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3142
:pcs-gap 0
)true10Using ephemeris for target 15481-03-288Pephemeris data for target 15481-03-288P does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 18.286 to 20.092. ephemeris interval: 19.090 to 21.091The scheduling data was generated by CASM 27.0.CASM was run in Phase II mode./tmp/OPVisit4346879084882720108.xmlThe flash warning disappears when using the zodiacal light model for the actual position of the target close to the ecliptic.1548435001000290.1897246512027(Tic-Visit
:proposal-id 15481
:visit-id "03"
:proposal-version -1
:trans-version "20181130"
:date "15-Apr-2019 11:04:37.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 142608
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15481
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15481
:visit-id "03"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2674
:al-overhead-at-end 0
:internal-dur-at-end 192
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3142
:pcs-gap 0
)true10Using ephemeris for target 15481-04-288Pephemeris data for target 15481-04-288P does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 18.286 to 20.092. ephemeris interval: 19.090 to 21.091The scheduling data was generated by CASM 27.0.CASM was run in Phase II mode./tmp/OPVisit10439040850492568333.xmlThe flash warning disappears when using the zodiacal light model for the actual position of the target close to the ecliptic.1550305836000289.4202288786277(Tic-Visit
:proposal-id 15481
:visit-id "04"
:proposal-version -1
:trans-version "20181130"
:date "15-Apr-2019 11:04:41.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 142608
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15481
:visit-id "04"
:obset-id "04"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15481
:visit-id "04"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2674
:al-overhead-at-end 0
:internal-dur-at-end 192
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3142
:pcs-gap 0
)true10Using ephemeris for target 15481-05-288Pephemeris data for target 15481-05-288P does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 18.286 to 20.092. ephemeris interval: 19.090 to 21.091The scheduling data was generated by CASM 27.0.CASM was run in Phase II mode./tmp/OPVisit623492700787078957.xmlThe flash warning disappears when using the zodiacal light model for the actual position of the target close to the ecliptic.(Tic-Visit
:proposal-id 15481
:visit-id "05"
:proposal-version -1
:trans-version "20181130"
:date "15-Apr-2019 11:04:17.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 142608
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15481
:visit-id "05"
:obset-id "05"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15481
:visit-id "05"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2674
:al-overhead-at-end 0
:internal-dur-at-end 192
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3142
:pcs-gap 0
)true10