We are requesting 10 orbits of Mid-cycle time to observe comet 41P/Tuttle-Giacobini-Kresak530669421Assigned ID: 1573
----- Attempting Submission 1 (Sat Sep 30 22:43:41 GMT 2017) -----Thank you for working to schedule these observations.
If there are any questions, feel free to contact me.-1777383954----- Attempting Submission 1 (Tue Nov 28 04:17:46 GMT 2017) -----The Nucleus of comet 41P/Tuttle-Giacobini-KresakComet 41P/Tuttle-Giacobini-Kresak is undergoing an unprecedented spindown of its nucleus, with its rotation period more than doubling from 20 to 42+ hours in a two month period. No other comet has been observed to exhibit this magnitude of change in its dynamic state, suggesting that 41P has a distinct alignment of its activity that generates highly efficient torques on the nucleus. Its rapid evolution presents us with a unique opportunity for testing models of cometary dynamics. Unfortunately, little information currently exists about the nucleus itself, which limits our ability to quantify the forces involved. We are requesting 10 HST orbits, spanning a 7-day window, to observe the comet's lightcurve. We will use this lightcurve to characterize the nucleus' size and shape and determine its current rotation period. We will use the F350LP filter to maximize the S/N of our measurements, and we have developed an observation sampling strategy that optimizes the 10 orbits to provide an good coverage of lightcurves with any period between 2 and 7 days. Results derived from these observations will provide the knowledge needed for detailed analyses of the comet's torques and how they respond to changing production rates and illumination conditions.We are attempting to define a comet nucleus lightcurve, so ideally we would like to spread our 10 orbits out at roughly equal intervals over the observing window.
For the following we assume the window starts 11-Dec-2017:00:00:00 and ends 14-Dec-2017:11:39:00.
(The start date is assumed to be the start of the upcoming SMS, and the end date, given by visit planner, is presumably defined by the time at which the comet enters the solar exclusion zone. If these are not the correct limits, then our window size and average interval may change a little.)
The window is thus 3.48 days (83.5 hrs) long, and with 9 intervals between 10 visits, the average interval is ~9 hrs.
Thus we would like to sample the lightcurve on average every 9 hours. In the timing requirements for the visits, we specify intervals of 6 to 12 hrs, and are willing to occasionally relax those limits even further to facilitate scheduling, as long as we obtain suitable coverage of the observing window.
Each visit is identical and will consist of 7 images obtained with the WFC3/UVIS instrument in the 1kx1k subframe mode.
The 7-image sequence repeated at each visit:
F350LP 160 sec
F475W 400 sec
F625W 340 sec
(dither)
F350LP 160 sec
F475W 400 sec
F625W 340 sec
(dither)
F350LP 160 secSolar System3falsefalsefalsefalsefalsefalseSUPPORTEDSOLAR SYSTEMCOMETComet 41P/Tuttle-Giacobini-KresakTYPE=COMET,Q=1.045042734323105,E=0.6612507057941893,I=9.229131575306448,O=141.0662859883997,W=62.15858593106646,T=12-APR-2017:18:03:14,TTimeScale=TDB,EQUINOX=J2000,EPOCH=01-APR-2017:00:00:00,EpochTimeScale=TDB,A1=1.745203733444E-8,A2=4.275330603123E-9,A3=1.473430991173E-9EARTHWFC3/UVISImagingNoNoF350LPWFC3/UVISImagingNoNoF475WWFC3/UVISImagingNoNoF625WPOS-TARGDITHER0.145LINEfalsefalse246.84WFC3-UVIS-DITHER-LINE2falseUsing ephemeris for target 15421-01-41Pephemeris data for target 15421-01-41P does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 17.195 to 19.091. ephemeris interval: 17.304 to 19.305Timing link suitability includes constraints ([02 After 01 by 0.2 to 0.5 days])The scheduling data was generated by CASM 25.2.CASM was run in Phase II mode.Timing Requirements:
To clarify, we are trying to define a lightcurve, so we would like to space our 10 orbits at roughly equal intervals through the observing window, if possible. Assuming the window start time is 11-Dec-2017:00:00:00 and the end time is 14-Dec-2017:11:39:00 (according to the visit planner - presumably defined by the time at which the comet enters the solar exclusion zone) then the intervals would be an average of ~9 hrs. In the requirements below, we specify intervals of 6 to 12 hrs (and are willing to relax that even further to facilitate scheduling) but would like to span the majority of the observing window.151296655000074.5853720594873(Tic-Visit
:proposal-id 15421
:visit-id "01"
:proposal-version -1
:trans-version "20171009"
:date "27-Nov-2017 21:31: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 121872
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15421
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15421
:visit-id "01"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2858
:al-overhead-at-end 0
:internal-dur-at-end 170
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)false10Using ephemeris for target 15421-02-41Pephemeris data for target 15421-02-41P does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 17.195 to 19.091. ephemeris interval: 17.304 to 19.305Timing link suitability includes constraints ([02 After 01 by 0.2 to 0.5 days] [03 After 02 by 0.2 to 0.5 days])The scheduling data was generated by CASM 25.2.CASM was run in Phase II mode.Timing Requirements:
To clarify, we are trying to define a lightcurve, so we would like to space our 10 orbits at roughly equal intervals through the observing window, if possible. Assuming the window start time is 11-Dec-2017:00:00:00 and the end time is 14-Dec-2017:11:39:00 (according to the visit planner - presumably defined by the time at which the comet enters the solar exclusion zone) then the intervals would be an average of ~9 hrs. In the requirements below, we specify intervals of 6 to 12 hrs (and are willing to relax that even further to facilitate scheduling) but would like to span the majority of the observing window.151299692800074.69999999999999(Tic-Visit
:proposal-id 15421
:visit-id "02"
:proposal-version -1
:trans-version "20171009"
:date "27-Nov-2017 21:58:19.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 121872
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15421
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15421
:visit-id "02"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2858
:al-overhead-at-end 0
:internal-dur-at-end 170
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)false10Using ephemeris for target 15421-03-41Pephemeris data for target 15421-03-41P does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 17.195 to 19.091. ephemeris interval: 17.304 to 19.305Timing link suitability includes constraints ([03 After 02 by 0.2 to 0.5 days] [04 After 03 by 0.2 to 0.5 days])The scheduling data was generated by CASM 25.2.CASM was run in Phase II mode.Timing Requirements:
To clarify, we are trying to define a lightcurve, so we would like to space our 10 orbits at roughly equal intervals through the observing window, if possible. Assuming the window start time is 11-Dec-2017:00:00:00 and the end time is 14-Dec-2017:11:39:00 (according to the visit planner - presumably defined by the time at which the comet enters the solar exclusion zone) then the intervals would be an average of ~9 hrs. In the requirements below, we specify intervals of 6 to 12 hrs (and are willing to relax that even further to facilitate scheduling) but would like to span the majority of the observing window.151302376700075.80000000000001(Tic-Visit
:proposal-id 15421
:visit-id "03"
:proposal-version -1
:trans-version "20171009"
:date "27-Nov-2017 21:58:20.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 121872
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15421
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15421
:visit-id "03"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2858
:al-overhead-at-end 0
:internal-dur-at-end 170
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)false10Using ephemeris for target 15421-04-41Pephemeris data for target 15421-04-41P does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 17.195 to 19.091. ephemeris interval: 17.304 to 19.305Timing link suitability includes constraints ([04 After 03 by 0.2 to 0.5 days] [05 After 04 by 0.2 to 0.5 days])The scheduling data was generated by CASM 25.2.CASM was run in Phase II mode.Timing Requirements:
To clarify, we are trying to define a lightcurve, so we would like to space our 10 orbits at roughly equal intervals through the observing window, if possible. Assuming the window start time is 11-Dec-2017:00:00:00 and the end time is 14-Dec-2017:11:39:00 (according to the visit planner - presumably defined by the time at which the comet enters the solar exclusion zone) then the intervals would be an average of ~9 hrs. In the requirements below, we specify intervals of 6 to 12 hrs (and are willing to relax that even further to facilitate scheduling) but would like to span the majority of the observing window.151304665400070.4(Tic-Visit
:proposal-id 15421
:visit-id "04"
:proposal-version -1
:trans-version "20171009"
:date "27-Nov-2017 21:58:21.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 121872
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15421
:visit-id "04"
:obset-id "04"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15421
:visit-id "04"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2858
:al-overhead-at-end 0
:internal-dur-at-end 170
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)false10Using ephemeris for target 15421-05-41Pephemeris data for target 15421-05-41P does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 17.195 to 19.091. ephemeris interval: 17.304 to 19.305Timing link suitability includes constraints ([05 After 04 by 0.2 to 0.5 days] [06 After 05 by 0.2 to 0.5 days])The scheduling data was generated by CASM 25.2.CASM was run in Phase II mode.Timing Requirements:
To clarify, we are trying to define a lightcurve, so we would like to space our 10 orbits at roughly equal intervals through the observing window, if possible. Assuming the window start time is 11-Dec-2017:00:00:00 and the end time is 14-Dec-2017:11:39:00 (according to the visit planner - presumably defined by the time at which the comet enters the solar exclusion zone) then the intervals would be an average of ~9 hrs. In the requirements below, we specify intervals of 6 to 12 hrs (and are willing to relax that even further to facilitate scheduling) but would like to span the majority of the observing window.151306974300070.0(Tic-Visit
:proposal-id 15421
:visit-id "05"
:proposal-version -1
:trans-version "20171009"
:date "27-Nov-2017 21:58:23.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 121872
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15421
:visit-id "05"
:obset-id "05"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15421
:visit-id "05"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2858
:al-overhead-at-end 0
:internal-dur-at-end 170
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)false10Using ephemeris for target 15421-06-41Pephemeris data for target 15421-06-41P does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 17.195 to 19.091. ephemeris interval: 17.304 to 19.305Timing link suitability includes constraints ([06 After 05 by 0.2 to 0.5 days] [07 After 06 by 0.2 to 0.5 days])The scheduling data was generated by CASM 25.2.CASM was run in Phase II mode.Timing Requirements:
To clarify, we are trying to define a lightcurve, so we would like to space our 10 orbits at roughly equal intervals through the observing window, if possible. Assuming the window start time is 11-Dec-2017:00:00:00 and the end time is 14-Dec-2017:11:39:00 (according to the visit planner - presumably defined by the time at which the comet enters the solar exclusion zone) then the intervals would be an average of ~9 hrs. In the requirements below, we specify intervals of 6 to 12 hrs (and are willing to relax that even further to facilitate scheduling) but would like to span the majority of the observing window.151309815300071.0(Tic-Visit
:proposal-id 15421
:visit-id "06"
:proposal-version -1
:trans-version "20171009"
:date "27-Nov-2017 21:58:25.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 121872
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15421
:visit-id "06"
:obset-id "06"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15421
:visit-id "06"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2858
:al-overhead-at-end 0
:internal-dur-at-end 170
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)false10Using ephemeris for target 15421-07-41Pephemeris data for target 15421-07-41P does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 17.195 to 19.091. ephemeris interval: 17.304 to 19.305Timing link suitability includes constraints ([07 After 06 by 0.2 to 0.5 days] [08 After 07 by 0.2 to 0.5 days])The scheduling data was generated by CASM 25.2.CASM was run in Phase II mode.Timing Requirements:
To clarify, we are trying to define a lightcurve, so we would like to space our 10 orbits at roughly equal intervals through the observing window, if possible. Assuming the window start time is 11-Dec-2017:00:00:00 and the end time is 14-Dec-2017:11:39:00 (according to the visit planner - presumably defined by the time at which the comet enters the solar exclusion zone) then the intervals would be an average of ~9 hrs. In the requirements below, we specify intervals of 6 to 12 hrs (and are willing to relax that even further to facilitate scheduling) but would like to span the majority of the observing window.151313248600074.4416226894075(Tic-Visit
:proposal-id 15421
:visit-id "07"
:proposal-version -1
:trans-version "20171009"
:date "27-Nov-2017 21:58:25.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 121872
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15421
:visit-id "07"
:obset-id "07"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15421
:visit-id "07"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2858
:al-overhead-at-end 0
:internal-dur-at-end 170
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)false10Using ephemeris for target 15421-08-41Pephemeris data for target 15421-08-41P does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 17.195 to 19.091. ephemeris interval: 17.304 to 19.305Timing link suitability includes constraints ([08 After 07 by 0.2 to 0.5 days] [09 After 08 by 0.2 to 0.5 days])The scheduling data was generated by CASM 25.2.CASM was run in Phase II mode.Timing Requirements:
To clarify, we are trying to define a lightcurve, so we would like to space our 10 orbits at roughly equal intervals through the observing window, if possible. Assuming the window start time is 11-Dec-2017:00:00:00 and the end time is 14-Dec-2017:11:39:00 (according to the visit planner - presumably defined by the time at which the comet enters the solar exclusion zone) then the intervals would be an average of ~9 hrs. In the requirements below, we specify intervals of 6 to 12 hrs (and are willing to relax that even further to facilitate scheduling) but would like to span the majority of the observing window.151316159800077.0(Tic-Visit
:proposal-id 15421
:visit-id "08"
:proposal-version -1
:trans-version "20171009"
:date "27-Nov-2017 21:58:26.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 121872
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15421
:visit-id "08"
:obset-id "08"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15421
:visit-id "08"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2858
:al-overhead-at-end 0
:internal-dur-at-end 170
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)false10Using ephemeris for target 15421-09-41Pephemeris data for target 15421-09-41P does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 17.195 to 19.091. ephemeris interval: 17.304 to 19.305Timing link suitability includes constraints ([09 After 08 by 0.2 to 0.5 days] [10 After 09 by 0.2 to 0.5 days])The scheduling data was generated by CASM 25.2.CASM was run in Phase II mode.Timing Requirements:
To clarify, we are trying to define a lightcurve, so we would like to space our 10 orbits at roughly equal intervals through the observing window, if possible. Assuming the window start time is 11-Dec-2017:00:00:00 and the end time is 14-Dec-2017:11:39:00 (according to the visit planner - presumably defined by the time at which the comet enters the solar exclusion zone) then the intervals would be an average of ~9 hrs. In the requirements below, we specify intervals of 6 to 12 hrs (and are willing to relax that even further to facilitate scheduling) but would like to span the majority of the observing window.151318398800074.3982281536(Tic-Visit
:proposal-id 15421
:visit-id "09"
:proposal-version -1
:trans-version "20171009"
:date "27-Nov-2017 21:58:27.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 121872
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15421
:visit-id "09"
:obset-id "09"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15421
:visit-id "09"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2858
:al-overhead-at-end 0
:internal-dur-at-end 170
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)false10Using ephemeris for target 15421-10-41Pephemeris data for target 15421-10-41P does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 17.195 to 19.091. ephemeris interval: 17.304 to 19.305Timing link suitability includes constraints ([10 After 09 by 0.2 to 0.5 days])The scheduling data was generated by CASM 25.2.CASM was run in Phase II mode.Timing Requirements:
To clarify, we are trying to define a lightcurve, so we would like to space our 10 orbits at roughly equal intervals through the observing window, if possible. Assuming the window start time is 11-Dec-2017:00:00:00 and the end time is 14-Dec-2017:11:39:00 (according to the visit planner - presumably defined by the time at which the comet enters the solar exclusion zone) then the intervals would be an average of ~9 hrs. In the requirements below, we specify intervals of 6 to 12 hrs (and are willing to relax that even further to facilitate scheduling) but would like to span the majority of the observing window.151321260200074.37437364373179(Tic-Visit
:proposal-id 15421
:visit-id "10"
:proposal-version -1
:trans-version "20171009"
:date "27-Nov-2017 21:58:28.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 121872
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 15421
:visit-id "10"
:obset-id "10"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 15421
:visit-id "10"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2858
:al-overhead-at-end 0
:internal-dur-at-end 170
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3202
:pcs-gap 0
)false10