The total number of Primary Orbits used in all Cycles must equal the total number of Primary Orbits specified on all the Observations. (Compare totals reported on the first and second pages of the PDF Preview.) This program tests a new means of performing snapshots. This is the reason why the number of targets does not equal the number of requested orbits. -1286143515 Assigned ID: 607 ----- Attempting Submission 1 (Fri Nov 16 01:28:38 GMT 2018) ----- HST Phase I Proposal 607 (PhaseI.apt) successfully submitted. Receipt: # 607-1 ----- Attempting Submission 2 (Fri Nov 16 20:43:40 GMT 2018) ----- This is a snapshot program. The number of orbits used exceeds the number allocated This target is not used in this proposal. This pattern is not used in this proposal. This submission includes three potential targets. -890658061 ----- Attempting Submission 1 (Mon Jan 28 19:18:38 GMT 2019) ----- ----- Attempting Submission 2 (Fri Feb 15 01:10:51 GMT 2019) ----- ----- Attempting Submission 3 (Wed Feb 20 05:39:20 GMT 2019) ----- HST Phase II Proposal 15675 (GO15675_Feb19.apt) successfully submitted. Receipt: # 15675-3 ----- Attempting Submission 4 (Wed Feb 20 05:47:53 GMT 2019) ----- ----- Attempting Submission 5 (Tue Mar 05 22:40:09 GMT 2019) ----- HST Phase II Proposal 15675 (March_5th_APT.apt) successfully submitted. Receipt: # 15675-5 ----- Attempting Submission 6 (Tue Mar 05 23:50:09 GMT 2019) ----- ----- Attempting Submission 8 (Wed Apr 03 12:53:08 GMT 2019) ----- ----- Attempting Submission 9 (Wed Apr 10 04:57:07 GMT 2019) ----- HST Phase II Proposal 15675 (April_9th.apt) successfully submitted. Receipt: # 15675-9 ----- Attempting Submission 10 (Wed Apr 10 05:13:53 GMT 2019) ----- We have supplied three potential targets, although we understand at most two can scheduled. A New Approach to Following Transients with HST: Rolling Snapshots We are now entering an era in which large scale surveys of the sky will discover numerous transients each night. The number of targets that could benefit from HST observations on timescales of less than three weeks will easily exceed the ability of HST to schedule disruptive ToO observations. Here we propose a variant of snapshot scheduling that would allow transients to be observed as soon as 11 days after discovery with little to no additional overhead compared to a standard snapshot program. We call this new observational approach ``Rolling Snapshots.'' While any one object will have a low probability of being observed in such a program, the large number of transients available will make it possible to build up statistically significant samples, with the the type of transient and exact observation scheme determined by the science under investigation. Here we ask to use rolling snapshots to obtain WFC3 UV grism spectra of a limited sample of Type Ia, Type II and superluminous supernovae discovered by the Zwicky Transient Facility. This program will allow us to verify that Rolling Snapshots are indeed an efficient use of obsevatory resources and will also give a taste of some of the exciting science the community could undertake with Rolling Snapshots. In this test program, we are using the WFC3/UVIS grism to obtain UV spectra of transients shortly after outburst. We will use the G280Lgrism and take spectra of 500 seconds (split into two dithers). We will also obtain F350LP images of the field. These images have two purposes. First they will serve as the reference image allowing us to set the wavelength scale of the spectra. However, we expect that in over twenty-five percent of our images the first order spectrum of the transient will land on the zeroth order spectrum of the host galaxy in a region where the zeroth order spectrum is bright enough to contribute noticeable contamination. The F350LP filter has very similar throughput to the zeroth order of the G280 grism. We wish to also test whether subtraction of the F350LP image from first order spectrum can be used to reduce this contamination. We are using a custom 1024x1024 subarray in order to reduce readout overhead and buffer dumps to decrease the total time used. We need a custom subarray as the G280 can only be used with the UVIS aperture. Stellar Physics 6 false AVAILABLE EXT-STAR SUPERNOVA SUPERNOVA TYPE IA J2000 STAR SUPERNOVA J2000 EXT-STAR SUPERNOVA SUPERNOVA TYPE IA J2000 EXT-STAR SUPERNOVA J2000 EXT-STAR SUPERNOVA J2000 EXT-STAR SUPERNOVA J2000 EXT-STAR SUPERNOVA TYPE II J2000 EXT-STAR SUPERNOVA TYPE II J2000 EXT-STAR SUPERNOVA PI activated WFC3/UVIS Spectroscopic No No G280 WFC3/UVIS Imaging No No F350LP WFC3/UVIS Spectroscopic No No G280 WFC3/UVIS Imaging No No F350LP WFC3/UVIS Spectroscopic No No G280 WFC3/UVIS Imaging No No F350LP WFC3/UVIS Spectroscopic No No G280 WFC3/UVIS Imaging No No F350LP WFC3/UVIS Spectroscopic No No G280 WFC3/UVIS Imaging No No F350LP WFC3/UVIS Spectroscopic No No G280 WFC3/UVIS Imaging No No F350LP WFC3/UVIS Spectroscopic No No G280 WFC3/UVIS Imaging No No F350LP WFC3/UVIS Spectroscopic No No G280 WFC3/UVIS Imaging No No F350LP WFC3/UVIS Spectroscopic No No G280 WFC3/UVIS Imaging No No F350LP WFC3/UVIS Spectroscopic No No G280 WFC3/UVIS Imaging No No F350LP POS-TARG DITHER 0.145 LINE false false 2 46.84 WFC3-UVIS-DITHER-LINE 1 false POS-TARG DITHER 0.145 LINE false false 2 226.84 WFC3-UVIS-DITHER-LINE 2 false The scheduling data was generated by CASM 27.0. CASM was run in Phase II mode. This is for UVIS2, the preferred chip. (Tic-Visit :proposal-id 15675 :visit-id "T1" :proposal-version -1 :trans-version "20181130" :date "05-Mar-2019 18:49:20.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 87056 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15675 :visit-id "T1" :obset-id "T1" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15675 :visit-id "T1" :orbit-number 1 :pcs-time 333 :si-vis-utilization 1109 :al-overhead-at-end 80 :internal-dur-at-end 132 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3142 :pcs-gap 0 ) false 1 0 Template for future visits. We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. The scheduling data was generated by CASM 27.0. CASM was run in Phase II mode. This is for UVIS1, to be used only if UVIS2 won't schedule because of the large POSTARG. (Tic-Visit :proposal-id 15675 :visit-id "T2" :proposal-version -1 :trans-version "20181130" :date "05-Mar-2019 18:49:21.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 87056 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15675 :visit-id "T2" :obset-id "T2" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15675 :visit-id "T2" :orbit-number 1 :pcs-time 333 :si-vis-utilization 1121 :al-overhead-at-end 83 :internal-dur-at-end 132 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3142 :pcs-gap 0 ) false 1 0 Template for future visits. The nominal position is 512.0, 3581 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, 49".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. The nominal position is 512.0, 3581 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, 49".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. The nominal position is 512.0, 3581 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, 49".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. The nominal position is 512.0, 3581 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, 49".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. The nominal position is 512.0, 3581 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, 49".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. The scheduling data was generated by CASM 27.0. CASM was run in Phase II mode. This is for UVIS2, the preferred chip. 1551742756000 230.04956933071105 (Tic-Visit :proposal-id 15675 :visit-id "3A" :proposal-version -1 :trans-version "20181130" :date "05-Mar-2019 18:49:22.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 104464 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15675 :visit-id "3A" :obset-id "3A" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15675 :visit-id "3A" :orbit-number 1 :pcs-time 333 :si-vis-utilization 1380 :al-overhead-at-end 83 :internal-dur-at-end 151 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3285 :pcs-gap 0 ) false 1 0 We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. The scheduling data was generated by CASM 27.0. CASM was run in Phase II mode. This is for UVIS2, the preferred chip. 1553349361000 206.1539865450245 (Tic-Visit :proposal-id 15675 :visit-id "4A" :proposal-version -1 :trans-version "20181130" :date "05-Mar-2019 18:49:23.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 104464 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15675 :visit-id "4A" :obset-id "4A" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15675 :visit-id "4A" :orbit-number 1 :pcs-time 333 :si-vis-utilization 1296 :al-overhead-at-end 80 :internal-dur-at-end 151 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3165 :pcs-gap 0 ) false 1 0 We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. The scheduling data was generated by CASM 27.0. CASM was run in Phase II mode. This is for UVIS2, the preferred chip. (Tic-Visit :proposal-id 15675 :visit-id "5A" :proposal-version -1 :trans-version "20181130" :date "12-Mar-2019 23:47:30.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 104464 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15675 :visit-id "5A" :obset-id "5A" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15675 :visit-id "5A" :orbit-number 1 :pcs-time 333 :si-vis-utilization 1256 :al-overhead-at-end 80 :internal-dur-at-end 151 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3157 :pcs-gap 0 ) false 1 0 We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. The scheduling data was generated by CASM 27.0. CASM was run in Phase II mode. This is for UVIS2, the preferred chip. (Tic-Visit :proposal-id 15675 :visit-id "5B" :proposal-version -1 :trans-version "20181130" :date "12-Mar-2019 23:47:32.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 104464 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15675 :visit-id "5B" :obset-id "5B" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15675 :visit-id "5B" :orbit-number 1 :pcs-time 333 :si-vis-utilization 1226 :al-overhead-at-end 80 :internal-dur-at-end 151 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3285 :pcs-gap 0 ) false 1 0 This SN has been fading rapidly, so we are removing it from observation We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. This is for UVIS2, the preferred chip. (Tic-Visit :proposal-id 15675 :visit-id "6A" :proposal-version -1 :trans-version "20181130" :date "02-Apr-2019 19:28:43.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 104464 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15675 :visit-id "6A" :obset-id "6A" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15675 :visit-id "6A" :orbit-number 1 :pcs-time 333 :si-vis-utilization 1296 :al-overhead-at-end 80 :internal-dur-at-end 151 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3238 :pcs-gap 0 ) false 1 0 We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. DR Note: Moving an additional 4" to better remove offset between F350LP and G280 to -61" -80". We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. DR Note: Moving an additional 4" to better remove offset between F350LP and G280 to -61" -80". We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. DR Note: Moving an additional 4" to better remove offset between F350LP and G280 to -59" -76". This is for UVIS2, the preferred chip. (Tic-Visit :proposal-id 15675 :visit-id "5A" :proposal-version -1 :trans-version "20181130" :date "12-Mar-2019 23:47:30.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 104464 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15675 :visit-id "5A" :obset-id "5A" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15675 :visit-id "5A" :orbit-number 1 :pcs-time 333 :si-vis-utilization 1256 :al-overhead-at-end 80 :internal-dur-at-end 151 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3157 :pcs-gap 0 ) false 1 0 We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. DR Note: Moving an additional 4" to better remove offset between F350LP and G280 to -61" -80". We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. DR Note: Moving an additional 4" to better remove offset between F350LP and G280 to -61" -80". We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. DR Note: Moving an additional 4" to better remove offset between F350LP and G280 to -59" -76". This is for UVIS2, the preferred chip. (Tic-Visit :proposal-id 15675 :visit-id "6A" :proposal-version -1 :trans-version "20181130" :date "02-Apr-2019 19:28:43.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 104464 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15675 :visit-id "6A" :obset-id "6A" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15675 :visit-id "6A" :orbit-number 1 :pcs-time 333 :si-vis-utilization 1296 :al-overhead-at-end 80 :internal-dur-at-end 151 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3238 :pcs-gap 0 ) false 1 0 We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. DR Note: Moving an additional 4" to better remove offset between F350LP and G280 to -61" -80". We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. DR Note: Moving an additional 4" to better remove offset between F350LP and G280 to -61" -80". We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. DR Note: Moving an additional 4" to better remove offset between F350LP and G280 to -59" -76". This is for UVIS2, the preferred chip. (Tic-Visit :proposal-id 15675 :visit-id "5A" :proposal-version -1 :trans-version "20181130" :date "12-Mar-2019 23:47:30.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 104464 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15675 :visit-id "5A" :obset-id "5A" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15675 :visit-id "5A" :orbit-number 1 :pcs-time 333 :si-vis-utilization 1256 :al-overhead-at-end 80 :internal-dur-at-end 151 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3157 :pcs-gap 0 ) false 1 0 We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. DR Note: Moving an additional 4" to better remove offset between F350LP and G280 to -61" -80". We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. DR Note: Moving an additional 4" to better remove offset between F350LP and G280 to -61" -80". We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. DR Note: Moving an additional 4" to better remove offset between F350LP and G280 to -59" -76". This is for UVIS2, the preferred chip. (Tic-Visit :proposal-id 15675 :visit-id "5A" :proposal-version -1 :trans-version "20181130" :date "12-Mar-2019 23:47:30.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 104464 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15675 :visit-id "5A" :obset-id "5A" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15675 :visit-id "5A" :orbit-number 1 :pcs-time 333 :si-vis-utilization 1256 :al-overhead-at-end 80 :internal-dur-at-end 151 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3157 :pcs-gap 0 ) false 1 0 We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. DR Note: Moving an additional 4" to better remove offset between F350LP and G280 to -61" -80". We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. DR Note: Moving an additional 4" to better remove offset between F350LP and G280 to -61" -80". We are effectively duplicating the UVIS2-C1K1C-SUB aperture, but using the UVIS aperture appropriate for G280. The nominal position is 537.0, 512.0 while for UVIS, it's 2073.0, 250.0 (or effectively 2073.0, 2332). So we want a POSTARG of -61".0, -72".0. This was slightly refined in Aladin. From SB: One minor comment I'd have is to consider shifting the area for the subarray readout slightly to the left, in order to include the left overscan i.e. decrease CENTERAXIS1 by 23. By including the overscan columns in the subarray, the calibration software can compute the correction using the image itself rather than using a default look-up value. Note: 23 not 25 is the number of overscan pixels for a subarray. New note: CENTERAXIS includes overscan, so use 513. DR note: 515 to stop the warnings. DR Note: Moving an additional 4" to better remove offset between F350LP and G280 to -59" -76".