Proposal was erroneously marked "GO" instead of "GO/DD".-1810738916Assigned ID: 1608
----- Attempting Submission 1 (Thu Oct 26 09:04:48 GMT 2017) -----
HST Phase I Proposal 1608 (ISO.apt) successfully submitted.
Receipt: # 1608-1
----- Attempting Submission 2 (Thu Oct 26 09:19:47 GMT 2017) -----Be very careful mixing POS TARG and Center_Pattern = Yes
Be very careful mixing POS TARG and Center_Pattern = Yes
Be very careful mixing POS TARG and Center_Pattern = Yes
Be very careful mixing POS TARG and Center_Pattern = Yesnew pos-targ, visit 05835539049----- Attempting Submission 1 (Fri Oct 27 23:31:47 GMT 2017) -----
----- Attempting Submission 2 (Mon Oct 30 12:40:18 GMT 2017) -----
----- Attempting Submission 3 (Mon Nov 06 20:50:17 GMT 2017) -----
HST Phase II Proposal 15405 (15405.apt) successfully submitted.
Receipt: # 15405-3
----- Attempting Submission 4 (Tue Nov 07 12:56:05 GMT 2017) -----
HST Phase II Proposal 15405 (15405.apt) successfully submitted.
Receipt: # 15405-4
----- Attempting Submission 5 (Tue Nov 07 16:18:01 GMT 2017) -----
----- Attempting Submission 6 (Tue Nov 07 16:26:42 GMT 2017) -----
----- Attempting Submission 7 (Tue Nov 07 21:11:12 GMT 2017) -----
HST Phase II Proposal 15405 (15405.apt) successfully submitted.
Receipt: # 15405-7
----- Attempting Submission 8 (Tue Nov 07 21:36:59 GMT 2017) -----
----- Attempting Submission 9 (Wed Nov 08 12:41:17 GMT 2017) -----
HST Phase II Proposal 15405 (15405.apt) successfully submitted.
Receipt: # 15405-9
----- Attempting Submission 10 (Wed Nov 08 12:59:45 GMT 2017) -----
----- Attempting Submission 11 (Wed Nov 29 15:25:40 GMT 2017) -----
----- Attempting Submission 12 (Fri Dec 15 20:13:19 GMT 2017) -----
Your proposal could not be saved.
Submission aborted.
----- Attempting Submission 13 (Mon Dec 18 17:36:19 GMT 2017) -----The dither pattern is much, much smaller than the POSTARG settings. This should be fine. Not sure why
it's fussing about orbit and visit planner. I ran them and they look fine.Which way home? Finding the origin of our Solar System's first interstellar visitorWe request HST/WFC3/UVIS observations of A/2017 U1, a recently discovered fast moving and fast fading object that appears to originate from outside the Solar System. Rapid follow-up observations from the ground established the object's orbit as hyperbolic and thus ruled out that A/2017 U1 is a comet or asteroid. The proposed observations are critical to (a) determine the object's rotation period in order to allow observations to be performed at maximal brightness, and (b) obtain precise astrometry along an extended arc length in order to identify the region from which this object originated.
A/2017 U1 is the first known interloper from outside the Solar System, and the observations proposed here play a pivotal role in determining its origin.The proposed observation consists of two components that serve tightly related purposes: 1) Extend the astrometric arc in order to permit a refined orbit estimation that may allow us to uncover where the target originated. 2) Obtain critical light curve observations as the object is fading to provide accurate predictions of the rotational phase for our ongoing follow-up observations.
To achieve the first goal, we split our observation into three visits, distributed evenly over a 40-day period in order to maximize the observed arc of the interloper's orbit. The beginning of this period, and hence the time of the first visit, is set by the requirement to align HST's astrometric observations with those performed with groundbased facilities, which results in a date of November 22, 2017 (or within a day thereof) for the first visit. The end of the 40-day period, and hence the time of the third visit, is defined by the date at which our target is predicted to have faded to V=27.5 which we consider the limiting magnitude for a credible detection with HST in a single orbit. We expect this to occur on January 01, 2018, but stress that adjustments in our photometric model may alter this prediction by a few days. The second visit should be scheduled near the midpoint between the first and the third visit in order to provide the best possible constraints on the target's highly eccentric orbit. Again, some flexibility is required to allow adjustment as the result of improvements in our model predictions.
To achieve the second goal, we allocate three orbits to the first visit, and one orbit each to the subsequent second and third visit. The longer, first visit aims to sample the target's light curve at high precision and over a sufficiently long time to tightly constrain both amplitude and period, both of which are crucial parameters of the photometric model that underlies the predictions driving the timing of visits two and three.
All observations will be performed with WFC3/UVIS and the F350LP filter in order to maximize system throughput. Since ours is a moving target, no dithering is required. We do, however, split each orbit into 5 subexposures using CR-SPLIT in order to allow efficient removal of cosmic rays and limit the track length of GAIA reference stars in the field that form the basis of our astrometric solution. Since our target is located at high Galactic latitude, the surface density of reference stars is low; we therefore request additional flexibility to allow scheduling of all visits (within the aforementioned windows) such that the number of GAIA stars is maximized.Solar System0SUPPORTEDSOLAR SYSTEMASTEROIDInterstellar ObjectTYPE=COMET,Q=0.2544189102683901,E=1.197091100469663,I=122.600523808621,O=24.60311659652012,W=241.5361324795846,T=09-SEP-2017:11:19:55,TTimeScale=TDB,EQUINOX=J2000,EPOCH=27-OCT-2017:00:00:00,EpochTimeScale=TDBEARTHSOLAR SYSTEMorbital elements update from JPL on Nov. 29ASTEROIDInterstellar ObjectTYPE=COMET,Q=0.2553352156734523,E=1.1994907679102,I=122.6864296097109,O=24.59924632942247,W=241.7015187109427,T=09-SEP-2017:11:46:05,TTimeScale=TDB,EQUINOX=J2000,EPOCH=31-OCT-2017:00:00:00,EpochTimeScale=TDBEARTHSOLAR SYSTEMASTEROIDInterstellar Asteroid OUMUAMUATYPE=COMET,Q=0.2558123336343649,E=1.200914723821507,I=122.7325277932375,O=24.59699783461255,W=241.7946554840634,T=09-SEP-2017:12:12:09,TTimeScale=TDB,EQUINOX=J2000,EPOCH=01-JAN-2018:00:00:00,EpochTimeScale=TDBEARTHWFC3/UVISImagingNoNoF350LPCELESTIALOTHER.030This is a small fractional pixel dither for nearly non-redundant pixels between frames on the target.LINEfalsetrue50LINE1falseUsing ephemeris for target 15405-01-A-2017-U1ephemeris data for target 15405-01-A-2017-U1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 17.213 to 19.091. ephemeris interval: 17.304 to 19.305Timing link suitability includes constraints ([02 After 01 by 0.1 to 0.1 days] [03 After 01 by 0.3 to 0.3 days])The scheduling data was generated by CASM 25.2.CASM was run in Phase II mode.This visit is intended to be scheduled as soon as possible without being a disruptive turn-around.
Otherwise the timing is not critical but candidate times for scheduling need to be checked for stellar
contamination and for having sufficient numbers of Gaia reference stars. This visit is the timing anchor
for visits 2 and 3.151123376200051.984233118362(Tic-Visit
:proposal-id 15405
:visit-id "01"
:proposal-version -1
:trans-version "20170613"
:date "07-Nov-2017 07:50:32.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 1443744
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15405
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15405
:visit-id "01"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2721
:al-overhead-at-end 0
:internal-dur-at-end 668
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)false10Using ephemeris for target 15405-02-A-2017-U1ephemeris data for target 15405-02-A-2017-U1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 17.213 to 19.091. ephemeris interval: 17.304 to 19.305Timing link suitability includes constraints ([02 After 01 by 0.1 to 0.1 days])The scheduling data was generated by CASM 25.2.CASM was run in Phase II mode.This visit should be close in time to visit 1. The timing applied here is an initial guess and may need to be modified slightly
as more lightcurve information becomes available. This initial request is for this visit to be consecutive to visit 1. However,
it could also be consecutive with visit 3 if that works better.151123948400052.0(Tic-Visit
:proposal-id 15405
:visit-id "02"
:proposal-version -1
:trans-version "20170613"
:date "07-Nov-2017 07:50: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 1443744
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15405
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15405
:visit-id "02"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2721
:al-overhead-at-end 0
:internal-dur-at-end 668
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)false10Using ephemeris for target 15405-03-A-2017-U1ephemeris data for target 15405-03-A-2017-U1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 17.213 to 19.091. ephemeris interval: 17.304 to 19.305Timing link suitability includes constraints ([03 After 01 by 0.3 to 0.3 days])The scheduling data was generated by CASM 25.2.CASM was run in Phase II mode.This visit should be close in time to visit 1. The timing applied here is an initial guess and may need to be modified slightly
as more lightcurve information becomes available. This initial request is based on a rotational period of 4 hours and is
intended to run 5 orbits after visit 1.151135393200087.0(Tic-Visit
:proposal-id 15405
:visit-id "03"
:proposal-version -1
:trans-version "20170613"
:date "07-Nov-2017 07:50:34.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 1443744
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15405
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15405
:visit-id "03"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2721
:al-overhead-at-end 0
:internal-dur-at-end 668
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)false10Using ephemeris for target 15405-04-A-2017-U1ephemeris data for target 15405-04-A-2017-U1 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 17.213 to 19.091. ephemeris interval: 17.304 to 19.305The scheduling data was generated by CASM 25.2.CASM was run in Phase II mode.This timing for this visit is roughly half way between visit 1 and 5. The only thing critical about the timing is to
get this data for rotational phase refinements to support scheduling the last visit. There is more latitude in
the timing than indicated if there is a problem with this request.151304169900069.63179906051869(Tic-Visit
:proposal-id 15405
:visit-id "04"
:proposal-version -1
:trans-version "20170613"
:date "07-Nov-2017 07:50:35.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 1443744
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15405
:visit-id "04"
:obset-id "04"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15405
:visit-id "04"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2721
:al-overhead-at-end 0
:internal-dur-at-end 668
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)false10Using ephemeris for target 15405-05-OUMUAMUAephemeris data for target 15405-05-OUMUAMUA does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 17.294 to 19.091. ephemeris interval: 17.334 to 19.335The scheduling data was generated by CASM 25.2.CASM was run in Phase II mode.This timing for this visit is set when we anticipate the target will reach V=27.5 at maximum light.
The final scheduling for this will depend on updates provided by the other visits.(Tic-Visit
:proposal-id 15405
:visit-id "05"
:proposal-version -1
:trans-version "20171009"
:date "15-Dec-2017 12:00:04.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 1443744
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15405
:visit-id "05"
:obset-id "05"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15405
:visit-id "05"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2721
:al-overhead-at-end 0
:internal-dur-at-end 668
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)false10