This request is to obtain data during 2020 March-September and the only way to secure this time is through a mid-cycle request.
Revised the Before timing window.1268558463Assigned ID: 1226
----- Attempting Submission 1 (Fri Jan 17 22:41:28 GMT 2020) -----
HST Phase I Proposal 1226 (2I_midcycle.apt) successfully submitted.
Receipt: # 1226-1
----- Attempting Submission 2 (Fri Jan 17 22:46:31 GMT 2020) -----
----- Attempting Submission 3 (Sat Jan 18 04:41:15 GMT 2020) -----The number of orbits used exceeds the number allocated
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 = 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 = 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 = Yes
Be very careful mixing POS TARG and Center_Pattern = YesRevised proposal following HOPR request approval to repeat visit 5. Please note that Marc Buie (buie@boulder.swri.edu) is the primary contact for scheduling
and implementation issues. The existing orbit in the proposal is good enough to support this visit retry.-1253409212----- Attempting Submission 1 (Thu Mar 19 16:59:57 GMT 2020) -----
----- Attempting Submission 2 (Thu Sep 03 14:25:21 GMT 2020) -----The warnings are for use of POSTARG combined with a line dither.
They are all set to 0 for this initial submission. This use of POSTARG has been
used successfully for similar Arrokoth, Oumuamua, and Borisov observations.
Orbit allocation shows 10 but we have added a new visit (11) based on the approval of our HOPR request.Tracking the Outbound Motion of Interstellar Comet 2I/Borisov.We are requesting 10 orbits to (1) perform high precision astrometry on
the outbound orbit to model the non-gravitational acceleration and model the
activity drivers; (2) confirm the rotation period detected in the previous HST
program 16043, but with better contrast to get the nucleus axis ratio; (3) use the
jets detected in the HST data to constrain the rotation pole; and (4) to observe
the Earth's orbit plane crossing to analyze the activity profile of the large dust
grains. For these observations we will use WFC3/UVIS imaging with F350LP
passband. This request is to obtain data during 2020 March-September and the only way to
secure this time is through a mid-cycle request.We want these to be approximately monthly, time constraint can be quite loose (~1-2 week window per visit).
Thus one orbit in April, May, June, July, early Sep and late Sep, as close to 9/30 as possible or early October.
For the August Visit - we want 4 orbits within +/- 5 days of August 1, the orbit plane crossing date. Randomly spread is fine in that period.
All data are full UVIS field images to ensure sufficient astrometric reference stars to get precise positional measurements on the comet.Each of the team members has expertise that is relevant and necessary to this proposal. A brief description follows.
Karen Meech - expert on interstellar object observations and coordinating international teams. Lead much of the work for the 1I observing campaign. Expert on comet observations and interpretation, including rotation analysis.
Marc Buie - expert user of HST for astrometry and photometry of solar system objects. Lead for the Phase 2 development and assisting with scheduling.
Davide Farnocchia - Expert in non-gravitational analysis, will combine with astrometry from ground based assets.
Marco Micheli / David Tholen - Are the world experts in astrometry and orbit determinationastrometry from ground based assets and assessment of astrometric biases from the combined HST/ground dataset
Olivier Hainaut - Assist with interpretation of the rotation light curve and shape analysis. Provide additional ground-bsaed data from our VLT 2I program.
Hermann Boehnhardt - Laplace filtering, coma removal from HST images, nucleus size, rotation pole analysis
Coryn Bailer-Jones - Expert in trajectory analysis and application of GAIA for astrometry.
Jan Kleyna - Comet expert and expertise with innovative programming for data reduction and rotation and rotation pole analysis. He will be a key team member for the analysis of the data.
Jacqueline Keane - expert in interpreting comet data, familiar with HST. She will help collect the associated ground based observations and process the data so we can develop the best estimate of when to initiate the observations.Solar System3falsefalsefalsefalsefalsefalsefalseSUPPORTEDSOLAR SYSTEMCOMETInterstellar ObjectTYPE=COMET,Q=2.006624008587265,E=3.356191268153205,I=44.05262620283894
,O=308.1489154698829,W=209.1246056235187,T=08-DEC-2019:13:04:38,TTimeScale=TDB,EQUINOX=J2000,EPOCH=31-JUL-2020:00:00:00,EpochTimeScale=TDB,R0=2.808
,DT=0.
,A1=7.312064170837E-8,A2=-3.252092599869E-8,A3=0.
,ALN=0.1112620426,NM=2.15,NN=5.093,NK=4.6142,AMRAT=0.EARTHWFC3/UVISImagingNoNoF350LPCELESTIALOTHER0.03LINEfalsetrue50LINE1falseUsing ephemeris for target 16088-01-I2-BOROSOVephemeris data for target 16088-01-I2-BOROSOV does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 19.213 to 21.089. ephemeris interval: 20.060 to 22.060The scheduling data was generated by CASM 28.0.CASM was run in Phase II mode.The five long, dithered exposures are intended to fill a single visibility window to get the relative timing we need. This is a stand-alone visit with a window provided to give a time constraint that is loose but holds it in roughly the right timeframe for the overall temporal sequence needed for the astrometry. Successful observations require a minimum number of suitable Gaia DR2 sources in the full field of UVIS. As the observations are scheduled, the proposal team needs to check potential windows for suitable guide stars and provide guidance on which windows will work best. If the fields are sparse enough, we may need to provide adjusted POSTARG values to ensure there are enough stars.15861326560005.879282594535994(Tic-Visit
:proposal-id 16088
:visit-id "01"
:proposal-version -1
:trans-version "20191203"
:date "19-Mar-2020 10:46: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 1443744
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 16088
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 16088
:visit-id "01"
:orbit-number 1
:pcs-time 393
: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 3142
:pcs-gap 0
)true10Using ephemeris for target 16088-02-I2-BOROSOVephemeris data for target 16088-02-I2-BOROSOV does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 19.213 to 21.089. ephemeris interval: 20.060 to 22.060The scheduling data was generated by CASM 28.0.CASM was run in Phase II mode.The five long, dithered exposures are intended to fill a single visibility window to get the relative timing we need. This is a stand-alone visit with a window provided to give a time constraint that is loose but holds it in roughly the right timeframe for the overall temporal sequence needed for the astrometry. Successful observations require a minimum number of suitable Gaia DR2 sources in the full field of UVIS. As the observations are scheduled, the proposal team needs to check potential windows for suitable guide stars and provide guidance on which windows will work best. If the fields are sparse enough, we may need to provide adjusted POSTARG values to ensure there are enough stars.158874546100051.0(Tic-Visit
:proposal-id 16088
:visit-id "02"
:proposal-version -1
:trans-version "20191203"
:date "19-Mar-2020 10:46:13.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 16088
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 16088
:visit-id "02"
:orbit-number 1
:pcs-time 393
: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 3142
:pcs-gap 0
)true10Using ephemeris for target 16088-03-I2-BOROSOVephemeris data for target 16088-03-I2-BOROSOV does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 19.213 to 21.089. ephemeris interval: 20.060 to 22.060The scheduling data was generated by CASM 28.0.CASM was run in Phase II mode.The five long, dithered exposures are intended to fill a single visibility window to get the relative timing we need. This is a stand-alone visit with a window provided to give a time constraint that is loose but holds it in roughly the right timeframe for the overall temporal sequence needed for the astrometry. Successful observations require a minimum number of suitable Gaia DR2 sources in the full field of UVIS. As the observations are scheduled, the proposal team needs to check potential windows for suitable guide stars and provide guidance on which windows will work best. If the fields are sparse enough, we may need to provide adjusted POSTARG values to ensure there are enough stars.159070984300067.89490576178079(Tic-Visit
:proposal-id 16088
:visit-id "03"
:proposal-version -1
:trans-version "20191203"
:date "19-Mar-2020 10:46: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 1443744
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 16088
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 16088
:visit-id "03"
:orbit-number 1
:pcs-time 393
: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 3142
:pcs-gap 0
)true10Using ephemeris for target 16088-04-I2-BOROSOVephemeris data for target 16088-04-I2-BOROSOV does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 19.213 to 21.089. ephemeris interval: 20.060 to 22.060Timing link suitability includes constraints ([05 After 04])The scheduling data was generated by CASM 28.0.CASM was run in Phase II mode.The five long, dithered exposures are intended to fill a single visibility window to get the relative timing we need. This is a stand-alone visit with a window provided to give a time constraint that is loose but holds it in roughly the right timeframe for the overall temporal sequence needed for the astrometry. Successful observations require a minimum number of suitable Gaia DR2 sources in the full field of UVIS. As the observations are scheduled, the proposal team needs to check potential windows for suitable guide stars and provide guidance on which windows will work best. If the fields are sparse enough, we may need to provide adjusted POSTARG values to ensure there are enough stars.1594076053000101.26692946980029(Tic-Visit
:proposal-id 16088
:visit-id "04"
:proposal-version -1
:trans-version "20191203"
:date "19-Mar-2020 10:46:15.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 16088
:visit-id "04"
:obset-id "04"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 16088
:visit-id "04"
:orbit-number 1
:pcs-time 393
: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 3142
:pcs-gap 0
)true10Using ephemeris for target 16088-05-I2-BOROSOVephemeris data for target 16088-05-I2-BOROSOV does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 19.213 to 21.089. ephemeris interval: 20.060 to 22.060Timing link suitability includes constraints ([05 After 04])The scheduling data was generated by CASM 28.0.CASM was run in Phase II mode.The five long, dithered exposures are intended to fill a single visibility window to get the relative timing we need. This is a stand-alone visit with a window provided to give a time constraint that is loose but holds it in roughly the right timeframe for the overall temporal sequence needed for the astrometry. Successful observations require a minimum number of suitable Gaia DR2 sources in the full field of UVIS. As the observations are scheduled, the proposal team needs to check potential windows for suitable guide stars and provide guidance on which windows will work best. If the fields are sparse enough, we may need to provide adjusted POSTARG values to ensure there are enough stars.1598640676000118.36124956938511(Tic-Visit
:proposal-id 16088
:visit-id "05"
:proposal-version -1
:trans-version "20191203"
:date "19-Mar-2020 10:46:15.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 16088
:visit-id "05"
:obset-id "05"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 16088
:visit-id "05"
:orbit-number 1
:pcs-time 393
: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 3142
:pcs-gap 0
)false10Using ephemeris for target 16088-06-I2-BOROSOVephemeris data for target 16088-06-I2-BOROSOV does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 19.213 to 21.089. ephemeris interval: 20.060 to 22.060The scheduling data was generated by CASM 28.0.CASM was run in Phase II mode.The five long, dithered exposures are intended to fill a single visibility window to get the relative timing we need. This is a stand-alone visit with a window provided to give a time constraint that is loose but holds it in roughly the right timeframe for the overall temporal sequence needed for the astrometry. Successful observations require a minimum number of suitable Gaia DR2 sources in the full field of UVIS. As the observations are scheduled, the proposal team needs to check potential windows for suitable guide stars and provide guidance on which windows will work best. If the fields are sparse enough, we may need to provide adjusted POSTARG values to ensure there are enough stars.(Tic-Visit
:proposal-id 16088
:visit-id "06"
:proposal-version -1
:trans-version "20191203"
:date "19-Mar-2020 10:46: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 1443744
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 16088
:visit-id "06"
:obset-id "06"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 16088
:visit-id "06"
:orbit-number 1
:pcs-time 393
: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 3142
:pcs-gap 0
)false10Using ephemeris for target 16088-07-I2-BOROSOVephemeris data for target 16088-07-I2-BOROSOV does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 19.213 to 21.089. ephemeris interval: 20.060 to 22.060Timing link suitability includes constraints ([08 After 07 by 0.1 to 0.1 days] [09 After 07 by 2.5 to 3.5 days] [10 After 07 by 4.5 to 5.5 days])The scheduling data was generated by CASM 28.0.CASM was run in Phase II mode.The five long, dithered exposures are intended to fill a single visibility window to get the relative timing we need. This visit is timed to be close to the time when our viewpoint is in the orbit plane of the comet to study the dust surrounding the comet but is also used for astrometry. Successful observations require a minimum number of suitable Gaia DR2 sources in the full field of UVIS. As the observations are scheduled, the proposal team needs to check potential windows for suitable guide stars and provide guidance on which windows will work best. If the fields are sparse enough, we may need to provide adjusted POSTARG values to ensure there are enough stars.1596193803000118.0(Tic-Visit
:proposal-id 16088
:visit-id "07"
:proposal-version -1
:trans-version "20191203"
:date "19-Mar-2020 10:46: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 1443744
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 16088
:visit-id "07"
:obset-id "07"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 16088
:visit-id "07"
:orbit-number 1
:pcs-time 393
: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 3142
:pcs-gap 0
)false10Using ephemeris for target 16088-08-I2-BOROSOVephemeris data for target 16088-08-I2-BOROSOV does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 19.213 to 21.089. ephemeris interval: 20.060 to 22.060Timing link suitability includes constraints ([08 After 07 by 0.1 to 0.1 days])The scheduling data was generated by CASM 28.0.CASM was run in Phase II mode.The five long, dithered exposures are intended to fill a single visibility window to get the relative timing we need. This visit is timed to be close to the time when our viewpoint is in the orbit plane of the comet to study the dust surrounding the comet but is also used for astrometry. It has a relative timing contraint binding it to the previous visit. Ideally, visits 7 and 8 should be done back to back and this is how the timing constraint is written. Successful observations require a minimum number of suitable Gaia DR2 sources in the full field of UVIS. As the observations are scheduled, the proposal team needs to check potential windows for suitable guide stars and provide guidance on which windows will work best. If the fields are sparse enough, we may need to provide adjusted POSTARG values to ensure there are enough stars.1596199521000118.0(Tic-Visit
:proposal-id 16088
:visit-id "08"
:proposal-version -1
:trans-version "20191203"
:date "19-Mar-2020 10:46: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 1443744
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 16088
:visit-id "08"
:obset-id "08"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 16088
:visit-id "08"
:orbit-number 1
:pcs-time 393
: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 3142
:pcs-gap 0
)false10Using ephemeris for target 16088-09-I2-BOROSOVephemeris data for target 16088-09-I2-BOROSOV does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 19.213 to 21.089. ephemeris interval: 20.060 to 22.060Timing link suitability includes constraints ([09 After 07 by 2.5 to 3.5 days])The scheduling data was generated by CASM 28.0.CASM was run in Phase II mode.The five long, dithered exposures are intended to fill a single visibility window to get the relative timing we need. This visit is in support of the visit 7 and 8 data which are timed to be close to the time when our viewpoint is in the orbit plane of the comet to study the dust surrounding the comet but is also used for astrometry. Visits 9 and 10 provide rotational context for visits 7 and 8. Successful observations require a minimum number of suitable Gaia DR2 sources in the full field of UVIS. As the observations are scheduled, the proposal team needs to check potential windows for suitable guide stars and provide guidance on which windows will work best. If the fields are sparse enough, we may need to provide adjusted POSTARG values to ensure there are enough stars.1596456803000113.19075679045147(Tic-Visit
:proposal-id 16088
:visit-id "09"
:proposal-version -1
:trans-version "20191203"
:date "19-Mar-2020 10:46:18.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 16088
:visit-id "09"
:obset-id "09"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 16088
:visit-id "09"
:orbit-number 1
:pcs-time 393
: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 3142
:pcs-gap 0
)true10Using ephemeris for target 16088-10-I2-BOROSOVephemeris data for target 16088-10-I2-BOROSOV does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 19.213 to 21.089. ephemeris interval: 20.060 to 22.060Timing link suitability includes constraints ([10 After 07 by 4.5 to 5.5 days])The scheduling data was generated by CASM 28.0.CASM was run in Phase II mode.The five long, dithered exposures are intended to fill a single visibility window to get the relative timing we need. This visit is in support of the visit 7 and 8 data which are timed to be close to the time when our viewpoint is in the orbit plane of the comet to study the dust surrounding the comet but is also used for astrometry. Visits 9 and 10 provide rotational context for visits 7 and 8. Successful observations require a minimum number of suitable Gaia DR2 sources in the full field of UVIS. As the observations are scheduled, the proposal team needs to check potential windows for suitable guide stars and provide guidance on which windows will work best. If the fields are sparse enough, we may need to provide adjusted POSTARG values to ensure there are enough stars.1596634037000114.21026060432303(Tic-Visit
:proposal-id 16088
:visit-id "10"
:proposal-version -1
:trans-version "20191203"
:date "19-Mar-2020 10:46:18.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 16088
:visit-id "10"
:obset-id "10"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 16088
:visit-id "10"
:orbit-number 1
:pcs-time 393
: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 3142
:pcs-gap 0
)true10The scheduling data was generated by CASM 28.2.CASM was run in Phase II mode./tmp/OPVisit16040720614665647956.xmlThe five long, dithered exposures are intended to fill a single visibility window to get the relative timing we need. This is a stand-alone visit with a window provided to give a time constraint that is loose but holds it in roughly the right timeframe for the overall temporal sequence needed for the astrometry. Successful observations require a minimum number of suitable Gaia DR2 sources in the full field of UVIS. As the observations are scheduled, the proposal team needs to check potential windows for suitable guide stars and provide guidance on which windows will work best. If the fields are sparse enough, we may need to provide adjusted POSTARG values to ensure there are enough stars.
This is a repeat of visit 5 due to a guide star failure. The best use of this repeat visit would be to schedule this immediately adjacent to visit 6 which is already scheduled. If that is not possible, the next best thing is to schedule after visit 5 before the object is lost due to the solar exclusion zone. The window is set to all of the remaining time for scheduling in case even our second choice isn't possible.(Tic-Visit
:proposal-id 16088
:visit-id "11"
:proposal-version -1
:trans-version "20200619"
:date "03-Sep-2020 08:23: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 1443744
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 16088
:visit-id "11"
:obset-id "11"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 16088
:visit-id "11"
:orbit-number 1
:pcs-time 393
: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 3142
:pcs-gap 0
)true10