Document 10585221
Cycle 20 CS Training
COS/STIS Instrument Team
Paule Sonnentrucker
&
Nolan Walborn
June 4, 2012
Technical Support: Svea Hernandez
OUTLINE
I.
IntroducCon
II.
Phase II Support: Timeline & ResponsibiliCes
III.
CS/BOP Reviews: Tools & Tasks
6/5/12 COS/STIS CS training -‐ P. Sonnentrucker 2
I. INTRODUCTION
Who We Are Officially:
“The Contact ScienCst (CS) is an Instrument ScienCst (IS) belonging to the
STScI team who supports calibraCon and use of the instrument(s) in the assigned programs.”
Our Official Role:
The CS provides advice on observing strategies:
1-‐ to meet the scienCfic objecCves of the program,
2-‐ to answer quesCons about instrument performance and
3-‐ to maintain the health and safety of the detectors subject to damage by over-‐illuminaCon: COS and STIS/MAMA
Our responsibility ends when the programs have completed!
Ref: hbp://www.stsci.edu/hst/proposing/docs/proposingOverview
6/5/12 COS/STIS CS training -‐ P. Sonnentrucker 3
I. INTRODUCTION
Our Goals and STScI expectaCons:
1-‐ Excellent support of HST science and users is the fundamental reason for the existence of the InsCtute and our scienCfic staff
2-‐ Support of GO program development and implementaCon as a primary point of contact between STScI and the astronomical community
3-‐ IS bring essenCal scienCfic and instrument experCse to this process, which complements that of the PCs/RIAs in scheduling and other technical issues
(helpdesk service)
Thus it is incumbent upon us to do our best from our perspecCves to ensure opCmum effecCveness and quality of HST observing programs and data.
6/5/12 COS/STIS CS training -‐ P. Sonnentrucker 4
II. Phase II Support
Timeline:
1-‐ TAC NoCficaCons sent out to Proposers: June 15
2-‐ CS/IS assignments and PI noCficaCons: June 18-‐22
3-‐ Phase I proposals sent to designated CS/IS: June 18 at latest
They are confidenCal.
4-‐ Phase II deadline: July 13, 2012
6/5/12 COS/STIS CS training -‐ P. Sonnentrucker 5
II. Phase II Support
PI ResponsibiliCes -‐-‐ We do not check the following :
1-‐ Deliver an error-‐free Phase II proposal
2-‐ Perform BOT reviews & and provide supporCng material to CS at
Cme of submission
3-‐ Provide ETC ID numbers in APT for ACQ & Science exposures
4-‐ Check target coordinates and proper moCon accuracy
5-‐ Check for duplicaCons
Refs: hbp://www.stsci.edu/hst/proposing/docs/proposingOverview & COS Instrument Handbook-‐ Chapter 10
6/5/12 COS/STIS CS training -‐ P. Sonnentrucker 6
II. Phase II Support
CS/IS ResponsibiliCes: Things to Remember
The advice we give is only as good as the informa5on we receive!
1-‐ Get familiar with the Phase I proposals once sent to you. Remember they are confidenCal.
2-‐ If contacted, do not hesitate to ask the PIs for details about sources, fields, crowding, etc…-‐> important to determine feasibility and best TA mode
3-‐ CS interact directly with PIs; IS do not but can if they so wish.
4-‐ Keep all exchanges in wriCng and copy all exchanges to the new history repository (e.g.: hst12000@stsci.edu
)
5-‐ If phone exchange is inevitable (deadline crunch Cme typically):
-‐> send email to the PI summarizing decisions made
-‐> copy summary to history file and
-‐> ask PI for email confirmaCon of agreement
(should avoid future “blame game” situaCons)
6/5/12 COS/STIS CS training -‐ P. Sonnentrucker 7
II. Phase II Support
CS/IS ResponsibiliCes: Things to Remember
The BOT is only used to clear field stars. The ETC has to be used for science targets!
1-‐ Proposers need to run the BOT for all fields and all configuraCons (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-‐ Remind them to provide all supporCng material at the Cme of submission
4-‐ If field star unknown or unsafe, addiConal informaCon has to be provided by the PI and ETC should be used for clearance.
5-‐ PI has to idenCfy and share remaining issues at the Cme of submission.
The detailed BOT procedures are in COS IHB: chapter 10: hbp://www.stsci.edu/hst/cos/documents/handbooks/current/ch10.Bright_obj7.html
6-‐ Review AVAILABLE MODE requests and forward issues/recommendaCons to CS Lead for approval before phase II deadline .
6/5/12 COS/STIS CS training -‐ P. Sonnentrucker 8
II. Phase II Support
Resources for ConsultaCons:
1-‐ Cycle 20 Phase II instrucCons-‐ P2PI.pdf: hbp://www.stsci.edu/hst/proposing/docs/p2pi.html
2-‐ COS and STIS STANS for latest technical updates: hbp://www.stsci.edu/hst/cos/documents/newslebers/
3-‐ Instrument Handbooks:
COS: hbp://www.stsci.edu/hst/cos/documents/handbooks/current/cos_cover.html
STIS: hbp://www.stsci.edu/hst/sCs/documents/handbooks/currentIHB/cover.html
4-‐ APT/BOT demos and movies.
APT general page: hbp://www.stsci.edu/hst/proposing/apt/using_apt
STIS: hbp://apst.stsci.edu/apt/external/help/documentaCon/Running-‐BOT.html
COS: hbp://apst.stsci.edu/apt/external/help/documentaCon/Running-‐COS-‐BOT.html
6/5/12 COS/STIS CS training -‐ P. Sonnentrucker 9
II. Phase II Support
Resources for ConsultaCons:
5-‐ APT/Aladin & Phase II Interface demos and movies: hbp://apst.stsci.edu/apt/external/help/roadmap2.html
hbp://apst.stsci.edu/apt/external/help/documentaCon/Aladin-‐PII.html
hbp://apst.stsci.edu/apt/external/help/documentaCon/Aladin-‐PosTarg.html
hbp://apst.stsci.edu/apt/external/help/documentaCon/Aladin-‐Pabern.html
6-‐ Galex Interface: to check field coverage and crowding: hbp://galex.stsci.edu/GalexView/#
NB: The Galex fields are directly accessible via the APT/Aladin interface
7-‐ GSC V2.3 is used. hbp://gsss.stsci.edu/Catalogs/GSC/GSC2/GSCIIProperCes.htm
A few facts (see Lasker et al. 2008):
Astrometry: Complete to V=19.5 mag, F=20.5 and J= 21.5 ; Ref frame ICRF; typical error: 0.3” (worst case is 0.35-‐0.75” at edges of plates).
Photometry: Errors 0.2-‐0.25 mag. For stars brighter than V=9 mag in GSCII, Tycho-‐2 mag is used.
6/5/12 COS/STIS CS training -‐ P. Sonnentrucker 10
II. Phase II Support
Post-‐Phase II Deadline AcCviCes
1-‐ Phase II deadline is nominally followed by one month for PC verificaCons/reviews and one month for CS/IS reviews -‐> Early start for available proposals is recommended. 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 direcCves).
2-‐ BOP Reviews are to be done expediCously but not hasCly : all doubts are to be cleared before program can be allowed to execute. AddiConal informaCon has to be
provided by GOs. CS is sole judge of safety! If contenCons arise, contact the CS Lead who will resolve them.
6/5/12 COS/STIS CS training -‐ P. Sonnentrucker 11
II. Phase II Support
Post-‐Phase II Deadline AcCviCes
3-‐ The CS Lead resolves all VerificaCon (TAC compliance, duplicaCons) and Change issues, for policy uniformity. These are sent to the Lead only. If you inadvertently
receive any directly, forward them to the CS Lead and Deputy.
4-‐ Moving target (MT) and Target of Opportunity (ToOs) programs cannot be
completed unCl acCvated, but instrument specificaCons should be checked early to catch any issues.
12
II. Phase II Support
ProgrammaCcs:
1-‐ The program reviews status is maintained on our COS/STIS User Support Page hbp://www.stsci.edu/hst/insCtute/org/ins/cos_sCs/projects/UserSupport/Prop_review/cycle20/
2-‐ Lists of Urgent/verified proposals are distributed via emails under the
“Weekly Report” banner and are circulated by CS Lead/deputy weekly. Please abide by the “Review before” date. When delays occur, inform CS Lead/Deputy of
underlying reasons.
3-‐ Track your review Cme: update to nearest hour each Cme a proposal is worked on
and send final results to CS Lead. Do this conCnuously as reviews progress.
4-‐ Transmit to CS Lead notable cases of errors corrected and improvements recommended that may be useful for other CS/IS.
6/5/12 COS/STIS CS training -‐ P. Sonnentrucker 13
III. 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 hbp://galex.stsci.edu/GalexView/#
hbp://ngala.as.arizona.edu/dennis/mcsurvey.html
(MC survey)
4-‐ ETC to verify health and safety of science targets
6/5/12 COS/STIS CS training -‐ P. Sonnentrucker 14
III. CS Reviews: Tools
1-‐ SPAR tool: hbps://spar.stsci.edu
-‐ Replaced the CS Toolbox since April 17
th
, 2012
-‐ Has the same funcConaliCes 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. c-‐ where appropriate answer YES/NO quesCons d-‐ where appropriate explain how your reach you conclusions in text boxes e-‐ submit completed template via SPAR f-‐ save unready reviews if resoluCon is lengthy to support status tracking.
NB: combined COS+STIS proposals require separate COS and STIS templates;
Do immediate reviews of MT and ToOs, insofar as possible.
6/5/12 COS/STIS CS training -‐ P. Sonnentrucker 15
III. CS Reviews: Tools
2-‐ APT/BOT/Aladin Interface:
1-‐ upload the proposal to review in APT (retrieve from STScI)
2-‐ Select 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, acCvate “Proper MoCon” feature and Repeat steps 4-‐ and 5-‐
6-‐ Click “ LOAD DSS” icon. The exposure(s) will appear as different planes in the order they are listed in the APT spreadsheet.
7-‐ Macro-‐apertures and stars are displayed when selecCng exposure planes
8-‐ Select region in display to see details of enclosed star(s); these listed in table at bobom of Aladin window; Place cursor on star and table entry flashes (and vice versa)
9-‐ Click “Orient Ranges” in APT top menu to display specificaCons and U3 arrow. Grab
arrow or corner to rotate. “Reset Orients” returns to original sexngs.
6/5/12 COS/STIS CS training -‐ P. Sonnentrucker 16
III. CS Reviews: Tools
3-‐ Galex database:
-‐ 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 spaCal resoluCon (4’’). If it clears, fine. If not, the source(s) may sCll be safe but required higher resoluCon data. HST images can be loaded in Aladin. No calculaCons 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 saturaCon. Non-‐linearity correcCons are now applied by the BOT. Targets brighter than those limits are not to be cleared with Galex.
6/5/12 COS/STIS CS training -‐ P. Sonnentrucker 17
III. 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 conservaCve assumpCons (all main sequence stars with no reddening). Since one color does not determine SpT and E
B-‐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 (GalacCc Center and
Magellanic Clouds)
-‐ ResoluCon is inadequate in some fields; young regions in nearby Galaxy, extended regions. As a result, “unknown” and “unsafe” objects will require abenCon
-‐ GSC2 omits stars within a substanCal radius of very bright stars because of PSF arCfacts.
Star within saturated bright stellar or nebular images may be absent, requiring alternaCve sources
6/5/12 COS/STIS CS training -‐ P. Sonnentrucker 18
!
!!
III. CS Reviews: Tools
!
!"!
"# #!$%$&!#!$%''() $ * " +!*!$%$&() $ * " + , !#!$%$,() $ * " + & !
%&!# "!$%-./!#!$%00.() $ * " +!
1!
!
234!567!8395674:!67;<8=6747!
3-‐ GSC2 database (conCnued):
%&!
!"!$%-./!
'# $%00.() $ * " +!
!#!$%$,() $ * " + & !
-‐ BOT now clears faint stars assuming they are unreddened O5V stars if only 1 filter is present as follows.
E:D!<8!D78A4<?7D!?7L3K%!
()*)+*,-##
CN>SGTU!
CN>SMTU!
.,#"#/.0#.,#$# "#/.0#.,#$#
L<85!GJ!HJ!UJ!V*UJ!E:D!47E83:!
G34!3?@7A58!K<56!:3!HJ!E889;7!567!3?@7A5!<8!
E8!W9:X:3K:WJ!8=7A54EL!5Y=7!
E:!N.U!85E4!)H*G"*$%',+!E:D!=43A788!
E8!W:3!A3L34!<:23W!
:34;ELLY%!!Z2!567!3?@7A5!D378!:35!54<II74!
E:Y!EL7458J!L<85!567!GJ!UJ!8=7A54EL!5Y=7!
)E889;7D!N.U+J!A39:5!4E578J!E:D!85E598%!Z2!
567!3?@7A5!D378!54<II74!E:!EL745J!L<85!567!GJ!
8=7A54EL!5Y=7!E8![:3!A3L34!<:23\J!E:D!
47E83:!E8![9:X:3K:\%!
Cf: COS ROBOT (May 2011) at: hbp://apst.stsci.edu/apt/apt-‐bright-‐objects/index.html
()*)+*,-##
!
.,#"#/.0#$##
G34!3?@7A58!K<56!:3!GJ!
E889;7!567!3?@7A5!<8!E:!
N.U!85E4!)H*G"*$%',+!E:D!
=43A788!:34;ELLY%!!Z2!567!
3?@7A5!D378!:35!54<II74!E:Y!
EL7458J!L<85!567!HJ!UJ!8=7A54EL!
5Y=7!)E889;7D!N.U+J!A39:5!
4E578J!E:D!85E598%!Z2!567!
3?@7A5!D378!54<II74!E:!EL745J!
L<85!567!HJ!8=7A54EL!5Y=7!E8!
[:3!A3L34!<:23\J!E:D!47E83:!
E8![9:X:3K:\%!
"#/.0#$1#.,*#/#2*/-#
C3;=957!567!U!;EI:<59D7!E8!5639I6!567!
3?@7A5!K747!E!85E4%!Z2!567!U!;EI:<59D7!<8!
2E<:574!56E:!E!A95322!FEL97!)K6<A6!<8!567!U!
32!E:!N.!85E4!<:!567!WK3485W!2<L574!47DD7:7D!
?Y!])V*U+"$%0!K6<A6!<8!@985!8E27^!<2!567!
3?@7A5!K747!47DD7:7D!L788J!567!3?@7A5!
K39LD!?7!547E57D!?Y!567!533L!E8!E:!N.!85E4+J!
567:!547E5!567!3?@7A5!E8!E!85E4%!O67!A95322!
FEL978!E47!GTU!)B-'$_+!-.%-'!E:D!MTU!
)5EX7:!243;!>OZ>S`P`P8+!-0%0%!
0%!
!
P2574!567!
!
!E:D!
%&!
!<8!D74<F7DJ!E!8E:<5Y!A67AX!8639LD!?7!=74234;7D%!!Z2!567!
!
!;EI*
:<59D7!<8!2E<:574!56E:!,'!34!?4<I6574!56E:!*,%$J!34!<2!567!
%&!
COS/STIS CS training -‐ P. Sonnentrucker
8=7A54EL!5Y=7!8639LD!?7!L<857D!E8
