For G160M observations, please consult Chapter 9 of the COS Instrument Handbook to estimate overheads and the number of exposures per orbit, and consequently the correct lifetime position. Use of LP4 with G160M requires justification in the "Special Requirements" section of the Phase I PDF. Use of the default LP6 with G160M requires no justification. Proposals can be submitted with the warning present.
For G160M observations, please consult Chapter 9 of the COS Instrument Handbook to estimate overheads and the number of exposures per orbit, and consequently the correct lifetime position. Use of LP4 with G160M requires justification in the "Special Requirements" section of the Phase I PDF. Use of the default LP6 with G160M requires no justification. Proposals can be submitted with the warning present.Submission 2. Minor text updates.-141398980Assigned ID: 5597
----- Attempting Submission 1 (Tue Mar 26 19:57:22 GMT 2024) -----
HST Phase I Proposal 5597 successfully submitted.
Receipt: # 5597-1
----- Attempting Submission 2 (Tue Mar 26 23:53:20 GMT 2024) -----
HST Phase I Proposal 5597 successfully submitted.
Receipt: # 5597-2These warnings are related to the lifetime position when using the G160M grating. We will be using LP6, which requires no justification.The number of orbits used exceeds the number allocated
This target is not used in this proposal.
For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser.
COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details.
For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser.
COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details.
For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser.
COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details.
For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser.
COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details.
For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser.
COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details.
For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser.
COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details.
For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser.
COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details.
For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser.
COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details.
For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser.
COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details.
For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser.
COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details.
For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser.
COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details.
For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser.
COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details.
For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser.
COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details.
For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser.
COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details.
For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser.
COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details.
For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser.
COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details.
For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser.
COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details.
For the best data quality, it is generally required to use all four FP-POS positions at a given COS cenwave (or 2 positions for certain exception cases). See extended explanation in the diagnostic browser.
COS FUV PSA science exposures with extended targets have special calibration limitations. See "Errors and Warnings" for more details.Contingent on the discovery of the next active ISO we will need to resubmit with JPL ephemerides, which we will likely need to update several times prior to execution.
-Update July 7, 2025: 3I/ATLAS is confirmed interstellar, and we wish to trigger our ToO.
-Update July 23, 2025: removed NON-INT sequences, updated JPL Horizons ephemeris, and removed BETWEEN/WITHIN timing constraints
-Update July 23, 2025: Removed AFTER VISIT constraint, added BETWEEN to all visits, moved windows to optimize odds of success.
-Update August 12, 2025: Moved BETWEEN constraint up by 1 week (Dec. 1-14, instead of Dec. 7-21) to optimize target brightness.
-Update October 3,2025: Auto-adjust exposure times to prevent orbital overrun at SCHED=100, per C. Rodriguez' request.
-Update October 6, 2025: Made following changes per C. Rodriguez' request:
COS exposure times down to 500s per exposure. This is approximately 60% of our proposed exposure time per orbit (1000 s vs. 1700 s)
STIS exposure times down to 1100s/1500s (1st/2nd orbit of visit, respectively). This is about 70% of our proposed exposure time.
New BETWEEN is 27-NOV-2025 to 31-DEC-2025
WITHIN constraint relaxed to 7 days.
-Update October 9, 2025: Split COS and STIS 2-orbit visits into single orbits on advice of C. Rodriguez to improve schedulability.
New orbits are 01, 02, 03, 04, 07,08, 09,10.
New orbits have same SCHED=100, BETWEEN, and sequence WITHIN constraints.
NUV images at the end of COS visits in Version 6 have been removed with addition of new ACQ/Image exposures for the new orbits.
-Update October 29, 2025: COS orbits now have a single FP per orbit, with FP-1 repeated, per suggestion from S. Hasselquist.
STIS exposures changed from ACCUM to TIME-TAG w/ BUFFER-TIME set to 99 seconds, per suggestion from S. Dieterich.
Updated 3I/ATLAS orbital elements from Horizons.
-Update November 21, 2025: Updated orbital solution for 3I/ATLAS to JPL #30.
-Update November 21, 2025: Resubmitting on request of C. Rodriguez
-Update December 17, 2025: Resubmitting with JPL44 astrometry for target to update visits 10-14 with duplicates (corresponding to Visits 15-19)
-Update December 19, 2025: Following TTRB approval for a repeat of Epoch 1, Visits 1-7 have been repeated here as Visits 20-26 using JPL orbital solution 44.1173270456----- Attempting Submission 1 (Fri Aug 02 20:05:45 GMT 2024) -----
HST Phase II Proposal 17780 successfully submitted.
Receipt: # 17780-1
----- Attempting Submission 2 (Mon Jul 07 15:02:07 GMT 2025) -----
HST Phase II Proposal 17780 successfully submitted.
Receipt: # 17780-2
----- Attempting Submission 3 (Wed Jul 23 17:09:47 GMT 2025) -----
HST Phase II Proposal 17780 successfully submitted.
Receipt: # 17780-3
----- Attempting Submission 4 (Wed Jul 23 21:42:25 GMT 2025) -----
HST Phase II Proposal 17780 successfully submitted.
Receipt: # 17780-4
----- Attempting Submission 5 (Tue Aug 12 14:23:04 GMT 2025) -----
----- Attempting Submission 6 (Fri Oct 03 09:52:45 GMT 2025) -----
----- Attempting Submission 8 (Mon Oct 06 17:10:56 GMT 2025) -----
HST Phase II Proposal 17780 successfully submitted.
Receipt: # 17780-8
----- Attempting Submission 9 (Thu Oct 09 17:37:26 GMT 2025) -----
HST Phase II Proposal 17780 successfully submitted.
Receipt: # 17780-9
----- Attempting Submission 10 (Thu Oct 09 23:58:46 GMT 2025) -----
----- Attempting Submission 11 (Wed Oct 29 15:19:56 GMT 2025) -----
----- Attempting Submission 12 (Fri Nov 21 10:54:48 GMT 2025) -----
----- Attempting Submission 13 (Fri Nov 21 20:50:01 GMT 2025) -----
HST Phase II Proposal 17780 successfully submitted.
Receipt: # 17780-13
----- Attempting Submission 14 (Thu Dec 18 19:40:29 GMT 2025) -----
HST Phase II Proposal 17780 successfully submitted.
Receipt: # 17780-14
----- Attempting Submission 15 (Thu Dec 18 19:42:04 GMT 2025) -----
----- Attempting Submission 16 (Fri Dec 19 23:26:16 GMT 2025) -----Many of these are COS PSA, which we understand. The generic Target ISO ToO is kept in to preserve our initial plan, but is not used in any visits.
The number of orbits exceed as C. Rodriguez asked to duplicate visits 10-14 to update the target to 3I/ATLAS w/ JPL solution 44 ephemerides.Testing The Refractory Sulfur Reservoir Hypothesis with the Next Interstellar ObjectComets are the leftovers of the era of solar system formation and, as such contain some of the most primitive materials available for study. Interstellar comets allow us to probe the volatile and organic composition of a protoplanetary disk's cold midplane, where sub-mm and IR observations cannot penetrate. Within those disks, sulfur reservoirs are currently a major source of interest in the astrophysics community as less than 0.1% of the cosmic abundance of sulfur can be traced in gas species. Recent studies imply that the missing sulfur is trapped in refractory components, but which minerals are not yet clear. Ejected icy planetesimals offer unique opportunities to investigate sulfur-bearing species that would be locked in ice or dust in the midplane of these protoplanetary disks, revealed by an interstellar object's heating as it enters our solar system. With the imminent first light of LSST it is highly anticipated that several more will be discovered in the next few years. The time domain observations measured with HST COS during the apparition of the first active interstellar comet, 2I/Borisov, resulted in a first picture of the chemical composition of those volatiles present in another planetary system, but were not sensitive to sulfur or sulfur-bearing species. We propose a Target of Opportunity program to observe the next active interstellar object, which has yet to be discovered. We will quantify its CS, S2, and atomic sulfur reservoirs, a combination of species that is unique to HST's far-ultraviolet (FUV) capability, and measure the sulfur-to-oxygen ratio while providing unparalleled sensitivity to the commonly occurring cometary species CO and OH.1. Overall observational strategy
We plan to observe the next active interstellar object with V<15 with two instrument settings, COS G160M CENWAVE 1589 A and STIS G230L, in two temporally separated epochs. The FOV will be centered at the comet. Therefore, we will use the same 4 visit (7 orbit) observing sequence (3 COS visits and one STIS visit) for each epoch.
The sequence in each 2-orbit COS visit is:
ACQ/IMAGE in NUV MIRROR A with PSA setting, 30 s exposure
G160M FP-POS# 1794 s
G160M FP-POS# 1794 s
ACQ/IMAGE in NUV MIRROR A with PSA setting, 30 s exposure
We will alternate the FP positions to cycle through all four FP-POS in each epoch. The first 2 visits in an epoch will cycle through FP-POS 1-4, one FP per orbit.
For the third COS visit in each epoch the sequence is:
ACQ/IMAGE in NUV MIRROR A with PSA setting, 30 s exposure
G160M FP-POS1 897 s
G160M FP-POS# 897 s
The 3rd visit cycles FP-POS=1 and FP-POS=2 in a single orbit. The trailing ACQ/IMAGE used in for the first and second COS visits is eliminated to improve science overhead.
This leads to a total exposure time in FP 1 and 2 each of 2691 s and 1794 s for each FP 3 and 4, for a total exposure time of 8970 s over 5 orbits. The exposure time is based on COS ETC run #COS.sp.1928787.
The sequence for each 2-orbit STIS G230L visit is:
ACQ in MIRROR with F28X50LP, 3 s exposure
G230L with 52X0.5, 1900 s exposure
IMAGE in MIRROR with F28X50LP, 3 s
G230L with 52X0.5, 19000 s exposure
IMAGE in MIRROR with F28X50LP
This leads to a total exposure time of 3800s over two orbits. The exposure time is based on STIS ETC run #STIS.sp.1928799
2. Comet position uncertainty and acquisition:
Upon discovery the next active interstellar object we will work rapidly to improve the ephemerides uncertainties. If it becomes clear that we should expect a 3-sigma uncertainty in RA or DEC in the range of 1.5" we will replace the primary ACQ/IMAGE in each COS visit with an ACQ/SEARCH pattern to ensure detection.Our team has extensive experience with HST and consists of expert observers, modelers, and data analysts, who have developed sophisticated techniques for measuring and interpreting comet activity and composition. All team members will aid in integrating the results from the COS and STIS data and will be involved in the preparation of scientific publications.
The PI and team leader John Noonan (Auburn U.) is a postdoctoral research fellow with Far Ultraviolet (FUV) comet observation experience with both Rosetta Alice UVS and HST, and is an expert in the analysis and interpretation of cometary spectra. Dennis Bodewits (Auburn U.) is an expert on comet activity and coma physics and brings experience with the Rosetta and EPOXI comet missions. He has led several comet observing campaigns for space-based telescopes, including comet observations with HST, Chandra, XMM-Newton, and the Neil Gehrels-Swift Observatory. He is a co-investigator of the approved JWST TOO program to observe an interstellar object. Jian-Yang Li is an expert comet observer who has successfully led and/or participated in over 20 HST programs and is highly experienced in working with the STScI staff to schedule time-critical observations. He will assist with the scheduling and first look at data to ensure the observations are performed successfully. Martin Cordiner (GSFC/Catholic University of America) is an expert in observing and modeling both bound and unbound planetary atmospheres with infrared and sub-mm observatories. He will assist in the coordination with JWST and in analysis and interpretation of the data. Nathan Roth (GSFC/American University) is an early career scientist and expert in cometary near-IR/radio spectroscopy. He will assist with observations, analysis and interpretation of the data. Davide Farnocchia (JPL) is an expert in characterizing and modeling the orbits of small bodies in the solar system and has provided critical support in the past HST observations of comets for the ephemerides updates. Marco Micheli (ESA NEOCC) is an expert observational astronomer and has vast experience extracting astrometry and characterizing small body orbits. Olga Harrington Pinto (Auburn U.) is an expert in cometary activity and composition trends and has experience with Spitzer space telescope analysis. The team's successful campaigns to characterize the atomic and molecular abundances of interstellar comet 2I/Borisov with both HST (GO-16049) and ALMA give them a unique experiential advantage to observe the next interstellar object while implementing the lessons learned from their previous ISO campaigns.Solar System AstronomyExoplanets and Exoplanet Formation6falsetruefalsefalsefalsefalsefalseSUPPORTEDSOLAR SYSTEMYESWe will trigger our ToO upon the detection of an active ISO, that is, with an hyperbolic orbit with a barycentric eccentricity significantly greater than unity as reported by the JPL Small-body Database, that has a perihelion within 2 au and reaches at least V=15. Activity will be defined as having a distinct coma upon detection that manifests as a nonstellar point spread function in discovery images and that persists in all follow-up observations. We will coordinate with the JWST ToO team to trigger on the same object and focus HST's capability near perihelion, where JWST may not be able to observe depending on the object's path through the solar system.
On July 1, 2025 a new active ISO was discovered inbound; 3I/ATLAS. It was discovered at a V magnitude of ~18 and is expected to reach V~13 just prior to entering the solar keepout zone.COMETInterstellar ObjectTYPE=COMET,Q=1.356402568640983,E=6.139356333373651,I=175.1130738297457
,O=322.1563556123334,W=128.009728549728,T=29-OCT-2025:11:34:20,TTimeScale=TDB,EQUINOX=J2000,EPOCH=26-JUL-2025:00:00:00,EpochTimeScale=TDB,R0=2.808
,DT=0.
,A1=4.586562347412E-7,A2=2.042488479614E-7,A3=0.
,ALN=0.1112620426,NM=2.15,NN=5.093,NK=4.6142,AMRAT=0.EARTHSOLAR SYSTEMYESWe will trigger our ToO upon the detection of an active ISO, that is, with an hyperbolic orbit with a barycentric eccentricity significantly greater than unity as reported by the JPL Small-body Database, that has a perihelion within 2 au and reaches at least V=15. Activity will be defined as having a distinct coma upon detection that manifests as a nonstellar point spread function in discovery images and that persists in all follow-up observations. We will coordinate with the JWST ToO team to trigger on the same object and focus HST's capability near perihelion, where JWST may not be able to observe depending on the object's path through the solar system.
On July 1, 2025 a new active ISO was discovered inbound; 3I/ATLAS. It was discovered at a V magnitude of ~18 and is expected to reach V~13 just prior to entering the solar keepout zone.COMETInterstellar ObjectTYPE=COMET,Q=1.356418761995381,E=6.139422831829797,I=175.1130917268881
,O=322.1566239181344,W=128.0096924001076,T=29-OCT-2025:11:34:23,TTimeScale=TDB,EQUINOX=J2000,EPOCH=07-AUG-2025:00:00:00,EpochTimeScale=TDB,R0=1.
,DT=0.
,A1=4.572104930878E-8,A2=1.862444758415E-8,A3=-5.019464492798E-9
,ALN=1.,NM=2.,NN=0.,NK=0.,AMRAT=0.EARTHSOLAR SYSTEMCOMETWe will trigger our ToO upon the detection of an active ISO, that is, with an hyperbolic orbit with a barycentric eccentricity significantly greater than unity as reported by the JPL Small-body Database, that has a perihelion within 2 au and reaches at least V=15. Activity will be defined as having a distinct coma upon detection that manifests as a nonstellar point spread function in discovery images and that persists in all follow-up observations. We will coordinate with the JWST ToO team to trigger on the same object and focus HST's capability near perihelion, where JWST may not be able to observe depending on the object's path through the solar system.
On July 1, 2025 a new active ISO was discovered inbound; 3I/ATLAS. It was discovered at a V magnitude of ~18 and is expected to reach V~13 just prior to entering the solar keepout zone.Active Interstellar CometCOS/FUVSpectroscopicNoNoG160M1589COS/FUVSpectroscopicNoNoG160M1589STIS/NUV-MAMASpectroscopicNoNoG230L2376STIS/NUV-MAMASpectroscopicNoNoG230L2376Using ephemeris for target 17780-01-3IATLASephemeris data for target 17780-01-3IATLAS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07) Within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.1765845046000295.8468583440316(Tic-Visit
:proposal-id 17780
:visit-id "01"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:46.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 52368
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "01"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2127
:al-overhead-at-end 0
:internal-dur-at-end 478
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-02-3IATLASephemeris data for target 17780-02-3IATLAS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07) Within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.1765895894000303.8632018472154(Tic-Visit
:proposal-id 17780
:visit-id "02"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:46.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 52368
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "02"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2127
:al-overhead-at-end 0
:internal-dur-at-end 478
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-03-3IATLASephemeris data for target 17780-03-3IATLAS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07) Within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.1765902031000312.21790182384177(Tic-Visit
:proposal-id 17780
:visit-id "03"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:47.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 52368
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "03"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2127
:al-overhead-at-end 0
:internal-dur-at-end 478
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-04-3IATLASephemeris data for target 17780-04-3IATLAS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07) Within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.1765907194000294.3400294131128(Tic-Visit
:proposal-id 17780
:visit-id "04"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:47.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 52368
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "04"
:obset-id "04"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "04"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2127
:al-overhead-at-end 0
:internal-dur-at-end 478
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-05-3IATLASephemeris data for target 17780-05-3IATLAS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07) Within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.1765997590000272.17370325475366(Tic-Visit
:proposal-id 17780
:visit-id "05"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:47.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 52368
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "05"
:obset-id "05"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "05"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2127
:al-overhead-at-end 0
:internal-dur-at-end 478
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-06-3IATLASephemeris data for target 17780-06-3IATLAS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07) Within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.1766003240000299.753869888708(Tic-Visit
:proposal-id 17780
:visit-id "06"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:48.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 820032
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "06"
:obset-id "06"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "06"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2126
:al-overhead-at-end 0
:internal-dur-at-end 340
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-07-3IATLASephemeris data for target 17780-07-3IATLAS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (01 02 03 04 05 06 07) Within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.1766065541000277.87(Tic-Visit
:proposal-id 17780
:visit-id "07"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:48.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 820032
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "07"
:obset-id "07"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "07"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2126
:al-overhead-at-end 0
:internal-dur-at-end 340
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-20-3IATLAS-JPL44ephemeris data for target 17780-20-3IATLAS-JPL44 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (20 21 22 23 24 25 26) Within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 17780
:visit-id "20"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:49.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 52368
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "20"
:obset-id "20"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "20"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2127
:al-overhead-at-end 0
:internal-dur-at-end 478
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-21-3IATLAS-JPL44ephemeris data for target 17780-21-3IATLAS-JPL44 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (20 21 22 23 24 25 26) Within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 17780
:visit-id "21"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:49.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 52368
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "21"
:obset-id "21"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "21"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2127
:al-overhead-at-end 0
:internal-dur-at-end 478
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-22-3IATLAS-JPL44ephemeris data for target 17780-22-3IATLAS-JPL44 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (20 21 22 23 24 25 26) Within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 17780
:visit-id "22"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:49.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 52368
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "22"
:obset-id "22"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "22"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2127
:al-overhead-at-end 0
:internal-dur-at-end 478
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-23-3IATLAS-JPL44ephemeris data for target 17780-23-3IATLAS-JPL44 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (20 21 22 23 24 25 26) Within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 17780
:visit-id "23"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:50.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 52368
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "23"
:obset-id "23"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "23"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2127
:al-overhead-at-end 0
:internal-dur-at-end 478
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-24-3IATLAS-JPL44ephemeris data for target 17780-24-3IATLAS-JPL44 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (20 21 22 23 24 25 26) Within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 17780
:visit-id "24"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:50.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 52368
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "24"
:obset-id "24"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "24"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2127
:al-overhead-at-end 0
:internal-dur-at-end 478
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-25-3IATLAS-JPL44ephemeris data for target 17780-25-3IATLAS-JPL44 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (20 21 22 23 24 25 26) Within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 17780
:visit-id "25"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:50.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 820032
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "25"
:obset-id "25"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "25"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2126
:al-overhead-at-end 0
:internal-dur-at-end 340
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-26-3IATLAS-JPL44ephemeris data for target 17780-26-3IATLAS-JPL44 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (20 21 22 23 24 25 26) Within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 17780
:visit-id "26"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:51.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 820032
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "26"
:obset-id "26"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "26"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2126
:al-overhead-at-end 0
:internal-dur-at-end 340
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-08-3IATLASephemeris data for target 17780-08-3IATLAS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (08 09 10 11 12 13 14) Within 7.0 days] [Sequence (08 09 10 11 12 13 14) within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.1766347855000280.1677290641191(Tic-Visit
:proposal-id 17780
:visit-id "08"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:51.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 52368
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "08"
:obset-id "08"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "08"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2127
:al-overhead-at-end 0
:internal-dur-at-end 478
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-09-3IATLASephemeris data for target 17780-09-3IATLAS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (08 09 10 11 12 13 14) Within 7.0 days] [Sequence (08 09 10 11 12 13 14) within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.1766353964000303.7825965851099(Tic-Visit
:proposal-id 17780
:visit-id "09"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:52.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 52368
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "09"
:obset-id "09"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "09"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2127
:al-overhead-at-end 0
:internal-dur-at-end 478
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-10-3IATLASephemeris data for target 17780-10-3IATLAS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (08 09 10 11 12 13 14) Within 7.0 days] [Sequence (08 09 10 11 12 13 14) within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 17780
:visit-id "10"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:52.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 52368
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "10"
:obset-id "10"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "10"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2127
:al-overhead-at-end 0
:internal-dur-at-end 478
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-11-3IATLASephemeris data for target 17780-11-3IATLAS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (08 09 10 11 12 13 14) Within 7.0 days] [Sequence (08 09 10 11 12 13 14) within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 17780
:visit-id "11"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:52.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 52368
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "11"
:obset-id "11"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "11"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2127
:al-overhead-at-end 0
:internal-dur-at-end 478
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-12-3IATLASephemeris data for target 17780-12-3IATLAS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (08 09 10 11 12 13 14) Within 7.0 days] [Sequence (08 09 10 11 12 13 14) within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 17780
:visit-id "12"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:53.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 52368
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "12"
:obset-id "12"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "12"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2127
:al-overhead-at-end 0
:internal-dur-at-end 478
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-13-3IATLASephemeris data for target 17780-13-3IATLAS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (08 09 10 11 12 13 14) Within 7.0 days] [Sequence (08 09 10 11 12 13 14) within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 17780
:visit-id "13"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:53.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 820032
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "13"
:obset-id "13"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "13"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2126
:al-overhead-at-end 0
:internal-dur-at-end 340
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-14-3IATLASephemeris data for target 17780-14-3IATLAS does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335Timing link suitability includes constraints ([Group (08 09 10 11 12 13 14) Within 7.0 days] [Sequence (08 09 10 11 12 13 14) within 7.0 days])The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 17780
:visit-id "14"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:54.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 820032
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "14"
:obset-id "14"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "14"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2126
:al-overhead-at-end 0
:internal-dur-at-end 340
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-15-3IATLAS-JPL44ephemeris data for target 17780-15-3IATLAS-JPL44 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.1766438211000275.56934417519483(Tic-Visit
:proposal-id 17780
:visit-id "15"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:54.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 52368
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "15"
:obset-id "15"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "15"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2127
:al-overhead-at-end 0
:internal-dur-at-end 478
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-16-3IATLAS-JPL44ephemeris data for target 17780-16-3IATLAS-JPL44 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.1766489048000305.7059065122891(Tic-Visit
:proposal-id 17780
:visit-id "16"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:54.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 52368
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "16"
:obset-id "16"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "16"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2127
:al-overhead-at-end 0
:internal-dur-at-end 478
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-17-3IATLAS-JPL44ephemeris data for target 17780-17-3IATLAS-JPL44 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.1766494696000292.6115904926(Tic-Visit
:proposal-id 17780
:visit-id "17"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:55.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 52368
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "17"
:obset-id "17"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "17"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2127
:al-overhead-at-end 0
:internal-dur-at-end 478
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-18-3IATLAS-JPL44ephemeris data for target 17780-18-3IATLAS-JPL44 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.1766500345000311.2885223455147(Tic-Visit
:proposal-id 17780
:visit-id "18"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:55.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 820032
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "18"
:obset-id "18"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "18"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2126
:al-overhead-at-end 0
:internal-dur-at-end 340
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10Using ephemeris for target 17780-19-3IATLAS-JPL44ephemeris data for target 17780-19-3IATLAS-JPL44 does not cover planning interval. Physical constraints are assumed to be unschedulable outside of the ephemeris data. Planning interval: 25.320 to 26.335. ephemeris interval: 25.334 to 27.335The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.1766522939000277.21043620078564(Tic-Visit
:proposal-id 17780
:visit-id "19"
:proposal-version -1
:trans-version "20250929"
:date "19-Dec-2025 18:18:56.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 820032
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 17780
:visit-id "19"
:obset-id "19"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 17780
:visit-id "19"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2126
:al-overhead-at-end 0
:internal-dur-at-end 340
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2867
:pcs-gap 0
)true10