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.
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.
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.Final submission, new title, change LP6-658616060Assigned ID: 6983
----- Attempting Submission 1 (Wed Apr 08 21:26:45 GMT 2026) -----
HST Phase I Proposal 6983 successfully submitted.
Receipt: # 6983-1
----- Attempting Submission 2 (Wed Apr 15 21:58:17 GMT 2026) -----
HST Phase I Proposal 6983 successfully submitted.
Receipt: # 6983-2
----- Attempting Submission 3 (Thu Apr 16 15:58:16 GMT 2026) -----
HST Phase I Proposal 6983 successfully submitted.
Receipt: # 6983-3
----- Attempting Submission 4 (Thu Apr 16 17:46:52 GMT 2026) -----
HST Phase I Proposal 6983 successfully submitted.
Receipt: # 6983-4
----- Attempting Submission 5 (Thu Apr 16 20:34:31 GMT 2026) -----According to the July 2025 STAN, all COS160M observations have been moved to LP10. Hence, the warning concerning the choice between LP4 and LP6 seems to be outdated.ORBITAL VISIBILITY OVERRUN
ORBITAL VISIBILITY OVERRUN
ORBITAL VISIBILITY OVERRUN
COORDINATES SHOULD BE IN THE ICRS REFERENCE SYSTEM FOR A SMALL APERTURE
COORDINATES SHOULD BE IN THE ICRS REFERENCE SYSTEM FOR A SMALL APERTURE
COORDINATES SHOULD BE IN THE ICRS REFERENCE SYSTEM FOR A SMALL APERTURE
COORDINATES SHOULD BE IN THE ICRS REFERENCE SYSTEM FOR A SMALL APERTURESecond submission.
Reverted to the usage of COS and STIS for each star as described in Phase I. Spectroscopic coverage and quality (SNR) are good enough. Most warnings are gone, but BOT field warnings persist.1524492374----- Attempting Submission 1 (Fri Aug 07 16:39:37 GMT 2026) -----
HST Phase II Proposal 18428 successfully submitted.
Receipt: # 18428-1
----- Attempting Submission 2 (Mon Aug 17 16:48:44 GMT 2026) -----Second submission for evaluation by the CSThe keys to understanding high-mass stellar evolution: B hypergiants at different metallicitiesMassive stars are luminous, have powerful winds, and die violently as supernovae. Thereby, their individual and collective evolution steers the evolution of galaxies across cosmic time. Yet, post-main-sequence (PMS) evolution, especially of higher-mass stars (M > 30 Msun), is poorly understood. In that regard, B hypergiants (BHGs) may represent a key stage to understand PMS evolution, connecting B supergiants, luminous blue variables, and Wolf-Rayets. Besides being attributed to single stars with higher masses, binary evolution may open additional paths to explain the existence of BHGs. In both cases, strong stellar winds determine not only their spectral morphology but also their fate. Yet, few of them have been sufficiently studied to draw firm conclusions on their nature. An important reason for this is the dearth of good UV coverage for a significant fraction of BHGs, which we address with this proposal. Using the unique COS capabilities, we will uncover the outflows of prototypical BHGs in the Milky Way and Magellanic Clouds. By targeting not only early- and late-type BHGs, but also different metallicities (Z), we will be able to test how wind properties depend on Z. The comparison of the derived atmospheric parameters in the different regimes will allow us to probe connections in massive star evolution, paving the way for anchoring theoretical mass-loss recipes. Moreover, our observations will (i) yield the most overarching multiwavelength study of BHGs, (ii) complete the set of BHGs in the MCs observable in the UV, extending the ULLYSES BHG sample in both the LMC and SMC, and (iii) complement its coverage to Galactic metallicity.We propose to observe 8 BHGs in the Milky Way (MW) and MCs using COS and STIS. For the MW targets, in general, we will use: (i) COS G140L and G230L for an overall coverage with R~3000, comparable to IUE high dispersion spectra (R~5000), more than enough to probe wind features and (ii) G130M[1222], or G160M[1533], or both for higher resolution (R~22000), allowing us to additionally constrain chemical abundances and atmospheric turbulence (e.g., Bouret et al. 2015; Ramachandran et al. 2025). For the MC targets, which are UV brighter due to negligible reddening, we will use STIS E140M[1425], and E230M[1978/2707] with standard 02x02 aperture (except for the bright Sk -67 -17) for FUV and NUV coverage with higher resolution (R~30000). STIS will also be used, instead of lower resolution COS, for the brightest MW target HD50064. Conversely, COS G130M and G160M will be used for AzV 475 due to its combination of cooler temperature but high UV flux. Thereby, these settings will cover essentially all the relevant wind diagnostics along the mid/late B-type domain (e.g., N V, C II, Si IV, Al III, Mg II).
In total, we require 18 orbits, taking into account overhead times and the new COS Lifetime Position protection policy (we use less than 1% of the pixels' lifetime). Our observations will be performed in TIME-TAG mode. Whenever possible, we will use all four FP-POS positions for each target to enhance the lifetime of the detector.The proposing team consists of established researchers and PhD students.
A. Sander, V. Ramaschandran, L. Oskinova, D. Pauli, O. G. Telford, and W-R. Hamann all have experience with quantitative spectroscopy including HST UV data.
W-R. Hamann, L. Oskinova, A. Sander, V. Ramaschandran, D. Pauli, H. Todt, R. Hainich, R. Lefever, E. C. Schoesser, J. Josiek, S. Reyero Serantes, and M. Bernini Peron have detailed experience with non-LTE atmosphere modelling. T. Parsons have experience in modelling UV spectra using the SEI method. G. Gonzalez-Tora is an expert in spectral modeling of massive stars across all evolutionary phases. A. Sundar Samantaray is speciallist in investigating stellar populations and analyzing hot stars with rotation.
A. Sander, H. Todt, and W.-R. Hamann are the lead developers of PoWR, a state-of-the-art non-LTE stellar atmosphere code, especially designed to cope with radiatively-driven winds of hot stars. Moreover, D. Pauli, V. Ramachandran, and M. Bernini Peron have experience in modelling the evolution of massive stars with the publicly available MESA code, and J. Josiek has experience within the same field but with GENEC.Stellar Physics and Stellar Types6falsetruefalsefalsefalsefalsefalseSUPPORTEDSTARB0-B2 III-IB3-B5 III-INOThis 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.J2000J2000STARB6-B9.5 III-INOThis 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.J2000J2000STARB6-B9.5 III-INOThis 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.J2000J2000STARB6-B9.5 III-INOThis 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.This 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.J2000J2000STARB6-B9.5 III-ILUMINOUS BLUE VARIABLENOThis 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.J2000J2000STARA0-A3 III-INOThis 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.J2000J2000STARB0-B2 III-INOThis 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.J2000J2000STARB0-B2 III-INOThis 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.J2000J2000COS/FUVSpectroscopicNoNoG140L1105COS/NUVSpectroscopicNoNoG230L2950COS/FUVSpectroscopicNoNoG160M1533COS/FUVSpectroscopicNoNoG140L1105COS/NUVSpectroscopicNoNoG230L2950COS/FUVSpectroscopicNoNoG160M1533COS/FUVSpectroscopicNoNoG140L1105COS/NUVSpectroscopicNoNoG230L2950COS/FUVSpectroscopicNoNoG140L1280COS/NUVSpectroscopicNoNoG230L2635COS/NUVSpectroscopicNoNoG230L3000COS/NUVSpectroscopicNoNoG230L3360COS/FUVSpectroscopicNoNoG140L1105COS/FUVSpectroscopicNoNoG160M1533STIS/NUV-MAMASpectroscopicNoNoE230M2707COS/FUVSpectroscopicNoNoG130M1222COS/FUVSpectroscopicNoNoG160M1533STIS/NUV-MAMASpectroscopicNoNoE230M2707COS/FUVSpectroscopicNoNoG130M1222COS/FUVSpectroscopicNoNoG160M1533STIS/NUV-MAMASpectroscopicNoNoE230M1978STIS/NUV-MAMASpectroscopicNoNoE230M2707STIS/FUV-MAMASpectroscopicNoNoE140M1425STIS/NUV-MAMASpectroscopicNoNoE230M1978STIS/NUV-MAMASpectroscopicNoNoE230M2707STIS/FUV-MAMASpectroscopicNoNoE140M1425STIS/NUV-MAMASpectroscopicNoNoE230M1978STIS/NUV-MAMASpectroscopicNoNoE230M2707The scheduling data was generated by CASM 34.2.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18428
:visit-id "01"
:proposal-version -1
:trans-version "20260618"
:date "07-Aug-2026 18:00:34.0"
:trans-errors '(:WARNINGS 1 :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 226624
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18428
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18428
:visit-id "01"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2671
:al-overhead-at-end 0
:internal-dur-at-end 353
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3011
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18428
:visit-id "01"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2409
:al-overhead-at-end 0
:internal-dur-at-end 347
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3011
:pcs-gap 0
)true21Not sure about the LP/System/Volumes/Data/solaris/user1/sherwin/18428/OP-cache/18428-v02.xmlThe scheduling data was generated by CASM 34.2.CASM was run in Phase II mode.orbit numbers added to get around COS timing change. Orbits 2-3 should NOT be filled.(Tic-Visit
:proposal-id 18428
:visit-id "02"
:proposal-version -1
:trans-version "20260618"
:date "28-Aug-2026 09:04:25.0"
:trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 3
:saa-model "31"
:si-bright-earth-limb-angle 20.0
:data-volume 539904
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18428
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18428
:visit-id "02"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2641
:al-overhead-at-end 0
:internal-dur-at-end 382
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2976
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18428
:visit-id "02"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 771
:al-overhead-at-end 0
:internal-dur-at-end 4092
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2976
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18428
:visit-id "02"
:orbit-number 3
:pcs-time 380
:si-vis-utilization 1471
:al-overhead-at-end 0
:internal-dur-at-end 347
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2976
:pcs-gap 0
)true31The scheduling data was generated by CASM 34.2.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18428
:visit-id "03"
:proposal-version -1
:trans-version "20260618"
:date "07-Aug-2026 18:00:35.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 191808
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18428
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18428
:visit-id "03"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2589
:al-overhead-at-end 0
:internal-dur-at-end 353
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2976
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18428
:visit-id "03"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2439
:al-overhead-at-end 0
:internal-dur-at-end 357
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2976
:pcs-gap 0
)true20Not sure about the LPThe scheduling data was generated by CASM 34.2.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18428
:visit-id "04"
:proposal-version -1
:trans-version "20260618"
:date "17-Aug-2026 18:30:20.0"
:trans-errors '(:WARNINGS 1 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 3
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 174768
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18428
:visit-id "04"
:obset-id "04"
:pcs-mode "FGS"
)
(Tic-Obset
:proposal-id 18428
:visit-id "04"
:obset-id "A4"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18428
:visit-id "04"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2592
:al-overhead-at-end 0
:internal-dur-at-end 353
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2976
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18428
:visit-id "04"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2609
:al-overhead-at-end 0
:internal-dur-at-end 347
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2976
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18428
:visit-id "04"
:orbit-number 3
:pcs-time 380
:si-vis-utilization 2523
:al-overhead-at-end 0
:internal-dur-at-end 394
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2976
:pcs-gap 0
)true31Not sure about STIS TA Filter slitThe scheduling data was generated by CASM 34.2.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18428
:visit-id "09"
:proposal-version -1
:trans-version "20260618"
:date "17-Aug-2026 18:04:35.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 2
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 401040
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18428
:visit-id "09"
:obset-id "09"
:pcs-mode "FGS"
)
(Tic-Obset
:proposal-id 18428
:visit-id "09"
:obset-id "A9"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18428
:visit-id "09"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2728
:al-overhead-at-end 0
:internal-dur-at-end 347
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3121
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18428
:visit-id "09"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2634
:al-overhead-at-end 0
:internal-dur-at-end 394
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3121
:pcs-gap 0
)true20Not sure about STIS TA Filter slit/System/Volumes/Data/solaris/user1/sherwin/18428/OP-cache/18428-v10.xmlThe scheduling data was generated by CASM 34.2.CASM was run in Phase II mode.orbit numbers added to get around COS timing change. Orbits 2-3 should NOT be filled.(Tic-Visit
:proposal-id 18428
:visit-id "10"
:proposal-version -1
:trans-version "20260618"
:date "28-Aug-2026 09:05:27.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 3
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 435792
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18428
:visit-id "10"
:obset-id "10"
:pcs-mode "FGS"
)
(Tic-Obset
:proposal-id 18428
:visit-id "10"
:obset-id "A0"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18428
:visit-id "10"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2599
:al-overhead-at-end 0
:internal-dur-at-end 394
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2979
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18428
:visit-id "10"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 1058
:al-overhead-at-end 0
:internal-dur-at-end 3805
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 2979
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18428
:visit-id "10"
:orbit-number 3
:pcs-time 380
:si-vis-utilization 1151
:al-overhead-at-end 0
:internal-dur-at-end 347
: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 34.2.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18428
:visit-id "07"
:proposal-version -1
:trans-version "20260618"
:date "07-Aug-2026 17:32:20.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 2
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 278864
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18428
:visit-id "07"
:obset-id "07"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18428
:visit-id "07"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2684
:al-overhead-at-end 0
:internal-dur-at-end 0
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3092
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18428
:visit-id "07"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2530
:al-overhead-at-end 194
:internal-dur-at-end 319
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3092
:pcs-gap 0
)true20Not sure about STIS TA Filter slitThe scheduling data was generated by CASM 34.2.CASM was run in Phase II mode.(Tic-Visit
:proposal-id 18428
:visit-id "08"
:proposal-version -1
:trans-version "20260618"
:date "07-Aug-2026 17:43:46.0"
:trans-errors '(:WARNINGS 4 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 2
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 278864
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 18428
:visit-id "08"
:obset-id "08"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 18428
:visit-id "08"
:orbit-number 1
:pcs-time 380
:si-vis-utilization 2648
:al-overhead-at-end 0
:internal-dur-at-end 113
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3092
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 18428
:visit-id "08"
:orbit-number 2
:pcs-time 380
:si-vis-utilization 2630
:al-overhead-at-end 194
:internal-dur-at-end 319
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3092
:pcs-gap 0
)true20