0 Assigned ID: 211 ----- Attempting Submission 1 (Thu Apr 09 16:16:17 GMT 2015) ----- An FUV exposure with Wavelength 1055 or 1096 has been specified with SEGMENT=B. An FUV exposure with Wavelength 1055 or 1096 has been specified with SEGMENT=B. An FUV exposure with Wavelength 1055 or 1096 has been specified with SEGMENT=B. An FUV exposure with Wavelength 1055 or 1096 has been specified with SEGMENT=B. An FUV exposure with Wavelength 1055 or 1096 has been specified with SEGMENT=B. updated coordinates and observing strategy to implement some wavecals during occultations 367342438 ----- Attempting Submission 1 (Wed Jul 22 02:20:28 GMT 2015) ----- ----- Attempting Submission 2 (Fri Dec 04 19:24:54 GMT 2015) ----- Target is too bright for FUVA. Wavelength alignment will be done manually, so no wavecals are obtained. We are requesting 2 orbits to obtain the data needed to produce 1-D flat fields for the COS FUV blue modes (CENWAVE = 1055, 1096). We use data obtained in a previous calibration program to demonstrate that the 1-D flats currently used by the COS team to correct the grid-wire shadows in the FUV channels are inappropriate for the "blue modes". Unfortunately, only the FUVA data from the previous program are adequate to create new 1-D flats. FUVB 1-D flats are needed for two reasons. First, they are essential for high signal-to-noise observations of any object below 1150 Ang, including hot stars, objects with strong emission lines below 1150 Ang, and the rich interstellar spectrum that lies below 1150 Ang. Further, blue mode FUVB data are typically obtained with the FUVA off. This means that wavelength calibrations must be done separately and can result in crippling overheads if a full complement of FPPOS observations are obtained. However, different FPPOS settings are needed to suppress the fixed pattern noise in the COS FUV detectors. Application of a high quality 1-D flat will minimize the effect of the fixed pattern noise, reducing the number of WAVCALs needed and increasing the efficiency of the instrument. Finally, blue mode FUVB data are now the only medium resolution modes lacking high quality 1-D flats. Obtain high S/N COS FUV data to construct FUVB P-flats for the blue modes. HOT STARS 0 true false false false SUPPORTED STAR DA NO Coordinates and proper motions are form COS TIR 2009-02(v2) This object was generated by the targetselector and retrieved from the SIMBAD database.This object was generated by the targetselector and retrieved from the SIMBAD database. J2000 COS/FUV Spectroscopic No No G130M 1096 1449256859476 C:\Users\acer\AppData\Local\Temp\OPVisit4135906843249622556.xml The scheduling data was generated by CASM 23.2. CASM was run in Phase II mode. (Tic-Visit :proposal-id 14179 :visit-id "02" :proposal-version -1 :trans-version "20150609" :date "04-Dec-2015 14:20:58.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 2 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 1478704 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 14179 :visit-id "02" :obset-id "02" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 14179 :visit-id "02" :orbit-number 1 :pcs-time 333 :si-vis-utilization 3069 :al-overhead-at-end 0 :internal-dur-at-end 874 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3403 :pcs-gap 0 ) (Tic-Orbit :proposal-id 14179 :visit-id "02" :orbit-number 2 :pcs-time 222 :si-vis-utilization 3181 :al-overhead-at-end 0 :internal-dur-at-end 842 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3403 :pcs-gap 0 ) true 2 0 This TA is a duplicate of two previous ACQ/IMAGES of this target. These 25 second TAs had ~5404 counst; S/N = ~70. Target Brightest Pixel = 1.7 counts/s From the ETC run, the Buffer time should be less than 2.35E6/4088. * (2/3.) < 383.2. For 1350s, the best buffer time is (1350-100)/4 = 312 s From the ETC run, the Buffer time should be less than 2.35E6/4088. * (2/3.) < 383.2. For 1200s, the best buffer time is (1350-100)/4 = 275 s From the ETC run, the Buffer time should be less than 2.35E6/4088. * (2/3.) < 383.2. We used 312 s for others, so we'll just use that one here as well. From the ETC run, the Buffer time should be less than 2.35E6/4088. * (2/3.) < 383.2. For 1350s, the best buffer time is (1350-100)/4 = 312 s From the ETC run, the Buffer time should be less than 2.35E6/4088. * (2/3.) < 383.2. For 1350s, the best buffer time is (1350-100)/4 = 312 s