0 Assigned ID: 4625 ----- Attempting Submission 1 (Wed May 24 20:45:28 GMT 2023) ----- HST Phase I Proposal 4625 successfully submitted. Receipt: # 4625-1 ----- Attempting Submission 2 (Wed May 24 21:45:12 GMT 2023) ----- This is a resubmission of the Phase 2 file for 17464. I downloaded the Phase 2 .apt file with Bill Januszewski's changes (https://www.stsci.edu/hst/observing/program-information?id=17464&observatory=HST&pi=1), and I edited CR Dra so that it is no longer listed as an extended target (per email communication with Leonardo Dos Santos, Dec 2023). -1873344134 ----- Attempting Submission 1 (Tue Sep 12 19:09:06 GMT 2023) ----- ----- Attempting Submission 2 (Mon Dec 18 20:24:33 GMT 2023) ----- Stellar flares are the most dramatic examples of energy release that non-degenerate stars undergo while on the main sequence. In our search for habitable zone planets around M dwarf stars, characterizing the flare activity of M dwarfs is a key ingredient to understanding the impact the star can have on its near stellar environment. Recent results have also demonstrated that particle acceleration in the stellar atmosphere plays a crucial role in the shape and amount of UV and optical radiation released during M dwarf flares. The NUV range is unequivocally a "fulcrum'' between the optical and shorter wavelength FUV continua but has been woefully undersampled in observations. We propose a HST Treasury program to characterize the NUV continuum and emission lines in M dwarf stellar flares. Only HST can empirically constrain the spectral peak and slope in the NUV and thus physically explain the origin of the flare in the low stellar atmosphere through the heating by accelerated particles. Our strategy spans a 4.5x greater spectral range in the NUV than previous studies and will provide flux-calibrated, time-resolved flare spectra just below the atmospheric cutoff (lam < 3200 A). The flare and quiescent data will have broad legacy value for characterizing the high-energy radiation environment of exoplanets, comparing to IRIS data of solar flares, and interpreting archival broadband NUV photometry of magnetically active stars. The science products -- time-resolved NUV spectra along with best-fit models to the NUV spectra calculated on a wider wavelength range from FUV through red-optical wavelengths -- will also benefit multiple communities. The immediate goal is to provide a comprehensive empirical survey of the NUV continuum and line radiation in several moderate-to-large stellar flares from CR Dra and GJ 1243 (M4Ve). Both stars have high and well-quantified flare rates from Kepler and TESS. CR Dra is a non-interacting, spectroscopic M-dwarf binary, and GJ 1243 has been observed by COS before (HST GO 13323; G230L, lam_c = 2650) for eight contiguous orbits in one visit. The proposed program will use the G230L grating (central wavelength 2950 Ang) of HST/COS in Time-Tag mode. The present strategy with COS will provide new information on the 1650-2050Ang to 2750-3150A continuum ratios in these flares and direct comparisons among flares. We will measure continuum slopes within each Stripe, between the two Stripes, as well as Mg II h and k wavelength-integrated line fluxes as a function of time. So, we will need absolute flux calibration. The GOS G230L spectra from GO 13323 resulted in a S/N per resel of ~3 in a time-tag 60s extraction. These data allowed characterization of the flare continuum level and slope to a S/N >= 20 in each of four \Delta lambda = 25-50Ang wide continuum windows. Visits of eight contiguous orbits are preferred to maximize on-star flare monitoring and to capture the full evolution of the flares (which can last for several hours). Because one of the targets (GJ 1243) is very faint in quiescence in the NUV, up to 85% of an orbit per visit is required for target acquisition. The previous HST/GO 13323 observations have demonstrated the feasibility for scheduling eight-orbit visits. For GJ 1243 (56 orbits, U=15.5, V = 12.8, M4 star), we use the strategy employed in HST GO 13323 (same grating, different wavelength center) for target acquisition (PEAKXD + PEAKD) and target acquisition exposure times. For CR Dra (32 orbits, U=12.0, V=9.5, M1 spec binary), we use the same target acquisition strategy as GJ 1243, but we scale the exposure times of the target acquisition by the U-band magnitude difference. We were awarded TESS observations at 20s cadence for these two targets. We do not know the TESS allocation yet for CR Dra, but GJ 1243 will be definitely observed in all sectors (through a separate TESS GO program). We have limited our "Between" windows for the visits to the dates with TESS Cycle 6 observations of each target: [GJ1243] Sector 74: 01/04/2024 - 01/29/2024 Sector 75: 01/31/2024 - 02/25/2024 Sector 81: 07/16/2024 - 08/09/2024 Sector 82: 08/11/2024 - 09/04/2024 [CR Dra] Sector 76: 02/27/2024 - 03/25/2024 Sector 77: 03/27/2024 - 04/22/2024 Sector 78: 04/24/2024 - 05/20/2024 Sector 79: 05/22/2024 - 06/17/2024 Where we have avoided the first and last date of each sector due to issues/artifacts associated with data downlink on these days. If the visits are not able to be scheduled within the TESS visibility windows in Cycle 6, then the preference is to schedule them at any time throughout Cycle 31, rather than forego any HST observations (e.g., the Visit Planner suggests that there is HST visibility in September 2024 for both targets). We are open to a discussion with the planners if 8 visits x 7 orbits (for GJ 1243) and 4 visits x 7 orbits + 1 visit x 4 orbits (for CR Dra) give better planning capabilities. Dr. Antigona Segura is an expert in astrobiology and pre-biotic chemistry in M dwarf systems. She has extensive experience in bridging flare and quiescent NUV observations with models of exoplanets using the Virtual Planetary Laboratory. Dr. Rachel Osten is an expert in multi-wavelength properties of M-dwarf and active-binary stellar flares, from the X-ray to the radio, including spectral modeling, energy partitions, and properties of accelerated particles. Clara Brasseur is an expert in mining and interpretation of multi-wavelength datasets of flares of all spectral types and in particular the optical and NUV connection. Isaiah Tristan is an expert in the multi-wavelength phenomena in M dwarf flares and flare rates from TESS, and he has expertise in analyzing flare simulations from the RADYN, RH, Gyrort, and FP codes. Dr. Yuta Notsu is an expert in ground-based spectral observations of M dwarf flares, stellar eruptions, and superflaring G dwarf stars. Dr. Adam Kowalski is a co-developer of the RADYN flare code and has expertise in NUV and optical spectral observations of solar and M-dwarf flares. Stellar Physics and Stellar Types Exoplanets and Exoplanet Formation 0 false false true true false false false true PRIMARY 2 true SUPPORTED STAR M V-IV NO CR Dra is a spectroscopic binary with a combined spectral type of M1. The angular separation of the two components varies between 0.06 - 0.16 arcsec, with a period of 4.05 years (Tamazian et al 2008 AJ 136, 974; note their Table 3 erroneously lists the units of angular separation in this table as milli-arcsec). The angular separation will be closer to its maximum (~0.16 arcsec) on the epoch of the HST observations (but also note that the orbital properties from astrometry conflict with those from spectroscopic lines -- Sperauskas et al. 2019 A&A), and so we have flagged this target as an extended source. According to the Tamazian et al photometry, the magnitude differences of the two components in this binary are ~ 1.8 mags in V; the differences in the NUV will be larger. Thus we don't know exactly how the TA algorithm will fare with this combined PSF shape. No Swift/UVOT images of CR Dra are available in the MAST archive for checking the relative fluxes in the NUV. We obtained J2000 ICRS coordinates from SIMBAD, which are corrected from the epoch=2016 Gaia DR3 coordinates by accounting for proper motion (corrections automatically by Simbad, which we verified). Half of the annual parallax is 25 mas. However, due the binarity, the sources could be separated from our coordinates by ~0.16 arcsec, which we assign as our uncertainty in RA and Dec. (the standard errors in RA and Dec, from Gaia DR3, are 0.40 mas and 0.42 mas, respectively; these are larger positional uncertainties than for the fainter target, GJ 1243, which might reflect that the double-source is slightly extended in Gaia). The target has a significant proper motion and we provide these values (from Gaia) in the fields. We note that the Proper Motion RA given in the field above is the value given by Simbad (ie, PM RA = 0.0879699 arcsec / year = cos(dec) * mu_RA) and the Gaia DR3 archive. (The standard errors in PM RA and PM Dec are 0.60 mas / year and 0.54 mas / year respectively, which result in a much smaller uncertainty in position by propagating these PM errors from 2016 to 2024). G202-36 GAIADR31429437378934511616 J2000 J2000 U=12.0 STAR M V-IV NO We obtained J2000 ICRS coordinates from SIMBAD, which are corrected from the epoch=2016 Gaia DR3 coordinates by accounting for proper motion (corrections automatically by Simbad, which we confirmed). We take the uncertainty in RA and Dec (from Gaia) to be 1/2 of the annual parallax = 40 mas -- this is to ensure that it is less than 0.4arcsec required by our target acquisition algorithm. (the standard errors in RA and Dec, from Gaia DR3 are 0.015 mas and 0.017 mas, respectively). The target has a significant proper motion and we provide these values (from Gaia). We note that the Proper Motion RA given in the field above is the value given by Simbad (ie, PM RA = 0.183242 arcsec / year = cos(dec) * mu_RA) and the Gaia DR3 archive. (The standard errors in PM RA and PM Dec are 0.02 mas / year and 0.02 mas / year, respectively). G208-42 GAIADR32080285727861817088 J2000 J2000 U=15.5, lam=2440-2840A flux = 7.5e-16 erg/s/cm2/Ang in quiescence COS/NUV Spectroscopic No No G230L 2950 COS/NUV Spectroscopic No No G230L 2950 1702930545922 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. First visit of GJ 1243. A non-flaring spectrum of GJ 1243 from 1100-9000 Ang was constructed for the TA calculation: FUV and NUV spectra of AD Leo (a dM3e star; Hawley & Pettersen 1991) scaled to the magnitude of GJ 1243 combined with an optical spectrum of GJ 1243 (Kowalski et al. 2013 ApJS). We used SWIFT/UVOT images of GJ1243 in the UVW1 and UVM2 filters (archive.stsci.edu) to refine the quiescent UV flux. (Tic-Visit :proposal-id 17464 :visit-id "01" :proposal-version -1 :trans-version "20230626" :date "18-Dec-2023 15:15:44.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 7 :saa-model "32" :si-bright-earth-limb-angle 20.0 :data-volume 10036336 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17464 :visit-id "01" :obset-id "01" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17464 :visit-id "01" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2477 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "01" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "01" :orbit-number 3 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "01" :orbit-number 4 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "01" :orbit-number 5 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "01" :orbit-number 6 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "01" :orbit-number 7 :pcs-time 392 :si-vis-utilization 2528 :al-overhead-at-end 0 :internal-dur-at-end 417 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2920 :pcs-gap 0 ) true 7 0 Because the target is intrinsically very faint in the UV during quiescence, a large fraction of the first orbit of each visit must be used for target acquistion. We have scheduled a TA algorithm of ACQ/PEAKXD (300s) +ACQ/PEAKD (300s), which give the best S/N ~ 27 and 32, respectively, for a dwell time of 300 seconds for the spectrum of GJ 1243 scaled to U=15.5. In HST GO 13323 (Sept 2014), we calculated a S/N of 40 for this quiescent spectrum of GJ 1243 (COS.sa.519303), and this TA algorithm apparently worked well then. There is no major change in sensitivity between 2014 and 2024: https://www.stsci.edu/hst/instrumentation/cos/performance/sensitivity Note, two 3x3 ACQ/SEARCH algorithms only allow for shorter exposure times but this takes up an entire orbit. The COS/G230L wavelength position of 3360 gives better S/N (compared to the wavelength position of the science exposures with COS wavelength position 2950) during quiescence because it samples the redder/brighter part of the quiescent continuum. Note that we have conservatively estimated the UV flux of GJ 1243 and any small flares will only increase the S/N for each TA exposure. We performed an ETC simulation with a conservatively large flare (\Delta u = 4.7 mag; see comments for Orb2-Science Exposure 1) for the 3360 grating and the local+global count rate limits are not exceeded. The buffer time from the ETC (COS.sa.519401) is 200 seconds (2/3 x buffer time is 130 sec), which is less than the exposure time. This would result in the loss of data during the acquisition but the S/N would be far in excess of the required level. See comments for the ACQ-PEAKXD exposure. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. 1702930549672 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Second visit of GJ 1243. A non-flaring spectrum of GJ 1243 from 1100-9000 Ang was constructed for the TA calculation: FUV and NUV spectra of AD Leo (a dM3e star; Hawley & Pettersen 1991) scaled to the magnitude of GJ 1243 combined with an optical spectrum of GJ 1243 (Kowalski et al. 2013 ApJS). We used SWIFT/UVOT images of GJ1243 in the UVW1 and UVM2 filters (archive.stsci.edu) to refine the quiescent UV flux. (Tic-Visit :proposal-id 17464 :visit-id "03" :proposal-version -1 :trans-version "20230626" :date "18-Dec-2023 15:15:48.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 7 :saa-model "32" :si-bright-earth-limb-angle 20.0 :data-volume 10036336 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17464 :visit-id "03" :obset-id "03" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17464 :visit-id "03" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2477 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "03" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "03" :orbit-number 3 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "03" :orbit-number 4 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "03" :orbit-number 5 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "03" :orbit-number 6 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "03" :orbit-number 7 :pcs-time 392 :si-vis-utilization 2528 :al-overhead-at-end 0 :internal-dur-at-end 417 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2920 :pcs-gap 0 ) true 7 0 Because the target is intrinsically very faint in the UV during quiescence, a large fraction of the first orbit of each visit must be used for target acquistion. We have scheduled a TA algorithm of ACQ/PEAKXD (300s) +ACQ/PEAKD (300s), which give the best S/N ~ 27 and 32, respectively, for a dwell time of 300 seconds for the spectrum of GJ 1243 scaled to U=15.5. In HST GO 13323 (Sept 2014), we calculated a S/N of 40 for this quiescent spectrum of GJ 1243 (COS.sa.519303), and this TA algorithm apparently worked well then. There is no major change in sensitivity between 2014 and 2024: https://www.stsci.edu/hst/instrumentation/cos/performance/sensitivity Note, two 3x3 ACQ/SEARCH algorithms only allow for shorter exposure times but this takes up an entire orbit. The COS/G230L wavelength position of 3360 gives better S/N (compared to the wavelength position of the science exposures with COS wavelength position 2950) during quiescence because it samples the redder/brighter part of the quiescent continuum. Note that we have conservatively estimated the UV flux of GJ 1243 and any small flares will only increase the S/N for each TA exposure. We performed an ETC simulation with a conservatively large flare (\Delta u = 4.7 mag; see comments for Orb2-Science Exposure 1) for the 3360 grating and the local+global count rate limits are not exceeded. The buffer time from the ETC (COS.sa.519401) is 200 seconds (2/3 x buffer time is 130 sec), which is less than the exposure time. This would result in the loss of data during the acquisition but the S/N would be far in excess of the required level. See comments for the ACQ-PEAKXD exposure. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. 1702930552938 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Third visit of GJ 1243. A non-flaring spectrum of GJ 1243 from 1100-9000 Ang was constructed for the TA calculation: FUV and NUV spectra of AD Leo (a dM3e star; Hawley & Pettersen 1991) scaled to the magnitude of GJ 1243 combined with an optical spectrum of GJ 1243 (Kowalski et al. 2013 ApJS). We used SWIFT/UVOT images of GJ1243 in the UVW1 and UVM2 filters (archive.stsci.edu) to refine the quiescent UV flux. (Tic-Visit :proposal-id 17464 :visit-id "04" :proposal-version -1 :trans-version "20230626" :date "18-Dec-2023 15:15:52.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 7 :saa-model "32" :si-bright-earth-limb-angle 20.0 :data-volume 10036336 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17464 :visit-id "04" :obset-id "04" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17464 :visit-id "04" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2477 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "04" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "04" :orbit-number 3 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "04" :orbit-number 4 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "04" :orbit-number 5 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "04" :orbit-number 6 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "04" :orbit-number 7 :pcs-time 392 :si-vis-utilization 2528 :al-overhead-at-end 0 :internal-dur-at-end 417 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2920 :pcs-gap 0 ) true 7 0 Because the target is intrinsically very faint in the UV during quiescence, a large fraction of the first orbit of each visit must be used for target acquistion. We have scheduled a TA algorithm of ACQ/PEAKXD (300s) +ACQ/PEAKD (300s), which give the best S/N ~ 27 and 32, respectively, for a dwell time of 300 seconds for the spectrum of GJ 1243 scaled to U=15.5. In HST GO 13323 (Sept 2014), we calculated a S/N of 40 for this quiescent spectrum of GJ 1243 (COS.sa.519303), and this TA algorithm apparently worked well then. There is no major change in sensitivity between 2014 and 2024: https://www.stsci.edu/hst/instrumentation/cos/performance/sensitivity Note, two 3x3 ACQ/SEARCH algorithms only allow for shorter exposure times but this takes up an entire orbit. The COS/G230L wavelength position of 3360 gives better S/N (compared to the wavelength position of the science exposures with COS wavelength position 2950) during quiescence because it samples the redder/brighter part of the quiescent continuum. Note that we have conservatively estimated the UV flux of GJ 1243 and any small flares will only increase the S/N for each TA exposure. We performed an ETC simulation with a conservatively large flare (\Delta u = 4.7 mag; see comments for Orb2-Science Exposure 1) for the 3360 grating and the local+global count rate limits are not exceeded. The buffer time from the ETC (COS.sa.519401) is 200 seconds (2/3 x buffer time is 130 sec), which is less than the exposure time. This would result in the loss of data during the acquisition but the S/N would be far in excess of the required level. See comments for the ACQ-PEAKXD exposure. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. 1702930556133 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Fourth visit of GJ 1243. A non-flaring spectrum of GJ 1243 from 1100-9000 Ang was constructed for the TA calculation: FUV and NUV spectra of AD Leo (a dM3e star; Hawley & Pettersen 1991) scaled to the magnitude of GJ 1243 combined with an optical spectrum of GJ 1243 (Kowalski et al. 2013 ApJS). We used SWIFT/UVOT images of GJ1243 in the UVW1 and UVM2 filters (archive.stsci.edu) to refine the quiescent UV flux. 1708361420000 322.479031320939 (Tic-Visit :proposal-id 17464 :visit-id "05" :proposal-version -1 :trans-version "20230626" :date "18-Dec-2023 15:15:55.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 7 :saa-model "32" :si-bright-earth-limb-angle 20.0 :data-volume 10036336 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17464 :visit-id "05" :obset-id "05" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17464 :visit-id "05" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2477 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "05" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "05" :orbit-number 3 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "05" :orbit-number 4 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "05" :orbit-number 5 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "05" :orbit-number 6 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "05" :orbit-number 7 :pcs-time 392 :si-vis-utilization 2528 :al-overhead-at-end 0 :internal-dur-at-end 417 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2920 :pcs-gap 0 ) true 7 0 Because the target is intrinsically very faint in the UV during quiescence, a large fraction of the first orbit of each visit must be used for target acquistion. We have scheduled a TA algorithm of ACQ/PEAKXD (300s) +ACQ/PEAKD (300s), which give the best S/N ~ 27 and 32, respectively, for a dwell time of 300 seconds for the spectrum of GJ 1243 scaled to U=15.5. In HST GO 13323 (Sept 2014), we calculated a S/N of 40 for this quiescent spectrum of GJ 1243 (COS.sa.519303), and this TA algorithm apparently worked well then. There is no major change in sensitivity between 2014 and 2024: https://www.stsci.edu/hst/instrumentation/cos/performance/sensitivity Note, two 3x3 ACQ/SEARCH algorithms only allow for shorter exposure times but this takes up an entire orbit. The COS/G230L wavelength position of 3360 gives better S/N (compared to the wavelength position of the science exposures with COS wavelength position 2950) during quiescence because it samples the redder/brighter part of the quiescent continuum. Note that we have conservatively estimated the UV flux of GJ 1243 and any small flares will only increase the S/N for each TA exposure. We performed an ETC simulation with a conservatively large flare (\Delta u = 4.7 mag; see comments for Orb2-Science Exposure 1) for the 3360 grating and the local+global count rate limits are not exceeded. The buffer time from the ETC (COS.sa.519401) is 200 seconds (2/3 x buffer time is 130 sec), which is less than the exposure time. This would result in the loss of data during the acquisition but the S/N would be far in excess of the required level. See comments for the ACQ-PEAKXD exposure. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. 1702930559744 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Fifth visit of GJ 1243. A non-flaring spectrum of GJ 1243 from 1100-9000 Ang was constructed for the TA calculation: FUV and NUV spectra of AD Leo (a dM3e star; Hawley & Pettersen 1991) scaled to the magnitude of GJ 1243 combined with an optical spectrum of GJ 1243 (Kowalski et al. 2013 ApJS). We used SWIFT/UVOT images of GJ1243 in the UVW1 and UVM2 filters (archive.stsci.edu) to refine the quiescent UV flux. 1708446769000 321.38997065779654 (Tic-Visit :proposal-id 17464 :visit-id "06" :proposal-version -1 :trans-version "20230626" :date "18-Dec-2023 15:15:58.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 7 :saa-model "32" :si-bright-earth-limb-angle 20.0 :data-volume 10036336 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17464 :visit-id "06" :obset-id "06" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17464 :visit-id "06" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2477 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "06" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "06" :orbit-number 3 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "06" :orbit-number 4 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "06" :orbit-number 5 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "06" :orbit-number 6 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "06" :orbit-number 7 :pcs-time 392 :si-vis-utilization 2528 :al-overhead-at-end 0 :internal-dur-at-end 417 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2920 :pcs-gap 0 ) true 7 0 Because the target is intrinsically very faint in the UV during quiescence, a large fraction of the first orbit of each visit must be used for target acquistion. We have scheduled a TA algorithm of ACQ/PEAKXD (300s) +ACQ/PEAKD (300s), which give the best S/N ~ 27 and 32, respectively, for a dwell time of 300 seconds for the spectrum of GJ 1243 scaled to U=15.5. In HST GO 13323 (Sept 2014), we calculated a S/N of 40 for this quiescent spectrum of GJ 1243 (COS.sa.519303), and this TA algorithm apparently worked well then. There is no major change in sensitivity between 2014 and 2024: https://www.stsci.edu/hst/instrumentation/cos/performance/sensitivity Note, two 3x3 ACQ/SEARCH algorithms only allow for shorter exposure times but this takes up an entire orbit. The COS/G230L wavelength position of 3360 gives better S/N (compared to the wavelength position of the science exposures with COS wavelength position 2950) during quiescence because it samples the redder/brighter part of the quiescent continuum. Note that we have conservatively estimated the UV flux of GJ 1243 and any small flares will only increase the S/N for each TA exposure. We performed an ETC simulation with a conservatively large flare (\Delta u = 4.7 mag; see comments for Orb2-Science Exposure 1) for the 3360 grating and the local+global count rate limits are not exceeded. The buffer time from the ETC (COS.sa.519401) is 200 seconds (2/3 x buffer time is 130 sec), which is less than the exposure time. This would result in the loss of data during the acquisition but the S/N would be far in excess of the required level. See comments for the ACQ-PEAKXD exposure. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. 1702930562948 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Sixth visit of GJ 1243. A non-flaring spectrum of GJ 1243 from 1100-9000 Ang was constructed for the TA calculation: FUV and NUV spectra of AD Leo (a dM3e star; Hawley & Pettersen 1991) scaled to the magnitude of GJ 1243 combined with an optical spectrum of GJ 1243 (Kowalski et al. 2013 ApJS). We used SWIFT/UVOT images of GJ1243 in the UVW1 and UVM2 filters (archive.stsci.edu) to refine the quiescent UV flux. (Tic-Visit :proposal-id 17464 :visit-id "07" :proposal-version -1 :trans-version "20230626" :date "18-Dec-2023 15:16:02.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 7 :saa-model "32" :si-bright-earth-limb-angle 20.0 :data-volume 10036336 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17464 :visit-id "07" :obset-id "07" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17464 :visit-id "07" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2477 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "07" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "07" :orbit-number 3 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "07" :orbit-number 4 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "07" :orbit-number 5 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "07" :orbit-number 6 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "07" :orbit-number 7 :pcs-time 392 :si-vis-utilization 2528 :al-overhead-at-end 0 :internal-dur-at-end 417 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2920 :pcs-gap 0 ) true 7 0 Because the target is intrinsically very faint in the UV during quiescence, a large fraction of the first orbit of each visit must be used for target acquistion. We have scheduled a TA algorithm of ACQ/PEAKXD (300s) +ACQ/PEAKD (300s), which give the best S/N ~ 27 and 32, respectively, for a dwell time of 300 seconds for the spectrum of GJ 1243 scaled to U=15.5. In HST GO 13323 (Sept 2014), we calculated a S/N of 40 for this quiescent spectrum of GJ 1243 (COS.sa.519303), and this TA algorithm apparently worked well then. There is no major change in sensitivity between 2014 and 2024: https://www.stsci.edu/hst/instrumentation/cos/performance/sensitivity Note, two 3x3 ACQ/SEARCH algorithms only allow for shorter exposure times but this takes up an entire orbit. The COS/G230L wavelength position of 3360 gives better S/N (compared to the wavelength position of the science exposures with COS wavelength position 2950) during quiescence because it samples the redder/brighter part of the quiescent continuum. Note that we have conservatively estimated the UV flux of GJ 1243 and any small flares will only increase the S/N for each TA exposure. We performed an ETC simulation with a conservatively large flare (\Delta u = 4.7 mag; see comments for Orb2-Science Exposure 1) for the 3360 grating and the local+global count rate limits are not exceeded. The buffer time from the ETC (COS.sa.519401) is 200 seconds (2/3 x buffer time is 130 sec), which is less than the exposure time. This would result in the loss of data during the acquisition but the S/N would be far in excess of the required level. See comments for the ACQ-PEAKXD exposure. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. 1702930566568 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Seventh visit of GJ 1243. A non-flaring spectrum of GJ 1243 from 1100-9000 Ang was constructed for the TA calculation: FUV and NUV spectra of AD Leo (a dM3e star; Hawley & Pettersen 1991) scaled to the magnitude of GJ 1243 combined with an optical spectrum of GJ 1243 (Kowalski et al. 2013 ApJS). We used SWIFT/UVOT images of GJ1243 in the UVW1 and UVM2 filters (archive.stsci.edu) to refine the quiescent UV flux. (Tic-Visit :proposal-id 17464 :visit-id "08" :proposal-version -1 :trans-version "20230626" :date "18-Dec-2023 15:16:05.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 7 :saa-model "32" :si-bright-earth-limb-angle 20.0 :data-volume 10036336 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17464 :visit-id "08" :obset-id "08" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17464 :visit-id "08" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2477 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "08" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "08" :orbit-number 3 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "08" :orbit-number 4 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "08" :orbit-number 5 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "08" :orbit-number 6 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "08" :orbit-number 7 :pcs-time 392 :si-vis-utilization 2528 :al-overhead-at-end 0 :internal-dur-at-end 417 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2920 :pcs-gap 0 ) true 7 0 Because the target is intrinsically very faint in the UV during quiescence, a large fraction of the first orbit of each visit must be used for target acquistion. We have scheduled a TA algorithm of ACQ/PEAKXD (300s) +ACQ/PEAKD (300s), which give the best S/N ~ 27 and 32, respectively, for a dwell time of 300 seconds for the spectrum of GJ 1243 scaled to U=15.5. In HST GO 13323 (Sept 2014), we calculated a S/N of 40 for this quiescent spectrum of GJ 1243 (COS.sa.519303), and this TA algorithm apparently worked well then. There is no major change in sensitivity between 2014 and 2024: https://www.stsci.edu/hst/instrumentation/cos/performance/sensitivity Note, two 3x3 ACQ/SEARCH algorithms only allow for shorter exposure times but this takes up an entire orbit. The COS/G230L wavelength position of 3360 gives better S/N (compared to the wavelength position of the science exposures with COS wavelength position 2950) during quiescence because it samples the redder/brighter part of the quiescent continuum. Note that we have conservatively estimated the UV flux of GJ 1243 and any small flares will only increase the S/N for each TA exposure. We performed an ETC simulation with a conservatively large flare (\Delta u = 4.7 mag; see comments for Orb2-Science Exposure 1) for the 3360 grating and the local+global count rate limits are not exceeded. The buffer time from the ETC (COS.sa.519401) is 200 seconds (2/3 x buffer time is 130 sec), which is less than the exposure time. This would result in the loss of data during the acquisition but the S/N would be far in excess of the required level. See comments for the ACQ-PEAKXD exposure. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. 1702930569863 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Eigth visit of GJ 1243. A non-flaring spectrum of GJ 1243 from 1100-9000 Ang was constructed for the TA calculation: FUV and NUV spectra of AD Leo (a dM3e star; Hawley & Pettersen 1991) scaled to the magnitude of GJ 1243 combined with an optical spectrum of GJ 1243 (Kowalski et al. 2013 ApJS). We used SWIFT/UVOT images of GJ1243 in the UVW1 and UVM2 filters (archive.stsci.edu) to refine the quiescent UV flux. 1708276061000 323.57015208866846 (Tic-Visit :proposal-id 17464 :visit-id "12" :proposal-version -1 :trans-version "20230626" :date "18-Dec-2023 15:16:08.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 7 :saa-model "32" :si-bright-earth-limb-angle 20.0 :data-volume 10036336 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17464 :visit-id "12" :obset-id "12" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17464 :visit-id "12" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2477 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "12" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "12" :orbit-number 3 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "12" :orbit-number 4 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "12" :orbit-number 5 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "12" :orbit-number 6 :pcs-time 392 :si-vis-utilization 2528 :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 2920 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "12" :orbit-number 7 :pcs-time 392 :si-vis-utilization 2528 :al-overhead-at-end 0 :internal-dur-at-end 417 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2920 :pcs-gap 0 ) true 7 0 Because the target is intrinsically very faint in the UV during quiescence, a large fraction of the first orbit of each visit must be used for target acquistion. We have scheduled a TA algorithm of ACQ/PEAKXD (300s) +ACQ/PEAKD (300s), which give the best S/N ~ 27 and 32, respectively, for a dwell time of 300 seconds for the spectrum of GJ 1243 scaled to U=15.5. In HST GO 13323 (Sept 2014), we calculated a S/N of 40 for this quiescent spectrum of GJ 1243 (COS.sa.519303), and this TA algorithm apparently worked well then. There is no major change in sensitivity between 2014 and 2024: https://www.stsci.edu/hst/instrumentation/cos/performance/sensitivity Note, two 3x3 ACQ/SEARCH algorithms only allow for shorter exposure times but this takes up an entire orbit. The COS/G230L wavelength position of 3360 gives better S/N (compared to the wavelength position of the science exposures with COS wavelength position 2950) during quiescence because it samples the redder/brighter part of the quiescent continuum. Note that we have conservatively estimated the UV flux of GJ 1243 and any small flares will only increase the S/N for each TA exposure. We performed an ETC simulation with a conservatively large flare (\Delta u = 4.7 mag; see comments for Orb2-Science Exposure 1) for the 3360 grating and the local+global count rate limits are not exceeded. The buffer time from the ETC (COS.sa.519401) is 200 seconds (2/3 x buffer time is 130 sec), which is less than the exposure time. This would result in the loss of data during the acquisition but the S/N would be far in excess of the required level. See comments for the ACQ-PEAKXD exposure. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. The COS ETC Run # is given for the worst-case scenario (largest flare possible) according to COS ISR 2017-01(v3). Buffer-time justification: We choose a conservative buffer-time of 120 sec. The ETC for a conservatiely large flare (COS.sp.1890592) with \Delta U ~ -4.7 mag flare (twice the largest flare observed in 5 months with Kepler) and with a T_flare=12,000K blackbody spectrum has a buffer fill time of 237 sec, and 2/3 of this is 150 sec. To allow for slightly larger increases still, a buffer-time of 120 seconds is chosen (which is near the minimum allowable). The COS ETC Run # is given in the field above (and for Phase 1) is for the absolute worst-case scenario (largest flare possible) according to ISR COS 2017-01(v3). The ETC gives a buffer fill time of 22s, but we think the chances of a magnitude of this flare (delta U = -8 mags) occurring is very small (i.e., has never been observed on this star) within our monitoring time. Since we require time-tag mode, we set the buffer time to 120s. This was used in the HST GO 13323 observations. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. 1702930574314 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. First visit of CR Dra. 1715676865000 204.0 (Tic-Visit :proposal-id 17464 :visit-id "02" :proposal-version -1 :trans-version "20230626" :date "18-Dec-2023 15:16:12.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 8 :saa-model "32" :si-bright-earth-limb-angle 20.0 :data-volume 12871440 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17464 :visit-id "02" :obset-id "02" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17464 :visit-id "02" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2491 :al-overhead-at-end 0 :internal-dur-at-end 152 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "02" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "02" :orbit-number 3 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "02" :orbit-number 4 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "02" :orbit-number 5 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "02" :orbit-number 6 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "02" :orbit-number 7 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "02" :orbit-number 8 :pcs-time 392 :si-vis-utilization 2542 :al-overhead-at-end 0 :internal-dur-at-end 426 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2934 :pcs-gap 0 ) true 8 0 The exposure time for TA was determined by scaling by the U-band magnitude difference (delta mag = -3.5) compared to GJ 1243. The S/N is 55 per 12s dwell time for a Pickles model M2V scaled to U=12.0. It will be slightly larger S/N for a M1-type like CR Dra. We checked the Pickles model flux at 3000 Ang against a IUE/LWP spectrum of CR Dra. See comments for the ACQ-PEAKXD exposure. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. 1702930578680 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Second visit of CR Dra. 1710662416000 251.55241682305598 (Tic-Visit :proposal-id 17464 :visit-id "09" :proposal-version -1 :trans-version "20230626" :date "18-Dec-2023 15:16:17.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 8 :saa-model "32" :si-bright-earth-limb-angle 20.0 :data-volume 12871440 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17464 :visit-id "09" :obset-id "09" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17464 :visit-id "09" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2491 :al-overhead-at-end 0 :internal-dur-at-end 152 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "09" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "09" :orbit-number 3 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "09" :orbit-number 4 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "09" :orbit-number 5 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "09" :orbit-number 6 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "09" :orbit-number 7 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "09" :orbit-number 8 :pcs-time 392 :si-vis-utilization 2542 :al-overhead-at-end 0 :internal-dur-at-end 426 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2934 :pcs-gap 0 ) true 8 0 The exposure time for TA was determined by scaling by the U-band magnitude difference (delta mag = -3.5) compared to GJ 1243. The S/N is 55 per 12s dwell time for a Pickles model M2V scaled to U=12.0. It will be slightly larger S/N for a M1-type like CR Dra. We checked the Pickles model flux at 3000 Ang against a IUE/LWP spectrum of CR Dra. See comments for the ACQ-PEAKXD exposure. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. 1702930583190 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Third visit of CR Dra. 1715762186000 204.0 (Tic-Visit :proposal-id 17464 :visit-id "10" :proposal-version -1 :trans-version "20230626" :date "18-Dec-2023 15:16:22.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 8 :saa-model "32" :si-bright-earth-limb-angle 20.0 :data-volume 12871440 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17464 :visit-id "10" :obset-id "10" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17464 :visit-id "10" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2491 :al-overhead-at-end 0 :internal-dur-at-end 152 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "10" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "10" :orbit-number 3 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "10" :orbit-number 4 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "10" :orbit-number 5 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "10" :orbit-number 6 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "10" :orbit-number 7 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "10" :orbit-number 8 :pcs-time 392 :si-vis-utilization 2542 :al-overhead-at-end 0 :internal-dur-at-end 426 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2934 :pcs-gap 0 ) true 8 0 The exposure time for TA was determined by scaling by the U-band magnitude difference (delta mag = -3.5) compared to GJ 1243. The S/N is 55 per 12s dwell time for a Pickles model M2V scaled to U=12.0. It will be slightly larger S/N for a M1-type like CR Dra. We checked the Pickles model flux at 3000 Ang against a IUE/LWP spectrum of CR Dra. See comments for the ACQ-PEAKXD exposure. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. 1702930587282 The scheduling data was generated by CASM 31.1. CASM was run in Phase II mode. Fourth visit of CR Dra. 1715932796000 204.0 (Tic-Visit :proposal-id 17464 :visit-id "11" :proposal-version -1 :trans-version "20230626" :date "18-Dec-2023 15:16:26.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 8 :saa-model "32" :si-bright-earth-limb-angle 20.0 :data-volume 12871440 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 17464 :visit-id "11" :obset-id "11" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 17464 :visit-id "11" :orbit-number 1 :pcs-time 443 :si-vis-utilization 2491 :al-overhead-at-end 0 :internal-dur-at-end 152 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "11" :orbit-number 2 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "11" :orbit-number 3 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "11" :orbit-number 4 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "11" :orbit-number 5 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "11" :orbit-number 6 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "11" :orbit-number 7 :pcs-time 392 :si-vis-utilization 2542 :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 2934 :pcs-gap 0 ) (Tic-Orbit :proposal-id 17464 :visit-id "11" :orbit-number 8 :pcs-time 392 :si-vis-utilization 2542 :al-overhead-at-end 0 :internal-dur-at-end 426 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2934 :pcs-gap 0 ) true 8 0 The exposure time for TA was determined by scaling by the U-band magnitude difference (delta mag = -3.5) compared to GJ 1243. The S/N is 55 per 12s dwell time for a Pickles model M2V scaled to U=12.0. It will be slightly larger S/N for a M1-type like CR Dra. We checked the Pickles model flux at 3000 Ang against a IUE/LWP spectrum of CR Dra. See comments for the ACQ-PEAKXD exposure. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring. Buffer time justification: COS.sp.1890594 says that in the event of a very large flare (Delta U-mag = -1.5 mags) on this star, the Buffer Fill Time is 185s. 2/3 of this is ~120s, and this is what we set for the Buffer time. The ETC Run # given above in the form (from the Phase A) is in the case of an enormous flare (delta U = -2.8mags), which we do not expect to occur on this star within our monitoring time. FP-POS = 3 is requested because we do not want to coadd data from individual FP-POS settings during our monitoring.