0Assigned ID: 6313
----- Attempting Submission 1 (Wed Apr 09 23:11:01 GMT 2025) -----
HST Phase I Proposal 6313 successfully submitted.
Receipt: # 6313-1
----- Attempting Submission 2 (Thu Apr 10 18:21:08 GMT 2025) -----Updated Phase 2 to ensure no orbital over-runs.
Reduced exposure time for PG1015562326069----- Attempting Submission 1 (Wed Aug 13 23:00:13 GMT 2025) -----
----- Attempting Submission 2 (Wed Nov 26 23:20:13 GMT 2025) -----
----- Attempting Submission 3 (Tue Dec 09 04:13:46 GMT 2025) -----Is Sulfur stored in the refractory or volatile component of planetary building blocks?Sulfur plays a key role in geochemical cycling on the Solar System's terrestrial planets and is required by all life. It can also form important spectrally active species in exoplanet atmospheres, affecting their climates and habitability. Yet, how abundant sulfur will be in exoplanets depends critically on how it is delivered to rocky planets during their formation, a journey that remains uncertain. Most notably it is not clear whether Sulfur is stored in the refractory (dust) phase of planetary building blocks or rather the volatile (ice) phase, the latter being much more readily lost to planets forming in the warm inner disk. This proposal will determine the Sulfur abundances in the planetary material in the atmospheres of 12 white dwarfs. Alongside oxygen, the abundances will tell us whether Sulfur is in ice or dust, providing a sufficiently large sample to answer the null hypothesis that Sulfur is predominantly found in the ice phase.This program aims to measure the Sulfur abundance in a sample of polluted white dwarfs. All targets are brighter than 16.7 mag in GALEX NUV.
Our primary setup is the G185M grating with a central wavelength of 1921A, which covers key sulfur lines SI 1807.3A and 1820.3A. For 4 targets (specially those with Helium-rich atmospheres) the S I 1253.8A is the strongest sulfur line, and therefore the G130M grating with a central wavelength of 1291A is used instead.
Reduced gyro observations: Our observations are not time critical, and can be scheduled any time, so reducing the possible observing windows will not affect this proposal. Using the visit planner tool, there are plenty of schedulable opportunities across the cycle for all targets. Target acquisition is required for all of our targets in order to sucessfully complete the proposed observations.
Scheduling: For targets which require >3 orbits, we have split the visits up to ensure maximum schedulability.Amy Bonsor is an expert on the interpretation of planetary abundances from the atmospheres of white dwarfs.
Siyi Xu and Laura Rogers are experts on spectroscopic observations of white dwarfs.
Patrick Dufour and Simon Blouin are experts on modelling white dwarf atmospheres.
Mihkel Kama is an expert on Sulfur in planet and star-forming regions, who will help link the white dwarf observations to the full story of Sulfur evolution.
Oliver Shorttle is an expert on the geochemical cycling of Sulfur in terrestrial planets and its importance to life.Exoplanets and Exoplanet Formation6falsetruefalsefalsefalsefalsefalseSUPPORTEDSTARDADZNOThis object was generated by the targetselector and retrieved from the SIMBAD database.
SIMBAD listed proper motion for this target. When retrieving targets with PM from SIMBAD, APT requests the coordinates be calculated with an epoch of the year 2000. Do not modify this epoch. Always review coordinates using the Target Confirmation tool, which graphically displays the PM.J2000J2000NUV=14.4STARDADZNOThis object was generated by the targetselector and retrieved from the SIMBAD database.
SIMBAD listed proper motion for this target. When retrieving targets with PM from SIMBAD, APT requests the coordinates be calculated with an epoch of the year 2000. Do not modify this epoch. Always review coordinates using the Target Confirmation tool, which graphically displays the PM.J2000J2000NUV=13.85STARDADZNOThis object was generated by the targetselector and retrieved from the SIMBAD database.
SIMBAD listed proper motion for this target. When retrieving targets with PM from SIMBAD, APT requests the coordinates be calculated with an epoch of the year 2000. Do not modify this epoch. Always review coordinates using the Target Confirmation tool, which graphically displays the PM.J2000J2000NUV=15.08STARDADZNOThis object was generated by the targetselector and retrieved from the SIMBAD database.
SIMBAD listed proper motion for this target. When retrieving targets with PM from SIMBAD, APT requests the coordinates be calculated with an epoch of the year 2000. Do not modify this epoch. Always review coordinates using the Target Confirmation tool, which graphically displays the PM.J2000J2000NUV=16.23STARDADZNOThis object was generated by the targetselector and retrieved from the SIMBAD database.
SIMBAD listed proper motion for this target. When retrieving targets with PM from SIMBAD, APT requests the coordinates be calculated with an epoch of the year 2000. Do not modify this epoch. Always review coordinates using the Target Confirmation tool, which graphically displays the PM.J2000J2000NUV=15.99STARDADZNOThis object was generated by the targetselector and retrieved from the SIMBAD database.
SIMBAD listed proper motion for this target. When retrieving targets with PM from SIMBAD, APT requests the coordinates be calculated with an epoch of the year 2000. Do not modify this epoch. Always review coordinates using the Target Confirmation tool, which graphically displays the PM.J2000J2000NUV=15.59STARDADZNOThis object was generated by the targetselector and retrieved from the SIMBAD database.
SIMBAD listed proper motion for this target. When retrieving targets with PM from SIMBAD, APT requests the coordinates be calculated with an epoch of the year 2000. Do not modify this epoch. Always review coordinates using the Target Confirmation tool, which graphically displays the PM.J2000J2000NUV=15.28STARDADZNOThis object was generated by the targetselector and retrieved from the SIMBAD database.
SIMBAD listed proper motion for this target. When retrieving targets with PM from SIMBAD, APT requests the coordinates be calculated with an epoch of the year 2000. Do not modify this epoch. Always review coordinates using the Target Confirmation tool, which graphically displays the PM.J2000J2000NUV=15.75STARDBDZNOThis object was generated by the targetselector and retrieved from the SIMBAD database.
SIMBAD listed proper motion for this target. When retrieving targets with PM from SIMBAD, APT requests the coordinates be calculated with an epoch of the year 2000. Do not modify this epoch. Always review coordinates using the Target Confirmation tool, which graphically displays the PM.J2000J2000NUV=16.49STARDBDZNOThis object was generated by the targetselector and retrieved from the SIMBAD database.
SIMBAD listed proper motion for this target. When retrieving targets with PM from SIMBAD, APT requests the coordinates be calculated with an epoch of the year 2000. Do not modify this epoch. Always review coordinates using the Target Confirmation tool, which graphically displays the PM.J2000J2000NUV=16.69STARDBDZNOThis object was generated by the targetselector and retrieved from the SIMBAD database.
SIMBAD listed proper motion for this target. When retrieving targets with PM from SIMBAD, APT requests the coordinates be calculated with an epoch of the year 2000. Do not modify this epoch. Always review coordinates using the Target Confirmation tool, which graphically displays the PM.J2000J2000NUV=16.46STARDBDZNOThis object was generated by the targetselector and retrieved from the SIMBAD database.
SIMBAD listed proper motion for this target. When retrieving targets with PM from SIMBAD, APT requests the coordinates be calculated with an epoch of the year 2000. Do not modify this epoch. Always review coordinates using the Target Confirmation tool, which graphically displays the PM.J2000J2000NUV=15.21COS/NUVSpectroscopicNoNoG185M1921COS/NUVSpectroscopicNoNoG185M1921COS/NUVSpectroscopicNoNoG185M1921COS/NUVSpectroscopicNoNoG185M1921COS/NUVSpectroscopicNoNoG185M1921COS/NUVSpectroscopicNoNoG185M1921COS/NUVSpectroscopicNoNoG185M1921COS/NUVSpectroscopicNoNoG185M1921COS/FUVSpectroscopicNoNoG130M1291COS/FUVSpectroscopicNoNoG130M1291COS/FUVSpectroscopicNoNoG130M1291COS/FUVSpectroscopicNoNoG130M1291The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18098
:visit-id "01"
:proposal-version -1
:trans-version "20250929"
:date "08-Dec-2025 21:11:11.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 2
:saa-model "32"
:si-bright-earth-limb-angle 20.0
:data-volume 382816
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18098
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18098
:visit-id "01"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2801
:al-overhead-at-end 0
:internal-dur-at-end 124
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3181
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18098
:visit-id "01"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2801
:al-overhead-at-end 0
:internal-dur-at-end 358
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3181
:pcs-gap 0
)true20The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18098
:visit-id "02"
:proposal-version -1
:trans-version "20250929"
:date "08-Dec-2025 21:11:12.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 1
:saa-model "32"
:si-bright-earth-limb-angle 20.0
:data-volume 191488
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18098
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18098
:visit-id "02"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2597
:al-overhead-at-end 0
:internal-dur-at-end 386
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2977
:pcs-gap 0
)true10The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18098
:visit-id "03"
:proposal-version -1
:trans-version "20250929"
:date "08-Dec-2025 21:11:12.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 2
:saa-model "32"
:si-bright-earth-limb-angle 20.0
:data-volume 347968
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18098
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18098
:visit-id "03"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2599
:al-overhead-at-end 0
:internal-dur-at-end 114
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2979
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18098
:visit-id "03"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2599
:al-overhead-at-end 0
:internal-dur-at-end 434
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2979
:pcs-gap 0
)true20The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18098
:visit-id "04"
:proposal-version -1
:trans-version "20250929"
:date "08-Dec-2025 21:11:12.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 2
:saa-model "32"
:si-bright-earth-limb-angle 20.0
:data-volume 313184
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18098
:visit-id "04"
:obset-id "04"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18098
:visit-id "04"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2612
:al-overhead-at-end 0
:internal-dur-at-end 105
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2992
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18098
:visit-id "04"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2612
:al-overhead-at-end 0
:internal-dur-at-end 424
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2992
:pcs-gap 0
)true20The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18098
:visit-id "05"
:proposal-version -1
:trans-version "20250929"
:date "08-Dec-2025 21:11:12.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 2
:saa-model "32"
:si-bright-earth-limb-angle 20.0
:data-volume 313184
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18098
:visit-id "05"
:obset-id "05"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18098
:visit-id "05"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2612
:al-overhead-at-end 0
:internal-dur-at-end 105
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2992
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18098
:visit-id "05"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2612
:al-overhead-at-end 0
:internal-dur-at-end 424
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2992
:pcs-gap 0
)true20The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18098
:visit-id "06"
:proposal-version -1
:trans-version "20250929"
:date "08-Dec-2025 21:11:13.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 3
:saa-model "32"
:si-bright-earth-limb-angle 20.0
:data-volume 513248
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18098
:visit-id "06"
:obset-id "06"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18098
:visit-id "06"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2646
:al-overhead-at-end 0
:internal-dur-at-end 105
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3026
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18098
:visit-id "06"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2646
:al-overhead-at-end 0
:internal-dur-at-end 124
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3026
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18098
:visit-id "06"
:orbit-number 3
:pcs-time 380
:si-vis-utilization 2646
:al-overhead-at-end 0
:internal-dur-at-end 358
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3026
:pcs-gap 0
)true30The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18098
:visit-id "07"
:proposal-version -1
:trans-version "20250929"
:date "08-Dec-2025 21:11:13.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 2
:saa-model "32"
:si-bright-earth-limb-angle 20.0
:data-volume 330592
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18098
:visit-id "07"
:obset-id "07"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18098
:visit-id "07"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2599
:al-overhead-at-end 0
:internal-dur-at-end 105
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2979
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18098
:visit-id "07"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2599
:al-overhead-at-end 0
:internal-dur-at-end 434
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2979
:pcs-gap 0
)true20The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18098
:visit-id "08"
:proposal-version -1
:trans-version "20250929"
:date "08-Dec-2025 21:11:13.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 2
:saa-model "32"
:si-bright-earth-limb-angle 20.0
:data-volume 347968
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18098
:visit-id "08"
:obset-id "08"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18098
:visit-id "08"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2607
:al-overhead-at-end 0
:internal-dur-at-end 114
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2987
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18098
:visit-id "08"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2607
:al-overhead-at-end 0
:internal-dur-at-end 434
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2987
:pcs-gap 0
)true20The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18098
:visit-id "09"
:proposal-version -1
:trans-version "20250929"
:date "08-Dec-2025 21:11:13.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 2
:saa-model "32"
:si-bright-earth-limb-angle 20.0
:data-volume 330592
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18098
:visit-id "09"
:obset-id "09"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18098
:visit-id "09"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2594
:al-overhead-at-end 0
:internal-dur-at-end 105
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2974
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18098
:visit-id "09"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2594
:al-overhead-at-end 0
:internal-dur-at-end 434
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2974
:pcs-gap 0
)true20The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18098
:visit-id "10"
:proposal-version -1
:trans-version "20250929"
:date "08-Dec-2025 21:11:14.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 2
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 165504
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18098
:visit-id "10"
:obset-id "10"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18098
:visit-id "10"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2631
:al-overhead-at-end 0
:internal-dur-at-end 2258
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3011
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18098
:visit-id "10"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2631
:al-overhead-at-end 0
:internal-dur-at-end 526
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3011
:pcs-gap 0
)true20The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18098
:visit-id "11"
:proposal-version -1
:trans-version "20250929"
:date "08-Dec-2025 21:11:14.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 2
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 165504
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18098
:visit-id "11"
:obset-id "11"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18098
:visit-id "11"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2631
:al-overhead-at-end 0
:internal-dur-at-end 2258
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3011
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18098
:visit-id "11"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2631
:al-overhead-at-end 0
:internal-dur-at-end 526
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3011
:pcs-gap 0
)true20The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18098
:visit-id "12"
:proposal-version -1
:trans-version "20250929"
:date "08-Dec-2025 21:11:15.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 2
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 165504
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18098
:visit-id "12"
:obset-id "12"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18098
:visit-id "12"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2684
:al-overhead-at-end 0
:internal-dur-at-end 2205
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3064
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18098
:visit-id "12"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2684
:al-overhead-at-end 0
:internal-dur-at-end 526
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3064
:pcs-gap 0
)true20The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18098
:visit-id "13"
:proposal-version -1
:trans-version "20250929"
:date "08-Dec-2025 21:11:15.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 2
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 165504
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18098
:visit-id "13"
:obset-id "13"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18098
:visit-id "13"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2684
:al-overhead-at-end 0
:internal-dur-at-end 2205
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3064
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18098
:visit-id "13"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2684
:al-overhead-at-end 0
:internal-dur-at-end 526
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3064
:pcs-gap 0
)true20The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18098
:visit-id "14"
:proposal-version -1
:trans-version "20250929"
:date "08-Dec-2025 21:11:15.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 3
:saa-model "32"
:si-bright-earth-limb-angle 20.0
:data-volume 217584
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18098
:visit-id "14"
:obset-id "14"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18098
:visit-id "14"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2599
:al-overhead-at-end 0
:internal-dur-at-end 95
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2979
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18098
:visit-id "14"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2599
:al-overhead-at-end 0
:internal-dur-at-end 67
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2979
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18098
:visit-id "14"
:orbit-number 3
:pcs-time 380
:si-vis-utilization 2599
:al-overhead-at-end 0
:internal-dur-at-end 415
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2979
:pcs-gap 0
)true30The scheduling data was generated by CASM 33.1.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18098
:visit-id "15"
:proposal-version -1
:trans-version "20250929"
:date "08-Dec-2025 21:11:16.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 2
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 278592
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18098
:visit-id "15"
:obset-id "15"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18098
:visit-id "15"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 1998
:al-overhead-at-end 0
:internal-dur-at-end 2891
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2976
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18098
:visit-id "15"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 1610
: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 2976
:pcs-gap 0
)true20