STScI Logo

Hubble Space Telescope
Phase I: FUV Detector Dark Monitor

COS Cycle-18 Calibration Phase-1

Last Revised:	October 20, 2010
Proposal ID:	12423
Title: FUV Detector Dark Monitor
PI: W. Zheng
Co-I(s): C. Proffitt, R. Osten, D. Sahnow

---------------------------------------------------------------------------
# Orbit estimates are TOTAL for all of cycle-18; assume 52 weeks) 

Total Prime Orbits:             0
External Parallel Orbits:       0
Internals or no-impact orbits:  130
Comments on orbit estimate:     5 orbit visits, repeated bi-weekly

---------------------------------------------------------------------------
# This section should be written with a GO audience in mind -- use 
# Calibration plans in COS handbook as a guide.

Purpose:                        
Perform routine monitoring of FUV XDL detector dark rate. The main purpose is 
to look for evidence of a change in the dark rate, both to track on-orbit time 
dependence and to check for a detector problem developing.
                  
Description:
Monitor the FUV detector dark rate by taking TIME-TAG science exposures with 
no light on the detector. Five times every two weeks a 22-min exposure is taken with 
the FUV detector with the shutter closed. The length of the exposures is chosen 
to make them fit in Earth occultations.

Accuracy:   Obtain a few counts per exposure (for nominal case). Build up decent 
	    S/N over time.
Comments on Accuracy: 
Products:   Dark rate reference files, ISR


---------------------------------------------------------------------------
# Link to Cycle 18 Science
# Use the GO + GTO Phase 1 exposure  listing and derived statistics
# posted on WWW.

Fraction of science programs supported by this calibration:     ~75% of COS

List categories of science which can't be executed until after this proposal:
why:

List categories of science which are best performed contemporaneous with 
this proposal:
why:


---------------------------------------------------------------------------
# THE REST OF THIS FORM IS FOR INTERNAL USE
---------------------------------------------------------------------------
Observation summary: 


# Target information (copy for each target)

Target Name.............................:	DARK
RA......................................:	N/A
Dec.....................................:	N/A	
Flux (and units)........................:	N/A	
Visibility window (if known or relevant):	N/A
Comment on choice of target:			N/A

# Exposure list plan at the Phase I level. Be as complete as reasonable. 
# If possible information should be complete enough to allow easy 
# submission of a Phase 2 from this form. However, if you have to leave
# some of the fields blank below, or want to provide the information
# in another format, that is acceptable. (Make sure you do the BOP checking
# though, as this is a phase-1 issue.)

Table of exposures (copy for each exposure as appropriate/desired):

Target or lamp..........................: DARK
Type of Acquisition.....................: None
Detector for observation................: COS FUV
Operating mode .........................: TIME-TAG
Spectral Element........................: DEF
Aperture................................: DEF
Central Wavelength......................: 
Exposure Time...........................: 1330
Number of Iterations ...................: 5
BOP Predicted Local Count Rate for MAMA.:
BOP Predicted Global Count Rate for MAMA:
ETC PID IDs for Count Rates.............:
Special Requirements or options.........: Avoid SAA if possible
Comments: (e.g. if monitoring, specify frequency) 


---------------------------------------------------------------------------
# Special needs of this proposal?

Scheduling: 

Prerequisites: N/A

PDB update?  No
On-board table update?    No

# Special Requirements:
Real time?                N
Special commanding?       N
Quick Data turnaround?    N
Special timing required?  N
Other?                    N
Describe (& justify) special requirements:


-------------------------------------------------------------------------
# Analysis Plan

Expected FTE weeks for analysis:                                4
Required turnaround on analysis (weeks):                        0
Data volume (Mb needed for analysis):                           0
Special software needed for analysis? (Describe):

Description of analysis Plans:	 

Use IDL scripts to identify and exclude SAA regions. Check hot pixels.
Derive the dark rate and produce combined dark images.