0Assigned ID: 3881
----- Attempting Submission 1 (Wed Dec 21 00:36:18 GMT 2022) -----
HST Phase I Proposal 3881 successfully submitted.
Receipt: # 3881-1
----- Attempting Submission 2 (Wed Dec 21 01:39:18 GMT 2022) -----In this resubmission, visits 22 and 23 are added to repeat visits 02 and 03 which failed. We'd like the repeat visits to be scheduled as soon as possible, so we included a BEFORE March 6 which could be relaxed if needed. -- Max Mutchler714027280----- Attempting Submission 1 (Tue Jan 03 19:18:11 GMT 2023) -----
----- Attempting Submission 2 (Fri Jan 06 16:22:35 GMT 2023) -----
----- Attempting Submission 3 (Wed Feb 08 18:51:33 GMT 2023) -----I ran the VP on on the two new visits and they look schedulable. I did not run VP on the completed visits.The Boulder Field of DidymosDeep post-impact observations of NASA DART asteroid target Didymos, taken on UT 2022 December 19, reveal the existence of a swarm of about 20 discrete, co-moving objects. These are interpreted as boulders lifted from the asteroid surface by the DART impact, with sizes in the approximate range 1 m to 3 m. Depending on the size distribution, large "particles" like those observed may dominate the ejected mass, so that it is important to characterize their properties (especially size), their number, and their velocity. We propose deep observations with HST and WFC3 in order to obtain 2nd-epoch observations of the boulder swarm. We will determine the brightness distribution (a proxy for the size distribution), a constraint on the boulder shape, and estimate the ejection velocities (speed and direction) from astrometric measurements. In addition, the proposed observations will be used to measure and model the diffuse debris trail consisting of centimeter-sized and larger particles, in order to reach the fullest possible characterization of the DART impact ejecta. The observations are urgent because Didymos is rapidly fading as it recedes from the Sun and Earth and because the boulders are already very faint. The proposed measurements maximally capitalize on the resolution and sensitivity of HST. Results will be of value both for the practical understanding of impact physics, and for the interpretation of natural impacts of the type already detected in P/2010 A2 and 596 Scheila. This is a unique observation of a unique event.The observational requirement is that we reach a sensitivity to faint sources comparable to that obtained on UT 2021 December 19. To reach the faintest magnitudes, the science objectives are best met using the same instrument (WFC3) and filter (F350LP) combination as employed in GO 16674 and 17289. The F350LP filter is a long-pass filter with very broad spectral coverage (FWHM > 4000A), providing maximum sensitivity to continuum sources. It has become the standard filter for numerous Hubble GO observations of faint solar system targets, from asteroids and comet nuclei to Kuiper belt objects. Our plan is to obtain dithered images (to escape the effects of bad pixels and the inter-chip gap) with five images per orbit having exposure times of 300 s each. Because co-moving objects are spread over a wide area, we will use the full WFC3 CCD readout, providing a 1600 x 1600 arcsec field of view. Prior observations of moving objects from archived data show that the limiting magnitude is affected by interference from trailed field objects, a problem which does not affect observations of stars and galaxies where no trailing is involved. Galaxies are a particular nuisance, since their diffuse, large-scale and structured brightness is difficult to mask. The best protection from degradation of the sensitivity by trailed objects in the background is provided by obtaining more data with different and uncorrelated backgrounds. Repeated detection of fragments in different orbits, for example, provides rock solid confidence that these objects are real and not noise peaks in the data. For this reason, and because we need to reach extreme depths to sample the objects detected in December 19 data, we request 16 orbits with WFC3 and the F350LP filter. The requested orbits provide unique information on the properties of the largest bodies ejected by the spacecraft impact. In this way we hope to exploit the unique capabilities of HST and the singular opportunity provided by the DART impact to provide the best possible characterization of impact. We request DDT observations to be taken at the earliest opportunity in calendar year 2023, in order to combat progressive geometric fading as the target recedes from the Sun and Earth. As described in the next paragraph, observations near UT 2023 February 1 would permit us to detect all the co-moving boulders detected in the December 19 HST data and therefore we describe the observing conditions on this date. The changing geometry of Didymos motivates observations as early as possible in calendar year 2023. Bearing in mind typical HST response times, we take as a realistic target date UT 2023 February 1. Fading caused by the growing heliocentric and geocentric distances is partly ameliorated by a decrease in the phase angle (i.e. by a reduction in phase dimming). The resulting fading due to geometry is m = 1.72 magnitudes (a factor of about 4.9 in flux density). Therefore, the brightest co-mover will appear at V = 26.5 + 1.7 = 28.2 on February 1, while the faintest reliably detected boulders, at V = 27.8 in the December data, will appear at V = 29.5 on February 1. Note that these estimates neglect the effects of rotation, which can cause any co-mover to be brighter or fainter than estimated here by an amount depending on the shape and rotational state of the body. We used the WFC3 Exposure Time Calculator to find that the brightest co-mover would be detected at SNR (signal-to-noise ratio) = 12.4 and the faintest at SNR = 3.7, on UT 2023 February 1, given 16 orbits of HST with WFC3 and F350LP. Hence, our request is for 16 orbits with WFC3 and F350LP, as close as possible to UT 2023 February 1. The ephemeris uncertainties have no impact on the planned observations. The non-sidereal rates of Didymos as observed from HST fall well with HSTs tracking capabilities (which are limited by linear interpolation from the ephemeris). Rates at the times of the October and December HST observations were 3 to 7 times larger but excellent data were still secured. The elongation of Didymos is 152 on February 1, and remains above the HST solar exclusion zone of 55 until UT 2023 July 6. There is no observationally favorable, comparably close pass to Earth by Didymos until 2062.PI Jewitt is an experienced solar system astronomer and author of numerous papers based on Hubble data. Yoonyoung Kim is an expert in the modeling of dust and debris moving under the action of solar radiation pressure and gravity. Jing Li is a solar and small body observer, with HST experience and facility in analysis of large datasets. Max Mutchler is an expert in the optimum use of HST for difficult HST observations of moving targets, as proposed here.Solar System Astronomy0falseSUPPORTEDSOLAR SYSTEMNOASTEROIDBinary asteroid (65803) DidymosTYPE=ASTEROID,A=1.643091249342108,E=0.3835237757664423,I=3.41380667080487
,O=72.9955220559403,W=319.5574473815775,M=6.411907609321696,EQUINOX=J2000,EPOCH=04-NOV-2022:12:00:00,EpochTimeScale=TDB,R0=1.
,A1=0.,A2=-1.053918254001E-14,A3=0.
,ALN=1.,NM=2.,NN=0.,NK=0.,AMRAT=0.EARTHWFC3/UVISImagingNoNoF350LPUsing ephemeris for target 17293-01-DIDYMOSephemeris data for target 17293-01-DIDYMOS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.365 to 25.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16) Within 2.0 days])The scheduling data was generated by CASM 30.3.CASM was run in Phase II mode./private/var/folders/tj/27ygn_756lz3w1z19s6wtgtm0006vh/T/OPVisit11134427417836289306.xml1675551413000124.0(Tic-Visit
:proposal-id 17293
:visit-id "01"
:proposal-version -1
:trans-version "20220630"
:date "08-Feb-2023 13:46:22.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 422320
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17293
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17293
:visit-id "01"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2069
:al-overhead-at-end 0
:internal-dur-at-end 498
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2782
:pcs-gap 0
)true10Using ephemeris for target 17293-02-DIDYMOSephemeris data for target 17293-02-DIDYMOS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.365 to 25.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16) Within 2.0 days])The scheduling data was generated by CASM 30.3.CASM was run in Phase II mode./private/var/folders/tj/27ygn_756lz3w1z19s6wtgtm0006vh/T/OPVisit15004716207213067168.xml1675556769000117.79911137743471(Tic-Visit
:proposal-id 17293
:visit-id "02"
:proposal-version -1
:trans-version "20220630"
:date "08-Feb-2023 13:46: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 422320
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17293
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17293
:visit-id "02"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2345
:al-overhead-at-end 0
:internal-dur-at-end 498
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2782
:pcs-gap 0
)true10Using ephemeris for target 17293-03-DIDYMOSephemeris data for target 17293-03-DIDYMOS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.365 to 25.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16) Within 2.0 days])The scheduling data was generated by CASM 30.3.CASM was run in Phase II mode./private/var/folders/tj/27ygn_756lz3w1z19s6wtgtm0006vh/T/OPVisit6877136033059644596.xml1675562520000117.79935682021909(Tic-Visit
:proposal-id 17293
:visit-id "03"
:proposal-version -1
:trans-version "20220630"
:date "08-Feb-2023 13:46:24.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 422320
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17293
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17293
:visit-id "03"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2345
:al-overhead-at-end 0
:internal-dur-at-end 498
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2782
:pcs-gap 0
)true10Using ephemeris for target 17293-04-DIDYMOSephemeris data for target 17293-04-DIDYMOS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.365 to 25.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16) Within 2.0 days])The scheduling data was generated by CASM 30.3.CASM was run in Phase II mode./private/var/folders/tj/27ygn_756lz3w1z19s6wtgtm0006vh/T/OPVisit12526948594212133726.xml1675568220000117.79962889855727(Tic-Visit
:proposal-id 17293
:visit-id "04"
:proposal-version -1
:trans-version "20220630"
:date "08-Feb-2023 13:46:24.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 422320
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17293
:visit-id "04"
:obset-id "04"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17293
:visit-id "04"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2345
:al-overhead-at-end 0
:internal-dur-at-end 498
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2782
:pcs-gap 0
)true10Using ephemeris for target 17293-05-DIDYMOSephemeris data for target 17293-05-DIDYMOS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.365 to 25.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16) Within 2.0 days])The scheduling data was generated by CASM 30.3.CASM was run in Phase II mode./private/var/folders/tj/27ygn_756lz3w1z19s6wtgtm0006vh/T/OPVisit2303297812116349603.xml1675573920000117.79630407599922(Tic-Visit
:proposal-id 17293
:visit-id "05"
:proposal-version -1
:trans-version "20220630"
:date "08-Feb-2023 13:46: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 422320
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17293
:visit-id "05"
:obset-id "05"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17293
:visit-id "05"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2345
:al-overhead-at-end 0
:internal-dur-at-end 498
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2782
:pcs-gap 0
)true10Using ephemeris for target 17293-06-DIDYMOSephemeris data for target 17293-06-DIDYMOS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.365 to 25.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16) Within 2.0 days])The scheduling data was generated by CASM 30.3.CASM was run in Phase II mode./private/var/folders/tj/27ygn_756lz3w1z19s6wtgtm0006vh/T/OPVisit8183621507026314639.xml1675579620000117.79663338400093(Tic-Visit
:proposal-id 17293
:visit-id "06"
:proposal-version -1
:trans-version "20220630"
:date "08-Feb-2023 13:46: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 422320
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17293
:visit-id "06"
:obset-id "06"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17293
:visit-id "06"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2345
:al-overhead-at-end 0
:internal-dur-at-end 498
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2782
:pcs-gap 0
)true10Using ephemeris for target 17293-07-DIDYMOSephemeris data for target 17293-07-DIDYMOS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.365 to 25.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16) Within 2.0 days])The scheduling data was generated by CASM 30.3.CASM was run in Phase II mode./private/var/folders/tj/27ygn_756lz3w1z19s6wtgtm0006vh/T/OPVisit1903367737077827071.xml1675585320000122.89685708404022(Tic-Visit
:proposal-id 17293
:visit-id "07"
:proposal-version -1
:trans-version "20220630"
:date "08-Feb-2023 13:46: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 422320
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17293
:visit-id "07"
:obset-id "07"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17293
:visit-id "07"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2345
:al-overhead-at-end 0
:internal-dur-at-end 498
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2782
:pcs-gap 0
)true10Using ephemeris for target 17293-08-DIDYMOSephemeris data for target 17293-08-DIDYMOS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.365 to 25.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16) Within 2.0 days])The scheduling data was generated by CASM 30.3.CASM was run in Phase II mode./private/var/folders/tj/27ygn_756lz3w1z19s6wtgtm0006vh/T/OPVisit2169202520393956787.xml1675591080000122.89724760671578(Tic-Visit
:proposal-id 17293
:visit-id "08"
:proposal-version -1
:trans-version "20220630"
:date "08-Feb-2023 13:46: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 422320
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17293
:visit-id "08"
:obset-id "08"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17293
:visit-id "08"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2345
:al-overhead-at-end 0
:internal-dur-at-end 498
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2782
:pcs-gap 0
)true10Using ephemeris for target 17293-09-DIDYMOSephemeris data for target 17293-09-DIDYMOS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.365 to 25.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16) Within 2.0 days])The scheduling data was generated by CASM 30.3.CASM was run in Phase II mode./private/var/folders/tj/27ygn_756lz3w1z19s6wtgtm0006vh/T/OPVisit14514661762705159942.xml167559678000093.74747322642821(Tic-Visit
:proposal-id 17293
:visit-id "09"
:proposal-version -1
:trans-version "20220630"
:date "08-Feb-2023 13:46: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 422320
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17293
:visit-id "09"
:obset-id "09"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17293
:visit-id "09"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2345
:al-overhead-at-end 0
:internal-dur-at-end 498
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2782
:pcs-gap 0
)true10Using ephemeris for target 17293-10-DIDYMOSephemeris data for target 17293-10-DIDYMOS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.365 to 25.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16) Within 2.0 days])The scheduling data was generated by CASM 30.3.CASM was run in Phase II mode./private/var/folders/tj/27ygn_756lz3w1z19s6wtgtm0006vh/T/OPVisit17276802987642241441.xml1675602480000109.96788000089322(Tic-Visit
:proposal-id 17293
:visit-id "10"
:proposal-version -1
:trans-version "20220630"
:date "08-Feb-2023 13:46: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 422320
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17293
:visit-id "10"
:obset-id "10"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17293
:visit-id "10"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2345
:al-overhead-at-end 0
:internal-dur-at-end 498
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2782
:pcs-gap 0
)true10Using ephemeris for target 17293-11-DIDYMOSephemeris data for target 17293-11-DIDYMOS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.365 to 25.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16) Within 2.0 days])The scheduling data was generated by CASM 30.3.CASM was run in Phase II mode./private/var/folders/tj/27ygn_756lz3w1z19s6wtgtm0006vh/T/OPVisit343031146107647652.xml1675608180000109.93010361549892(Tic-Visit
:proposal-id 17293
:visit-id "11"
:proposal-version -1
:trans-version "20220630"
:date "08-Feb-2023 13:46: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 422320
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17293
:visit-id "11"
:obset-id "11"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17293
:visit-id "11"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2345
:al-overhead-at-end 0
:internal-dur-at-end 498
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2782
:pcs-gap 0
)true10Using ephemeris for target 17293-12-DIDYMOSephemeris data for target 17293-12-DIDYMOS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.365 to 25.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16) Within 2.0 days])The scheduling data was generated by CASM 30.3.CASM was run in Phase II mode./private/var/folders/tj/27ygn_756lz3w1z19s6wtgtm0006vh/T/OPVisit6863271423194560584.xml1675613880000122.09546485260472(Tic-Visit
:proposal-id 17293
:visit-id "12"
:proposal-version -1
:trans-version "20220630"
:date "08-Feb-2023 13:46: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 422320
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17293
:visit-id "12"
:obset-id "12"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17293
:visit-id "12"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2345
:al-overhead-at-end 0
:internal-dur-at-end 498
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2782
:pcs-gap 0
)true10Using ephemeris for target 17293-13-DIDYMOSephemeris data for target 17293-13-DIDYMOS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.365 to 25.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16) Within 2.0 days])The scheduling data was generated by CASM 30.3.CASM was run in Phase II mode./private/var/folders/tj/27ygn_756lz3w1z19s6wtgtm0006vh/T/OPVisit15986929095633046541.xml1675619820000122.09601802046842(Tic-Visit
:proposal-id 17293
:visit-id "13"
:proposal-version -1
:trans-version "20220630"
:date "08-Feb-2023 13:46: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 422320
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17293
:visit-id "13"
:obset-id "13"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17293
:visit-id "13"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2195
:al-overhead-at-end 0
:internal-dur-at-end 498
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2782
:pcs-gap 0
)true10Using ephemeris for target 17293-14-DIDYMOSephemeris data for target 17293-14-DIDYMOS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.365 to 25.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16) Within 2.0 days])The scheduling data was generated by CASM 30.3.CASM was run in Phase II mode./private/var/folders/tj/27ygn_756lz3w1z19s6wtgtm0006vh/T/OPVisit8334726474180249683.xml167551680500095.47906869408621(Tic-Visit
:proposal-id 17293
:visit-id "14"
:proposal-version -1
:trans-version "20220630"
:date "08-Feb-2023 13:46:30.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 422320
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17293
:visit-id "14"
:obset-id "14"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17293
:visit-id "14"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2345
:al-overhead-at-end 0
:internal-dur-at-end 498
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2782
:pcs-gap 0
)true10Using ephemeris for target 17293-15-DIDYMOSephemeris data for target 17293-15-DIDYMOS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.365 to 25.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16) Within 2.0 days])The scheduling data was generated by CASM 30.3.CASM was run in Phase II mode./private/var/folders/tj/27ygn_756lz3w1z19s6wtgtm0006vh/T/OPVisit4338412496644107212.xml167552256000095.47910993252748(Tic-Visit
:proposal-id 17293
:visit-id "15"
:proposal-version -1
:trans-version "20220630"
:date "08-Feb-2023 13:46:30.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 422320
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17293
:visit-id "15"
:obset-id "15"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17293
:visit-id "15"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2345
:al-overhead-at-end 0
:internal-dur-at-end 498
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2782
:pcs-gap 0
)true10Using ephemeris for target 17293-16-DIDYMOSephemeris data for target 17293-16-DIDYMOS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 22.213 to 24.182. ephemeris interval: 22.365 to 25.001Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16) Within 2.0 days])The scheduling data was generated by CASM 30.3.CASM was run in Phase II mode./private/var/folders/tj/27ygn_756lz3w1z19s6wtgtm0006vh/T/OPVisit16328257381929024907.xml167552826000095.47917992565021(Tic-Visit
:proposal-id 17293
:visit-id "16"
:proposal-version -1
:trans-version "20220630"
:date "08-Feb-2023 13:46:31.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 422320
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17293
:visit-id "16"
:obset-id "16"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17293
:visit-id "16"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2345
:al-overhead-at-end 0
:internal-dur-at-end 498
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2782
:pcs-gap 0
)true10Using ephemeris for target 17293-22-DIDYMOSephemeris data for target 17293-22-DIDYMOS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.004 to 24.182. ephemeris interval: 23.031 to 25.032The scheduling data was generated by CASM 30.3.CASM was run in Phase II mode./private/var/folders/tj/27ygn_756lz3w1z19s6wtgtm0006vh/T/OPVisit17701561863809982750.xml(Tic-Visit
:proposal-id 17293
:visit-id "22"
:proposal-version -1
:trans-version "20220630"
:date "08-Feb-2023 13:46: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 422320
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17293
:visit-id "22"
:obset-id "22"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17293
:visit-id "22"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2345
:al-overhead-at-end 0
:internal-dur-at-end 498
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2782
:pcs-gap 0
)true10Using ephemeris for target 17293-23-DIDYMOSephemeris data for target 17293-23-DIDYMOS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 23.004 to 24.182. ephemeris interval: 23.031 to 25.032The scheduling data was generated by CASM 30.3.CASM was run in Phase II mode./private/var/folders/tj/27ygn_756lz3w1z19s6wtgtm0006vh/T/OPVisit11851980622012854021.xml(Tic-Visit
:proposal-id 17293
:visit-id "23"
:proposal-version -1
:trans-version "20220630"
:date "08-Feb-2023 13:46: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 422320
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17293
:visit-id "23"
:obset-id "23"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17293
:visit-id "23"
:orbit-number 1
:pcs-time 393
:si-vis-utilization 2345
:al-overhead-at-end 0
:internal-dur-at-end 498
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2782
:pcs-gap 0
)true10