Cycle 21 CS Training COS/STIS Instrument Team Paule Sonnentrucker June 12, 2013
advertisement
Cycle 21 CS Training COS/STIS Instrument Team Paule Sonnentrucker June 12, 2013 Acknowledgments: Nolan Walborn; Svea Hernandez, Cristina Oliveira, Steve Penton, Charles Proffitt, John Debes OUTLINE I. Introduction I. Phase II Support: Timeline & Responsibilities II. Cycle 21 Highlights I. General Considerations: Cycle‐independent 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 2 I. INTRODUCTION Who We Are Officially: “The Contact Scientist (CS) is an Instrument Scientist (IS) belonging to the STScI team who supports calibration and use of the instrument(s) in the assigned programs.” Our Official Role: The CS provides advice on observing strategies: 1‐ to meet the scientific objectives of the program, 2‐ to answer questions about instrument performance and 3‐ to maintain the health and safety of the detectors subject to damage by over‐illumination: COS and STIS/MAMA Our responsibility ends when programs have completed! => Questions are redirected to helpdesk Ref: http://www.stsci.edu/hst/proposing/docs/proposingOverview 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 3 I. INTRODUCTION STScI expectations and our goals: Providing excellent support of HST science and users is the fundamental reason for the existence of the Institute and our scientific staff. 1‐ Support of GO program development and implementation as a primary point of contact between STScI and the astronomical community 2‐ IS bring essential scientific and instrument expertise to this process, which complements that of the PCs/RIAs in scheduling and other technical issues (helpdesk service) Our Goal: Do our best from our perspectives to ensure optimum effectiveness of HST observing programs and optimum data quality. 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 4 II. Phase II Support Timeline: 1‐ TAC Notifications were sent out to Proposers: May 30, 2013 2‐ CS/IS assignments & SPAR notification + CS phase I deliveries: June 7 Phase I are confidential! 3‐ Phase II deadline: June 27, 2013 – Budget Hard deadline. NB: Phase II can be submitted later by at most 1 week. Decision should be made on a case‐by‐case basis in consultation with PC. 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 5 II. Phase II Support PI/PC Responsibilities – 1‐ Deliver an error‐free Phase II proposal – PC checks submission 2‐ Perform BOT reviews & provide supporting material to CS at time of submission 3‐ Provide ETC ID numbers in APT for ACQ & Science exposures 4‐ Check target coordinates and proper motion accuracy 5‐ Check for duplications & phase I / Phase II compliance 6‐ Confirmation charts are the responsibility of PI now! PCs are not tasked to remind PI to produce those charts anymore! We do not check these items! 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 6 II. Phase II Support CS/IS Responsibilities: Things to Remember! The advice we give is only as good as the information we receive! So… 1‐ Get familiar with the Phase I proposals once sent to you. Remember Phase I are confidential. ‐> remove copies from your mailbox and protect your repository. 2‐ CS interact directly with PIs; IS do not but can if they so wish. If you choose to remain an anonymous IS, send your recommendations to PC/helpdesk and always copy the history file of the program you are giving advice on. 3‐ If contacted, do not hesitate to ask the PIs for details about sources, fields, crowding, etc…‐> important to determine feasibility and best TA strategy. ‐> If you consult a team member on PI question, do not involve PC or PI in this discussion to avoid confusion on their side as to who is the point of contact 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 7 II. Phase II Support CS/IS Responsibilities: Things to Remember! 4‐ Keep all exchanges in writing and copy all exchanges to the new history repository (e.g.: hstXXXXX@stsci.edu) 5‐ If phone exchange is inevitable (deadline crunch time typically): ‐> send email to the PI summarizing decisions made ‐> copy summary to history file and ‐> ask PI for email confirmation of agreement (should avoid future “blame game” situations) 6‐ Forward all AVAILABLE MODE requests and Change request to USER SUPPORT Leads (Paule & Nolan) for approval before phase II deadline. The PI has to specify exact configurations and scientific justification. 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 8 II. Phase II Support CS/IS Responsibilities: BOT Things to Remember! The BOT is only used to clear field stars. The ETC have to be used for science targets 1‐ Proposers need to run the BOT for all fields and all configurations (TA + SCIENCE) and they need to check the results! Null result does not mean SAFE! 2‐ Remind PIs to enter ETC IDs in APT form. The “warning” should not be ignored so that reviews can be expedited. 3‐ If field star is unknown or unsafe, additional information has to be provided by the PI and ETC or instrument handbook brightness limits should be used for clearance. 4‐ PI has to identify and share remaining issues and provide all supporting material at the time of submission. 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 9 II. Phase II Support Post‐Phase II Deadline Activities 1‐ Phase II deadline is nominally followed by one month for PC verifications reviews and one month for CS/IS reviews… 2‐ All CS/IS reviews without ongoing issues are expected to be completed by September 30th of each year to support the new cycle scheduling (subject to any other team priority directives) ‐> Early start for available proposals is recommended. 3‐ BOP Reviews are to be done expeditiously but not hastily‐ CS is sole judge of safety!! All doubts are to be cleared before program can be allowed to execute. Additional information has to be provided by GOs. ‐> If contentions arise, contact the USER SUPPORT Leads (Paule & Nolan) who will resolve them. 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 10 II. Phase II Support Post‐Phase II Deadline Activities 4‐ The USER SUPPORT Leads resolves all Verification (TAC compliance, duplications) and Change issues, for policy uniformity. These should be sent to the Leads only ‐> If you inadvertently receive any directly, forward them with recommendations to Nolan & Paule for resolution. 5‐ Moving target (MT) and Target of Opportunity (ToOs) programs cannot be completed until activated, but instrument specifications should be checked early to catch any issues. 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 11 III. Cycle 21 Highlights COS: Buffer Time BT is time it takes to fill one of two on‐board COS buffers Maximum counts in each Buffer = 2.35 x 106 counts BT(s)= 2.35 x 106 counts Global count rate (c/s) N.B: Global count rate has to include the following: ‐ source count rate ‐ counts from detector dark current & stim pulses (FUV) ‐ actual source counts factoring in QE and dead times BT given by ETC includes all factors => ETC value should be used to determine appropriate BT! 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 12 III. Cycle 21 Highlights COS: Buffer Time: Recommendations changes from C20 http://www.stsci.edu/hst/cos/documents/handbooks/current/ch05.COS_Spectroscopy05.html#426774 To minimize overhead when reading buffer Example: Texp =2300s BT2/3=700s BTETC x2/3 BT2/3 BT2/3 ≤ 80 sec Y N TEXP ≤ 80 sec Y N YA 80 < BT2/3 ≤ 110 sec YB N BT2/3 ≤ TEXP & BT2/3 > 110 sec YA YB N N= (2300‐110)s = 3.13 700s ACCUM BT2/3 > TEXP & BT2/3 > 110 sec Y BT2/3 = 80 sec BT2/3 = 2/3 x BTETC No data loss but smaller Texp TEXP = 2 x BT2/3 BT2/3 = 111 sec Data loss but full Texp BT2/3 = 2/3 x BTETC BT = (TEXP – 110)/N N = round[(TEXP‐ 110)/(2/3 x BTETC)] BT2/3 = 2/3 x BTETC => N=4 & BT=548s For Texp > 110s: we no longer require that BT2/3= Texp when BT2/3 > Texp 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 13 III. Cycle 21 Highlights COS: Blue modes and Segment=B If G130M/1055 or G130M/1096 and Segment=B, TAGFLASH is disabled the lamp does not provide counts below 1180Å. Users NEED to include GO wavecals in a specific sequence that will depend on their number of orbits per visit and FP‐POS usage. See June STAN 2013 and Steve Penton’s web link below: http://www.stsci.edu/hst/cos/documents/newsletters/cos_stis_newsletters/full_stories/2013_06/bm_detail ‐> APT will issue a warning for PIs using these configurations asking them to contact their CS for further advice. NB: The APT warning will remain after the wavecal have been inserted but the proposal can be submitted with the warning. ‐> SPAR flags visits with these configurations and reminds CS to check appropriate wavecal inclusions. 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 14 III. Cycle 21 Highlights COS: Blue modes usage with Segment=both (FUVA on) If there are any very deep 1055/1096/1222 observations where segment A is left "on" for very long exposures with significant count rates, we might want to look and see if they unnecessarily burning in the long wavelength end and extracting lots of charge. ‐> If you are the CS on one such proposal; bring the program to the attention of User Support Lead (Paule) 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 15 III. Cycle 21 Highlights COS: FP‐POS usage in regular modes 1‐ The use of multiple FP‐POS positions for each CENWAVE setting of the COS FUV/ G160M and especially FUV/G130M & FUV/G140L(1280) is required unless a strong scientific justification to do otherwise is provided in Phase I. ‐> APT issues a warning if all FP‐POS are not used in a visit for regular modes ‐> reduce impact of Lyman A Geocoronal lines on detector ‐> Improve S/N and Legacy value of archive NB: flexibility is allowed on a case by case basis NB: Blue modes with Segment =B need special treatment (see above). 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 16 III. Cycle 21 Highlights COS: FP‐POS =ALL and exposure times 2‐ Remind users that since Cycle 20, the exposure time entered in APT when setting FP‐POS=ALL is the exposure time for EACH individual FP‐POS. It is no longer the total exposure time (that APT divided into 4 equal sub‐exposures in previous cycles). As a result, PIs have adjusted the individual FP‐POS exposure times with the orbit planner. ‐> Check that the exposure times entered for each FP‐POS in APT/Phase II is consistent with scientific goals. (e.g for high S/N, need to have approximately equal Texp for each FP‐POS). 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 17 III. Cycle 21 Highlights OBSOLETE: work‐around was implemented June 13, 2013. COS: Target Acquisitions issues: 1‐ There is bug is the "Home Position" or "Global Variable" Bug of current flight software. This will not be fixed in the FSW until LV53 (March 2014). Until then, we will be using Alan's workaround which inserts dummy OSM rotations to get the appropriate variables set before executing TAs with the following settings: COS/FUV G130M/1309 CUS/NUV G185M/1850 ‐> CS should bring those programs to the attention of the User Support Lead (Paule & Nolan) 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 18 III. Cycle 21 Highlights COS: NUV Target Acquisitions and ETC revisions 2‐ NUV ACQ/SEARCH has been implemented in the ETC and is added to the existing ACQ/IMAGE ETC for Phase II. PIs who used the ACQ/IMAGE ETC algorithm to estimate their TA exposure time in Phase I might now find that their TA exposure time is significantly larger for faint objects when using the proper ACQ/SEARCH ETC algorithm + ACQ/IMAGE ETC algorithm. ‐> In such instances the PI is encouraged to contact their CS. The CS should then forward to the User Support Lead (Paule & Nolan) for resolution. 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 19 III. Cycle 21 Highlights STIS: E140M and E140H configurations: global scattered light contamination. Observations show that the Global Count Rate (GCR) for all FUV STIS Echelle configurations (E140H or E140M) is greater than the GRC given by the ETC. Example for 2 settings (calculations from Ayres and Debes) GCR for E140H/1416 is higher than the GCR given by ETC by 30% GCR forE140M/1425 is higher than the GCR given by ETC by 20% ‐> CS should bring all Cycle 21 proposals using those modes where the prediction global count rate is within 30% of the limit (or above 150000 c/s) to the attention of User Support Lead (Paule & Nolan). 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 20 III. Cycle 21 Highlights STIS: CTI warning in ETC global scattered light contamination. A new "feature" warning was added to the ETC at the request of ACS/WFC3 concerning CTI that is will appear for STIS/ACQ but is not appropriate for STIS. ‐> CS should tell their PIs they will have enough counts in the source that they won’t have to worry about the warning for their observations. 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 21 CS Reviews Tools 1‐ SPAR 1.13 tool is available: https://spar.stsci.edu ‐ Replaced the CS Toolbox since April 17th, 2012 ‐ Has the same functionalities as CS toolbox, but more flexible How to use it: a‐ login: same as AD; Password: same as AD b‐ Enter proposal version number in template b‐ Review template flags & check lists. d‐ save unready reviews if resolution is lengthy to support status tracking. e‐ SPAR now sends submitted review copies to all parties involved in review (CS + outsourced or backup) f‐ combined COS+STIS proposals require separate COS and STIS templates; Do immediate reviews of MT and ToOs, insofar as possible. g‐ COS Buffer time flag as been remove (BT> exposure time is obsolete now) 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 22 CS Reviews Tools 2‐ APT/BOT/Aladin Interface: 1‐ upload the proposal to review in APT (retrieve from STScI) 2‐ Select single visit or single exposure to be reviewed 3‐ click “BOT icon” on top menu bar in APT 4‐ Select GSC2, click “Update display” and check all results in the summary table 5‐ Select Galex, click “Update display” and check all results in the summary table. When relevant, activate “Proper Motion” feature and Repeat steps 4‐ and 5‐ 6‐ “ LOAD DSS”. The exposure(s) will appear as different planes in the order they are listed in the APT spreadsheet. Galex AIS plates are not accessible in Aladin too! 7‐ Macro‐apertures and stars are displayed when selecting exposure planes 8‐ A region selection allows display of details for enclosed star(s) in table at bottom of Aladin window 9‐ “Orient Ranges” in APT top menu allow display of specifications and U3 arrow. Grab arrow or corner to rotate. “Reset Orients” returns to original settings. 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 23 CS Reviews Tools 3‐ Galex database: AIS now available in Aladin! ‐ BOT screens all fields with AIS (all‐sky) survey coverage. ‐ BOT assumes all Galex sources are unreddened O5V stars. ‐> If targets do not violate local/global count rates they are declared “safe” ‐ BOT does not check for Galex coverage of the field to be cleared!! ‐> Need to check for coverage separately (using Galexview/Aladin, for instance). ‐ If no Galex coverage, no sources will be returned in summary table. Note that the result is the same when there are no sources but field is covered! ‐ Galex provides an upper limit to individual source flux because of low spatial resolution (4’’). If it clears, fine. If not, the source(s) may still be safe but required higher resolution data. HST images can be loaded in Aladin. No calculations will be done but blended sources can be resolved. ‐ Magnitudes between FUV=14.332‐12.6 and NUV=14.875‐10.2 are subject to saturation. Non‐linearity corrections are now applied by the BOT. Targets brighter than those limits are not to be cleared with Galex. 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 24 Final Remarks Programmatics: 1‐ The program review status is maintained on our COS/STIS User Support Page http://www.stsci.edu/hst/institute/org/ins/cos_stis/projects/UserSupport/Prop_review/cycle21/ 2‐ Lists of Urgent/verified proposals are distributed via emails under the “Weekly Report” banner and are circulated by User Support Leads weekly. Please abide by the “Review before” date. If delays occur, inform Lead (Paule & Nolan) of underlying reasons. 3‐ Track your review time: update to nearest hour each time a proposal is worked on and send final results to CS Lead. Do this continuously as reviews progress. 4‐ Transmit to User Support Leads notable cases of errors (corrected or not) and recommended improvements. These may be useful to other CS/IS. 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 25 Final Remarks Health and safety rules! ‐ All doubts are to be cleared before allowing observations! ‐ Work With GOs & PCs cooperatively on solutions and alternatives, but do not accept pressure! ‐ Do not hesitate to bring problem cases to the attention of the User Support Leads for resolution. Ultimately it is up to you to protect the instruments! Happy CS reviewing Season 2013! 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 26 IV. General Considerations Cycle‐Independent 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 27 CS Reviews Tools Tools: Major Resources 1‐ The SPAR Engine: 2‐ BOT/Aladin interfaces: called from HST Astronomers’ Proposal Tool (APT) Current Version: 20.1 ‐> update if needed! 3‐ Galex/GSC2/MCPS databases: to check field stars coverage: Need to be used if the BOT/Galex tool generates a warning about field empty or crowded http://galex.stsci.edu/GalexView/# http://ngala.as.arizona.edu/dennis/mcsurvey.html (MC survey) 4‐ ETC to verify health and safety of science targets for sure and unknown & unsafe field targets, if necessary. 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 28 CS Reviews Tools 3‐ GSC2 database: ‐ Contains 2 filters F and J to derive 1 color to 21‐22 mag over full sky. ‐ BOT calculates V and B‐V from J and F under conservative assumptions (all main sequence stars with no reddening). Since one color does not determine SpT and EB‐V , all stars with B‐V <+0.1 are treated/classified as O5V stars. All stars bluer than a given magnitude (spectral element dependent) are assumed O5V Beware: ‐ One or both filters have significantly brighter limits on some fields (Galactic Center and Magellanic Clouds) ‐ Resolution is inadequate in some fields; young regions in nearby Galaxy, extended regions. As a result, “unknown” and “unsafe” objects will require attention ‐ GSC2 omits stars within a substantial radius of very bright stars because of PSF artifacts. Star within saturated bright stellar or nebular images may be absent, requiring alternative sources 6/12/13 COS/STIS CS training ‐ P. Sonnentrucker 29 CS Reviews Tools 3‐ GSC2 database (continued): ‐ BOT now clears faint stars assuming they are unreddened O5V stars if only 1 filter is present as follows. ? #' #1' 2) $$ &2$A$*&+$&2$B$ A$*&+$&2$B$ @3 ? OKa %! 61).!KJ!dJ!%J!/ &%J!( <*!0$( ), < K, 0!, ' 4$5.)!G1.#!<, !dJ!( ))- > $!.#$!, ' 4$5.!1) @3 ? O^ a %! ( )
