#
#
#    #########################################
#    ##                                     ##
#    ##    FUSE Phase 2 Proposal Template   ##
#    ##                                     ##
#    ##    for Use in Cycle 2, 10/4/2000    ##
#    ##                                     ##
#    #########################################
#
#  Refer to FUSE Cycle 2 Phase 2 Instructions for details.
#

# Proposal Identification
prog_id:	
title: 		
t_alloc_total: 	        # Ksec
t_alloc_orb:            # Orbits, for French programs only.


#    ######################
#    ##                  ##
#    ##  PI Information  ##
#    ##                  ##
#    ######################

pi_title:       
pi_first_name:  
pi_last_name:   
pi_affiliation: 
pi_institution: 
pi_address:     
pi_country:     
pi_phone:	
pi_fax:         
pi_email:       


#    ######################
#    ##                  ##
#    ##  LI Information  ##
#    ##                  ##
#    ######################

# Optional, if Program PI designates a separate primary contact person.

li_title:	
li_first_name: 	
li_last_name:	
li_affiliation: 
li_institution: 
li_address:     
li_country:     
li_phone:	
li_fax:		
li_email:	

#    ########################
#    ##                    ##
#    ##  COIs Information  ##
#    ##                    ##
#    ########################

# COI - 1, repeat as necessary for other Co-Is.
coi_title:		
coi_first_name:		
coi_last_name:		
coi_institution:	
coi_country:     
coi_phone:       	
coi_email:       	


#    ############################
#    ##                        ##
#    ##  Proposal Information  ##
#    ##                        ##
#    ############################
#
#  NOTE: Although not required, keeping text block lines to 80 character
#  or less will prevent line wraps and improve readability in the formatted
#  output.  Flat ascii text is much preferable to LaTex commands.

#  -------------
# |  Abstract   |
#  -------------

abstract_text:

#ENTER ABSTRACT TEXT HERE.

#  --------------------------
# |  Feasibility and Safety  |
#  --------------------------

feasibility_text:

#ENTER FEASIBILITY AND SAFETY DISCUSSION HERE.

#  ------------------
# |  Special Reqs.   |
#  ------------------

spec_req_text:

#ENTER DISCUSSION OF SPECIAL REQUIREMENTS KEYWORDS SPECIFIED HERE.

#  ------------------
# |  Support Info.   |
#  ------------------

support_info_text:

#ENTER ANY OTHER RELEVANT SUPPORTING INFORMATION HERE.


#
# Object-specific Information
#
#  Note: Keywords are on uncommented lines, terminated with a colon.
#  ENTER INPUTS TO THE RIGHT OF THE COLON for each relevant keyword (NOTE
#  NOT on the following line!  The blank lines below are for readability only!).
#  Comments or example formats are listed above each item (to prevent
#  line wraps in the electronic submission).  After the fact, comment lines
#  may be deleted if you wish. 
#
#  Also, you may add other comment lines at will, so long as each comment line
#  begins with a pound sign and is <=80 characters in length.  However, any 
#  such lines are for YOUR BENEFIT ONLY and are not part of your official 
#  submission. (Only uncommented lines are visible to the Parser and carried
#  forward into the database.)
#
#  Repeat the following keywords as necessary for each separate target.
#  Optional keywords may be left blank or dropped entirely.
#
#
#    ############################
#    ##                        ##
#    ##  Object 1 Information  ##
#    ##                        ##
#    ############################

# Object number,  1-99
object_number:  

# Object Name, from Phase 1 when possible. [NO SPACES]
object_name:  

# Numerical Object Class, from listing in Appendix B.
object_class:  	

# Object-level special requirements; MOVE, TOO, NIGHT
object_spec_req:     

# RA and Dec in J2000 
# Use format 20:31:45.22 and +31:02:01.5 (incl. colons)
ra_j2000:  
dec_j2000:  

# Two-letter source type designation, PC, PE, EC, EE 
source_type:  	

# Reference wavelength in Angstroms, e.g. 1032.0
lambda_ref:  	

# Reference flux in cgs units, Example  1.2E-12 [NO SPACES]
flux_lambda_ref:  	

# FWHM of emission line, in Angstroms, e.g. 0.5
eline_fwhm:   	

# "flux" per sq. arcsec; extended sources only.
sb_lambda_ref:  

# Equiv. Cont. Fluxes at 950, 1050, and 1150 A, e.g. 1.2E-12
flux_950:     
flux_1050:    
flux_1150:    

# Flux accuracy, HIGH, MED, LOW; see Phase 2 Instructions.       
flux_accuracy: 		

# V magnitude in magnitudes, e.g. 12.5
v_mag:		

# mag range, for variable sources only, e.g. 9.9-13.2
v_range:	

# Resolution element (for S/N calc); in Angstroms, e.g. 0.033
resolution_element:  	

# total expected cts/s, pref. from ETC/CRT or simulated spectrum
expected_ct_rate:

# Channel assumption for S/N calculation.  Legal entries are
# TOTAL, LIF1, LIF2, SIC1, or SIC2; see Phase 2 Instructions.
sig_noise_chan:    

# Calculated S/N per specified res. element.
sig_noise: 	

# Spectral type (if appropriate) [NO SPACES]
spectral_type:	

# E(B-V) in magnitudes, e.g. 0.10
color_excess:  		

# Source redshift, Z format or km/s, as appropriate.
red_shift:

# High proper motion flag; Y if you applied a PM correction to 
# coordinates above.  Blank or N otherwise.
high_prop_motion:	 

# Target priority within program, 1 or 2; use 4 for offset stars.
object_prio:	

# Phase zero point and period (see Phase 2 Instructions); 
# Only needed for EPHEM.
phase_zero:   	
phase_period:   


#
#    #########################################
#    ##                                     ##
#    ##   Object Obs-specific Information   ##
#    ##                                     ##
#    #########################################
#
# Repeat as needed to specify additional observations of a given target.
# The `observation_num:' keyword must be first for each new observation.
#
# As with above, comments and format examples given preceding each line. 
# These comments may be deleted if you wish.
#

# Observation number, 1-99, or `1 TO N' if MON.
# Starts with 1 for each new object.
observation_num:    

# `object_number' of target for this obs. 
obs_object_num:     

# `object_number' of offset target, if any. 
off_object_num:     

# Instrument mode; HIST, or TTAG
instrument_mode:    

# Aperture for Science; HIRS, MDRS, LWRS
aperture_req:    

# observation time in seconds, e.g. 20000 (no commas) 
# NOTE: "per observation" for MON.
obs_time_req:     

# Observation-level special requirements. (More than one? String out
# on one line with commas between.
# ROLL, SNAP, SAFTSNP, MON, EPHEM, HOLD, SPATIAL,
# CONTIG, CVZ, COORD, and/or FESIMG. (See Phase 2 Instructions.)
obs_spec_req:   

# If ROLL special reqm't; position angle and tolerance,
# in decimal degrees, e.g. 15.0
aperture_pa:                   
pa_tolerance:      

# If MON special reqm't; separation and tolerance on separation,
# in decimal days, e.g. 21.00
mon_t_sep:    
mon_delta_tsep:    

# If EPHEM special reqm't; desired phase (betw. 0.0 and 1.0) and
# phase tolerance; e.g. 0.5 and 0.05
phase_desired:    
phase_delta:    

# If FESIMG special reqm't; IN or OUT
targ_pos:     


#  Duplicate above lines as necessary for additional targets and/or 
#  observations.  Comment lines are optional, and can be added
#  or deleted at will.
#
#  End of form.