The First Early FUV Observations of a Type IIP Supernova

0 Assigned ID: 3744 ----- Attempting Submission 1 (Fri Mar 25 23:48:14 GMT 2022) ----- adding faint SN visit 5 -1081525562 ----- Attempting Submission 1 (Thu Jul 14 01:09:27 GMT 2022) ----- HST Phase II Proposal 17132 successfully submitted. Receipt: # 17132-1 ----- Attempting Submission 2 (Thu Jul 14 16:22:37 GMT 2022) ----- ----- Attempting Submission 3 (Thu Oct 13 17:11:43 GMT 2022) ----- HST Phase II Proposal 17132 successfully submitted. Receipt: # 17132-3 ----- Attempting Submission 4 (Tue Dec 06 11:25:30 GMT 2022) ----- ----- Attempting Submission 5 (Wed Dec 07 23:37:33 GMT 2022) ----- ----- Attempting Submission 7 (Wed Dec 14 05:48:17 GMT 2022) ----- I've run all of these on the faint SN visits which I plan on activating for AT2022acko The First Early FUV Observations of a Type IIP Supernova Early, ultraviolet (UV) observations of hydrogen rich Type IIP/L core-collapse supernovae (CCSNe) are critical for understanding the connection between massive red supergiant (RSG) stars, their mass loss, and the subsequent SN explosion. During the RSG phase, a significant amount of mass loss occurs, and depending on the duration can surround the star with dense and extended circumstellar material (CSM). When the star eventually explodes as a CCSN, high energy photons from the shock breakout ionizes the CSM. These ionization features can be used to constrain the properties of the CSM, including metallicity density, and structure, mapping the evolution of the final years of life of the progenitor star. UV observations during the first two weeks after explosion are crucial for detecting these high ionization lines, and are the most sensitive to lower densities and weaker CSM interactions which may occur in lower mass RSG progenitors. The dearth of UV (particularly FUV) observations of Type IIP/L SNe at this phase has left many open-ended questions about the role CSM interaction plays in "normal" Type II SNe, and a disruptive ToO with HST in the UV is crucial to obtaining these important data on a very short timescale. This proposal will be triggered on a very young type II supernova to obtain UV spectroscopy as close to the trigger time as possible. We will work closely with our contact scientist to ensure the safety of the detectors and with our program coordinator to ensure schedulability. Once triggered, the SN will be observed daily for 3 days and then once one week after the last observation. Each visit will consist of a STIS FUV-MAMA G140L observation with the 52x0.2" slit and a STIS NUV-MAMA G230L observation with the 52x0.2" slit I have created a complete set of visits for 3 scenarios: The supernova is faint at first observation (r~17mag rising to 15mag for last visit) The supernova is bright at first observation (r~14mag rising to 12mag for last visit) The supernova is on a bright background or has a nearby source an requires an offset for the TA (r~17mag rising to 15mag for last visit) Each of these scenarios has the same exposure time per observation K. A. Bostroem extensive experience with the STIS data reduction and the reduction and analysis of core collapse supernovae observations with Swift and Gemini. Her research focuses on understanding the progenitors of hydrogen-rich CC SNe. M. Lundquist is an active member of the DLT40 team and specializes in the reduction and analysis of Gemini and TESS observations supplementary to this proposal. He is currently a staff astronomer at the W. M. Keck Observatory. Prior to joining the DLT40 team, he worked as a Gemini Science Fellow at the Gemini Observatories. S. Valenti is the PI of our HST Cycle 28 and 29 program. He is the co-PI of DLT40. He has worked comprehensively on core collapse supernovae (CC SNe). D. Sand is the co-PI of the DLT40 survey and an expert in the progenitors of Type Ia SNe and SN environments. He has extensive experience with Swift, and Gemini observations of SNe and their environments. J. Andrews is an active member of the DLT40 team, has expertise observing with HST/STIS, and is an assistent astronomer the Gemini Observatory. Her research focuses on characterizing the progenitors of core collapse (CC) SNe, specifically focusing on their mass-loss history via circumstellar interaction. G. Hosseinzadeh is an expert in early SN~Ia light curves and has experience analyzing early UV data. J. Jencson is an active member of the DLT40 team and has extensive experience in reducing an analyzing Swift observations of transients. His research focuses on multi-wavelength studies of hydrogen-rich transients and searches for dust-obscured transients and faint/failed SNe. J. Pearson is focusing her thesis research on understanding the progenitors and environments of CC SNe and is an active member of the DLT40 team. S. Wyatt is an active member of the DLT40 team and has extensive experience in studying the diversity of SN~Ia and their progenitor systems. Y. Dong is an active member of the DLT40 team and is the PI of our Swift program and has experience analyzing both CC~SNe and SN~I. N. Meza is the newest member of the DLT40 team focusing his thesis work on CC~SNe. Stellar Physics and Stellar Types 6 false false true false false false false SUPPORTED EXT-STAR SUPERNOVA TYPE II NO J2000 J2000 EXT-STAR SUPERNOVA TYPE II NO J2000 EXT-STAR SUPERNOVA TYPE II NO J2000 J2000 EXT-STAR SUPERNOVA TYPE II DLT40 discovery. ATLAS non-detections < 24 hours prior to discovery J2000 STIS/FUV-MAMA Spectroscopic No No G140L 1425 STIS/NUV-MAMA Spectroscopic No No G230L 2376 STIS/FUV-MAMA Spectroscopic No No G140L 1425 STIS/NUV-MAMA Spectroscopic No No G230L 2376 STIS/FUV-MAMA Spectroscopic No No G140L 1425 STIS/NUV-MAMA Spectroscopic No No G230L 2376 STIS/FUV-MAMA Spectroscopic No No G140L 1425 STIS/NUV-MAMA Spectroscopic No No G230L 2376 1670325676747 The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. First epoch should be executed as soon as possible after trigger For SN with initial brightness around r=17 mag 1670660943000 33.209346853490814 (Tic-Visit :proposal-id 17132 :visit-id "01" :proposal-version -1 :trans-version "20220630" :date "06-Dec-2022 04:21:16.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 261408 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17132 :visit-id "01" :obset-id "01" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17132 :visit-id "01" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2739 :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 3156 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17132 :visit-id "01" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2749 :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 3156 :pcs-gap 0 ) true 2 0 Waiting for a suitable supernova to explode. I understand this response time is likely a lower limit on what STScI is capable of but the sooner the better for this program 1670325639271 The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. Second epoch should be executed 24 hours after first visit For SN with initial brightness around r=17 mag If possible execute at same orientation as visit 1 1670729479000 33.85536533551749 (Tic-Visit :proposal-id 17132 :visit-id "02" :proposal-version -1 :trans-version "20220630" :date "06-Dec-2022 04:20:38.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 261408 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17132 :visit-id "02" :obset-id "02" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17132 :visit-id "02" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2739 :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 3156 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17132 :visit-id "02" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2749 :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 3156 :pcs-gap 0 ) true 2 0 Waiting for a suitable supernova to explode. I understand this response time is likely a lower limit on what STScI is capable of but the sooner the better for this program Will be triggered at same time as visit 1 1670456077786 The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. Third epoch should be executed 24 hours after second visit and 48 hours after first visit For SN with initial brightness around r=17 mag If possible execute at same orientation as visit 1 1670843706000 33.8553540300409 (Tic-Visit :proposal-id 17132 :visit-id "03" :proposal-version -1 :trans-version "20220630" :date "07-Dec-2022 16:34:37.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 174416 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17132 :visit-id "03" :obset-id "03" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17132 :visit-id "03" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2757 :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 3156 :pcs-gap 0 ) true 1 0 Waiting for a suitable supernova to explode. I understand this response time is likely a lower limit on what STScI is capable of but the sooner the better for this program Will be triggered at same time as visit 1 BOP Warning for irregularly-variable source. This isn't irregularly variable so shouldn't be an issue 1670996256515 The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. /private/var/folders/cc/mq9wmn5j0ys2frsvjcw4m4hw0000gn/T/OPVisit12659842690026892444.xml fourth epoch should be executed 7 days after third visit For SN with initial brightness around r=17 mag If possible execute at same orientation as visit 1 1671843222000 53.324278715729605 (Tic-Visit :proposal-id 17132 :visit-id "04" :proposal-version -1 :trans-version "20220630" :date "13-Dec-2022 22:37:36.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 330992 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17132 :visit-id "04" :obset-id "04" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17132 :visit-id "04" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2760 :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 3156 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17132 :visit-id "04" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2764 :al-overhead-at-end 85 :internal-dur-at-end 132 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3156 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17132 :visit-id "04" :orbit-number 3 :pcs-time 392 :si-vis-utilization 2764 :al-overhead-at-end 0 :internal-dur-at-end 375 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3156 :pcs-gap 0 ) true 3 0 Waiting for a suitable supernova to explode. I understand this response time is likely a lower limit on what STScI is capable of but the sooner the better for this program Will be triggered at same time as visit 1 1670996577625 The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. /private/var/folders/cc/mq9wmn5j0ys2frsvjcw4m4hw0000gn/T/OPVisit16108171428630568780.xml visit 5 should be scheduled as soon as possible, regardless of when visit 4 executes (Tic-Visit :proposal-id 17132 :visit-id "13" :proposal-version -1 :trans-version "20220630" :date "13-Dec-2022 22:42:57.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 87408 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17132 :visit-id "13" :obset-id "13" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17132 :visit-id "13" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2763 :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 3156 :pcs-gap 0 ) true 1 0 Waiting for a suitable supernova to explode. I understand this response time is likely a lower limit on what STScI is capable of but the sooner the better for this program Will be triggered at same time as visit 1 1665679106744 The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. First epoch should be executed as soon as possible after trigger For supernova with initial mag around r=14mag (Tic-Visit :proposal-id 17132 :visit-id "05" :proposal-version -1 :trans-version "20220630" :date "13-Oct-2022 09:38:26.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 261408 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17132 :visit-id "05" :obset-id "05" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17132 :visit-id "05" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2739 :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 3142 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17132 :visit-id "05" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2749 :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 3142 :pcs-gap 0 ) false 2 0 Waiting for a suitable supernova to explode. I understand this response time is likely a lower limit on what STScI is capable of but the sooner the better for this program 1665679107543 The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. Second epoch should be executed 24 hours after first visit For SN with initial brightness around r=14 mag If possible execute at same orientation as visit 1 (Tic-Visit :proposal-id 17132 :visit-id "06" :proposal-version -1 :trans-version "20220630" :date "13-Oct-2022 09:38:27.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 261408 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17132 :visit-id "06" :obset-id "06" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17132 :visit-id "06" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2739 :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 3142 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17132 :visit-id "06" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2749 :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 3142 :pcs-gap 0 ) false 2 0 Waiting for a suitable supernova to explode. I understand this response time is likely a lower limit on what STScI is capable of but the sooner the better for this program Will be triggered at same time as visit 1 1665679108158 The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. Third epoch should be executed 24 hours after second visit and 48 hours after first visit For SN with initial brightness around r=14 mag If possible execute at same orientation as visit 1 (Tic-Visit :proposal-id 17132 :visit-id "07" :proposal-version -1 :trans-version "20220630" :date "13-Oct-2022 09:38:27.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 174416 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17132 :visit-id "07" :obset-id "07" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17132 :visit-id "07" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2749 :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 3142 :pcs-gap 0 ) false 1 0 Waiting for a suitable supernova to explode. I understand this response time is likely a lower limit on what STScI is capable of but the sooner the better for this program Will be triggered at same time as visit 1 1665679109143 The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. fourth epoch should be executed 7 days after third visit For SN with initial brightness around r=14 mag If possible execute at same orientation as visit 1 (Tic-Visit :proposal-id 17132 :visit-id "08" :proposal-version -1 :trans-version "20220630" :date "13-Oct-2022 09:38:28.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 330992 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17132 :visit-id "08" :obset-id "08" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17132 :visit-id "08" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2748 :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 3142 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17132 :visit-id "08" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2748 :al-overhead-at-end 85 :internal-dur-at-end 132 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3142 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17132 :visit-id "08" :orbit-number 3 :pcs-time 392 :si-vis-utilization 2750 :al-overhead-at-end 0 :internal-dur-at-end 375 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3142 :pcs-gap 0 ) false 3 0 Waiting for a suitable supernova to explode. I understand this response time is likely a lower limit on what STScI is capable of but the sooner the better for this program Will be triggered at same time as visit 1 1665679109979 The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. First epoch should be executed as soon as possible after trigger For SN with initial brightness around r=17 mag that requires acquisition on an offset star either due to high background or a nearby bright source (Tic-Visit :proposal-id 17132 :visit-id "09" :proposal-version -1 :trans-version "20220630" :date "13-Oct-2022 09:38:29.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 261408 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17132 :visit-id "09" :obset-id "09" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17132 :visit-id "09" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2739 :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 3142 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17132 :visit-id "09" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2749 :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 3142 :pcs-gap 0 ) false 2 0 Waiting for a suitable supernova to explode. I understand this response time is likely a lower limit on what STScI is capable of but the sooner the better for this program 1665679110813 The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. Second epoch should be executed 24 hours after first visit For SN with initial brightness around r=17 mag that requires acquisition on an offset star either due to high background or a nearby bright source If possible execute at same orientation as visit 1 (Tic-Visit :proposal-id 17132 :visit-id "10" :proposal-version -1 :trans-version "20220630" :date "13-Oct-2022 09:38:30.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 261408 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17132 :visit-id "10" :obset-id "10" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17132 :visit-id "10" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2739 :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 3142 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17132 :visit-id "10" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2749 :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 3142 :pcs-gap 0 ) false 2 0 Waiting for a suitable supernova to explode. I understand this response time is likely a lower limit on what STScI is capable of but the sooner the better for this program Will be triggered at same time as visit 1 1665679111431 The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. Third epoch should be executed 24 hours after second visit and 48 hours after first visit For SN with initial brightness around r=17 mag that requires acquisition on an offset star either due to high background or a nearby bright source If possible execute at same orientation as visit 1 (Tic-Visit :proposal-id 17132 :visit-id "11" :proposal-version -1 :trans-version "20220630" :date "13-Oct-2022 09:38:31.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 174416 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17132 :visit-id "11" :obset-id "11" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17132 :visit-id "11" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2749 :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 3142 :pcs-gap 0 ) false 1 0 Waiting for a suitable supernova to explode. I understand this response time is likely a lower limit on what STScI is capable of but the sooner the better for this program Will be triggered at same time as visit 1 1665679112395 The scheduling data was generated by CASM 30.3. CASM was run in Phase II mode. fourth epoch should be executed 7 days after third visit For SN with initial brightness around r=17 mag that requires acquisition on an offset star either due to high background or a nearby bright source If possible execute at same orientation as visit 1 (Tic-Visit :proposal-id 17132 :visit-id "12" :proposal-version -1 :trans-version "20220630" :date "13-Oct-2022 09:38:32.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 330992 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17132 :visit-id "12" :obset-id "12" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17132 :visit-id "12" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2748 :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 3142 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17132 :visit-id "12" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2748 :al-overhead-at-end 85 :internal-dur-at-end 132 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3142 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17132 :visit-id "12" :orbit-number 3 :pcs-time 392 :si-vis-utilization 2750 :al-overhead-at-end 0 :internal-dur-at-end 375 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3142 :pcs-gap 0 ) false 3 0 Waiting for a suitable supernova to explode. I understand this response time is likely a lower limit on what STScI is capable of but the sooner the better for this program Will be triggered at same time as visit 1