% FUSE Phase 1 observing proposal LaTeX template  (version 8.4)
% For Cycle 8
%
% Revision date: August 31, 2006. (B-G)
%
% WHAT, WHERE, AND WHEN TO SUBMIT YOUR PROPOSAL
%-------------------------------------------------------------------------
%  Changes in and reminders for this version: 
%
%	1) For Cycle 8 proposals, submission through the NSPIRES system at 
%          NASA, including both cover-page information and the full scientific 
%	   justification is now mandatory for ALL proposers.  
%	   The filled in LaTeX form (this file) must still, also, be submitted 
%	   to fuseprop@pha.jhu.edu
%	   Non-US proposers whose institutions are not registered in the 
%          NSPIRES database may use the "FUSE GI Support Center" as their 
%          proposal submitting organization (see the Phase 1 Instructions).
%
%       2) A new keyword, \targtype{}, has been introduced in Cycle 8.  This
%          keyword is used to identify targets of differing scientific priority
%          as well as low declination targets.
%
%	3) No user constrained observations are allowed in cycle 8.  Hence
%          all Special Requirements (SR) keywords, except TOO, FPSPLIT, SNAP 
%	   and SAFTSNP have been removed.  With respect to the Target of 
%	   Opportunity (TOO) SR note that the response time and observation 
%	   characteristics have changed from previous cycles. 
%          (Please see the NRA for details at /http://fusegi.pha.jhu.edu ).
%
%	4) In the "NASA proposal Number" keyword \nasapropno{}, please enter 
%          the FULL STRING returned by NSPIRES when you submitted the cover 
%          page.
%               
%--------------------------------------------------------------------------
%
% With the introduction of the NSPIRES system at NASA Peer Review Services,
% there are important differences from previous FUSE cycles in the proposal 
% submission procedures.
% Submittal of the full proposal, including both the web-generated Proposal 
% Cover Page as well as the full formatted proposal (.pdf form) is now required
% for all proposers.
% More information about using the NSPIRES system for FUSE Cycle 8 proposals 
% is available on the FUSE GI web site (http://fusegi.pha.jhu.edu).
%
% A complete proposal submission consists of three steps:
%
% 1) Fill in the Cover Page/Proposal Summary and upload the formatted proposal 
%    through the NASA Peer Review Services web site at:
%
%          http://nspires.nasaprs.com
%
%    Please note that THIS SUBMITTAL CANNOT BE DONE BY THE PI, but must be done 
%    by an Authorizing Official at your institution.  
%    Prior to this step, your institution must register at the NSPIRES site.
%    Please make sure you leave enough time before the proposal deadline
%    to accomplish the required set-up and review/administrative steps.
%
% 1b) (Non-US PIs) For non-US proposers, whose institutions are not registered 
%     with NSPIRES, the role of the submitting organization will be filled by
%     The "FUSE GI Support Center" and the Authorizing Official will be 
%     the FUSE Project Scientist, George Sonneborn, or his designee.
%
% NOTE - You must register and log in to your NSPIRES account to fill in the
%    Cover Page or NOI, and to upload the formatted proposal, so don't delay 
%    until the last week before the deadline.
%
%
% 2) Release the proposal to your institution's Authorizing Official and have 
%    them formally submit it to NASA.
%
%
% 3) Email the completed LaTeX proposal form (this file) to
%   fuseprop@pha.jhu.edu
%
%    Submission of the LaTeX proposal form is REQUIRED for all Guest 
%    Investigator proposals.
%
% Note that for Cycle 8, hard-copy submission is no longer required 
% (or accepted).
%
% The preferred method of preparing the formatted submission is to process the 
% LaTeX form provided below (together with the "fuse8.sty" file).
% However, users may prepare their formatted proposal using other tools,
% as long as the formatting strictly follows the instructions in section 2
% of the FUSE NRA.  In any event, the ASCII LaTeX form, provided herein, MUST 
% BE FILLED OUT AND SUBMITTED BY EMAIL regardless of the method used to
% prepare the formatted proposal.
%
% Please see the NRA for the Cycle 8 proposal due date.
%
%
% INSTRUCTIONS
%---------------
% Detailed instructions for filling out this proposal form can
% be found at the FUSE GI website (http://fusegi.pha.jhu.edu)
% in a document called "FUSE Phase 1 Proposal Instructions" updated for Cycle 8.
%
% LATEX
%---------
% All of the information to be provided in the form below should
% be inserted within the curly braces "{}", or as text blocks
% after a template keyword (a keyword is preceded by a backslash 
% character; example, \justification).  Comment lines start with
% the "%" sign and can be added at will, but will NOT show up in the
% formatted proposal or be processed by FUSE Mission Planning software.  
% You may remove any explanatory comments in this file or leave them in,
% as you wish; they are here only for your convenience.
%
% PostScript figures may be included in the formatted output by using
% the \plotone command.  Insert the following into your LaTeX file:
%   \begin{figure}[h]
%   \plotone{foo.eps}
%   \caption{}
%   \end{figure}
% where "foo.eps" is an Encapsulated PostScript file you have created.
% The figure will be scaled to a width of 95% of the width of the text.
% If you have a tall, narrow figure, you can scale it to a smaller
% fraction of the text with with \epsscale{fraction}.  For example:
%   \epsscale{0.5}\plotone{foo.eps}
% scales the figure to half of the text width.  Use \plottwo to plot
% two figures side-by-side, as in
%   \plottwo{foo1.eps}{foo2.eps}
%
% NOTE -  Please do not use colons in any text blocks in the proposal
% (such as "Scientific Justification", "Feasibility and Safety", etc.), 
% as this causes problems when interpreted by the parser software.  Colons
% are required inside the coordinate key-words \ra{} and \dec{}
%
% Proposers who wish to incorporate graphics using other techniques
% (e.g., with the commands provided with the Latex 2e graphics package,
% with the PSFIG macros, etc.) are free to do so, but JHU cannot provide
% any support or advice to those who choose these approaches.
%
% DO NOT submit the postscript figure with your LaTeX proposal file via 
% email!  Only the LaTeX file is needed for parsing into a database.
%
% For more information on LaTeX, see the LaTeX manual by Leslie Lamport,
% "LaTeX, A Document Preparation System, User's Guide and Reference Manual",
% 1994, Addison-Wesley Publishing Company.
%
%----------------------------------------------------------------------
% LaTeX template begins here:  Numbered headings correspond to listing
% of detailed instructions in section 3 of the Phase 1 Proposal 
% Instructions document.
%----------------------------------------------------------------------
% DO NOT DELETE THE NEXT TWO LINES
\documentclass[12pt]{article}
\usepackage{fuse8}

% If you want to add any personal LaTeX definitions, please add them 
% here before the \begin{document} command

\begin{document}

% 1. Proposal Title
% The program's title should be as short and descriptive as possible 
% and should be no more than about 100 characters. Enter between the
% curly braces.

\title{}   % (Required)

% 2. NASA Proposal Number
% Enter the complete proposal identification number assigned to your proposal
% (e.g. \nasapropno{06-FUSE8-123}) by the NASA Peer Review Services web site.

\nasapropno{}   % (Required)

% 3. Principal Investigator Contact Information. (All Fields Required)

% Please supply the requested contact information for the PI 
% All fields should be supplied for the PI, who is assumed to be 
% the primary point of contact for any questions about the program.

% Title (Dr., Mr., Ms., Prof., etc.)
\pititle{}		

% First name (John, or John G. to include initial)
\pifirstname{}		

% Last name   
\pilastname{}		
 
% Affiliation (Department of Astronomy, etc.)  
% Note that non-US proposers using the "FUSE GI Support Center" as the 
% Submitting Organization for NSPIRES should still list their nominal home 
% institution in this form. 

\piaffiliation{}	
 
% Institution (your university or institute name)
\institution{}		
 
% Address (123 East St., Baltimore, MD 21218)
\address{}		
 
% Country abbreviation (USA, UK, CAN, FRA, etc.)
\country{}		
 
% Telephone number, including country code if non-North America
\phone{}		

% FAX number
\fax{}			

% e-mail address (you@somewhere.anywhere.edu)
\email{}		

 
%
% 4. Scientific Category  (Required)
% Select a single scientific category for your proposal from the choices
% given below by uncommenting the appropriate category.
% This category will be used in scientific peer review panel assignment. 

%\scientificcategory{COOL STARS AND PROTOPLANETARY SYSTEMS}
%\scientificcategory{WHITE DWARFS AND CATACLYSMIC VARIABLES}
%\scientificcategory{HOT STARS AND MASSIVE BINARIES}
%\scientificcategory{STELLAR EJECTA AND GASEOUS NEBULAE}
%\scientificcategory{INTERSTELLAR MEDIUM AND GALACTIC STRUCTURE}
%\scientificcategory{GALAXIES, AGN AND QUASARS}
%\scientificcategory{INTERGALACTIC MATERIAL}
 
%
% 5. Observing Program Category  (Required)
% Each Cycle 8 proposal must be identified as either a "Standard" or "Survey"
% proposal.  Standard proposals correspond to regular observing programs and may
% contain constrained observations (see NRA Section 1.2).  Survey
% proposals provide the opportunity to observe a class of objects without the 
% requirement that a specific target be observed.  No constrained observations 
% are allowed in Survey programs, and all targets must be at |dec|>50 degrees.
% THE SELECTED CATEGORY MUST APPLY TO ALL TARGETS IN THE PROPOSAL.
% Select a single category for your proposal from the choices given below by 
% uncommenting the appropriate category.

%\programcategory{STANDARD}
%\programcategory{SURVEY}

% 6. Observation Summary Information
% The `totalobstime' is the total requested on-target integration time in
% kiloseconds for all targets in the program. (See notes in the Phase 1
% Proposal Instructions on handling short exposure times and SAFTSNPs.)  
% The `totalobjects' keyword indicates the number of independent positions 
% on the sky you wish to observe. (Multiple positions in extended sources 
% should be counted as separate targets, but moving targets should be 
% counted as one target.) 
%

% Total observing time, in Kiloseconds
\totalobstime{}    % (Required) 	

% Total number of objects
\totalobjects{}	   % (Required)
	
% 7. Abstract   (Required, text block) 
% Enter a brief description of up to 200 words between the \begin{abstract}
% and \end{abstract} keywords summarizing your program's goals.

\begin{abstract} 	
 
\end{abstract}
 

% 8. Co-Investigator Information  (Required for all Co-investigators)
\begin{investigators}

% List each Co-Investigator (CoI) by replicating the following seven
% items for each CoI. If you have no CoIs, leave these lines unchanged.

\coititle{} 	
\coifirstname{}	
\coilastname{}
\institution{}
\country{}
\phone{}
\email{}

\end{investigators}
 

% 9. Scientific Justification.  (Required, text block) 
% Enter text after the \justification keyword.  Describe the scientific
% justification for the proposed program, stating clearly its goals and
% significance to astronomy. You should include a brief discussion of
% scientific background, previous work, and why FUSE data are needed to
% address your goals. The Scientific Justification is limited to three
% pages for standard and survey proposals including figures, tables, 
% and/or references.  
% PLEASE DO NOT USE ANY COLONS IN ANY TEXT FIELD.

%  <=3 pages, including figures, tables and refs.

\justification    

 
% 10. Feasibility and Safety.  (Required, text block)
% Enter text after the \feasibility keyword.  Discuss in detail your
% signal-to-noise calculations and resolution requirements for your proposed
% observations.  Mention explicitly whether the S/N values listed in your
% target table pertain to a single channel or the total data set.  Describe 
% the quality of your flux estimates, including how you extrapolated into the 
% FUSE wavelength range. Describe explicitly any targets or situations that 
% may create concerns for instrument safety. Describe your method of 
% estimating the necessary exposure times for your targets. 
% Up to 2 pages single spaced can be used for this section.   
% PLEASE DO NOT USE ANY COLONS IN ANY TEXT FIELD.

%  <=2 pages
\feasibility      

 
% 11. Description of Observations.  (Optional, text block)
% Enter text after the \describeobservations keyword.  Up to one page of
% additional description is permitted here to address any "strategy
% issues" on how the observations should be performed, including discussion
% of Special Requirements or special scheduling issues.  If you request use
% of the MDRS aperture, discuss explicitly your requirements with regard to
% short wavelength (SiC channel) coverage in your spectra. (See Phase 1
% Instructions document for more information.)
% PLEASE DO NOT USE ANY COLONS IN ANY TEXT FIELD.

%  <=1 page
\describeobservations  
 

% 12. Additional Information.  (Optional, text block)
% Enter text after the \additionalinfo keyword.  Up to one page of text can 
% be supplied here to describe anything else about your proposed program 
% that  is relevant or that the review panel should know (such as data 
% analysis  plans, justification for any coordinated observations, etc.).
% PLEASE DO NOT USE ANY COLONS IN ANY TEXT FIELD.

%  <=1 page
\additionalinfo   


% 13. Previous FUSE Observing Programs.  (Optional, text block)  
% Enter text after the \previousfuseprograms keyword.
% Summarize the status of and the results and publications
% arising from FUSE observing time allocated to the PI in
% previous observing cycles.  The presentation of this
% information for Co-Is is optional.  Up to one page,
% including text and figures.
% PLEASE DO NOT USE ANY COLONS IN ANY TEXT FIELD.

%  <= 1 page
\previousfuseprograms  


% 14. Investigator Information.  (Optional, text block)
% Provide a short biographical sketch for the PI, including
% recent publications relevant to this proposal.  Relevant
% information about co-investigators may also be included
% here at the proposer's discretion, but the total length
% of this section must not exceed 1 page when formatted.
% PLEASE DO NOT USE ANY COLONS IN ANY TEXT FIELD.

% <= 1 page
\vita   


%---------------------------------------------------------------------- 
% 15. Target List and Observation Summary
%----------------------------------------------------------------------
% Please provide information for all targets to be observed.  Repeat
% the set of keywords below for each target.  In the formatted proposal,
% this information will come out in tabular format on a separate page or
% pages at the end of the formatted proposal. (Extra comment lines can be
% dropped at the user's discretion.) There are no explicit limits on the 
% length of this section.

\begin{observations} 

% Repeat this set of keywords for every target
% See the Phase 1 proposal instructions for detailed description of 
% each keyword.

% see Appendix A of Phase 1 instructions for conventions
% NOTE THAT THERE MUST NOT BE ANY SPACES IN THE TARGET NAMES.
\objectname{}   % (Required)	

% Should be in the form HH:MM:SS.SS (J2000 equinox)
\ra{}	   % (Required)			

% Should be in the form DD:MM:SS.S  (J2000 equinox)
\dec{}	   % (Required)			

% Visual magnitude, Johnson V magnitude preferred
\vmag{}	   % (Required)			

% Enter a spectral type. For stars, provide the MK spectral type 
% and luminosity class (no spaces! example: O7Ve).  
% For non-stars use one of the following:  
% QSO, AGN, GAL, SOL, CV, PN, SNR, CSPN, PSR, REF, CLU, OTR.
% (CLU=cluster of galaxies; OTR=other)
\spectype{} 	   % (Required)            

% Measured E(B-V)
\colorexcess{}	   % (Optional)	

% Source type:  (uncomment only one)	 (Required)
%\sourcetype{PC}   	%   Point Continuum 
%\sourcetype{PE}   	%   Point Emission-line
%\sourcetype{EC} 	%   Extended Continuum
%\sourcetype{EE} 	%   Extended Emission-line

% Reference wavelength in Angstroms
\lambdaref{}	   % (Required)		

% Estimated, observed, flux value at wavelength \lambdaref. in erg/cm2/s/A  
% Example: \fluxlambdaref{1.5e-12}
% NO TeX formatting allowed in this keyword.
\fluxlambdaref{}	   % (Required)	

% Flux estimate accuracy: (uncomment one) (Required)
%\fluxaccuracy{HIGH}	%   HIGH
%\fluxaccuracy{MED}	%   MED
%\fluxaccuracy{LOW}	%   LOW

% Info for emission line or extended objects.
% Uncomment next 2 keywords if they apply:

% FWHM of line in Angstroms for emission line objects
%\elinefwhm{}	%(Required for \sourcetype = PE and EE)	

% Surface brightness at wavelength \lambdaref in erg/cm^2/s/A/arcsec^2.  
% (Required for \sourcetype = EC and EE)
% Example: \sblambdaref{1.2e-15}
% NO TeX formatting allowed in this keyword.
%\sblambdaref{} %(Required for \sourcetype = EC and EE) 	

% Size of resolution element in Angstroms
\resolutionelement{} 	   % (Required) 	

% Channel used to calculate the S/N: SIC1, SIC2, LIF1, LIF2, or TOTAL
\signoisechan{}		   % (Required)	

% Expected S/N per resolution element
\signoise{}	   % (Required)		

% Aperture: (LWRS is default.  Change by commenting out LWRS and 
% un-commenting other.  Only one must be un-commented.)
% (Required)
%   LWRS (30"x30") (Default)
\aperture{LWRS}   	
%   MDRS (4"x20")
%\aperture{MDRS}   	
%   HIRS (1.25"x20")
%\aperture{HIRS}   	

% Special requirements: (uncomment all keywords that apply)
% See phase 1 proposal instructions for details
% (Optional, as needed)
%   Target of opportunity, including low declination targets.
%\specialreq{TOO}	
%   FPSPLIT observing procedure required (high S/N observation)
%\specialreq{FPSPLIT}
%   Short exposure (snapshot) before followup
%\specialreq{SNAP}	
%   To highlight potential bright object violations
%\specialreq{SAFTSNP}   
	
% Target type: To allow a more direct identification of the most important 
% targets for FUSE to observe in Cycle 8, the keyword \targtype{} has been 
% added.  This keyword is also used to identify low declination targets to be
% observed if and when this capabillity is again available.
% The four options are A: the scientifically most important targets,
% which will be allowed to drive the FUSE scheduling and may significantly 
% impact the observing efficiency.  Only a limited number and total exposure 
% time will be allowed of this target type.  B: Regular STANDARD program-
% category targets, C: targets below the nominally accessible Declination 
% range (|dec|>50deg) and D: SURVEY program-category targets.
%
% Change by commenting out B and un-commenting other. (Only one must be 
% un-commented.)  For STANDARD program-category proposals a mix of target 
% types A & B is allowed.  For SURVEY program-category proposals only target-
% type D is allowed.
%
% Target Type  (Required)
%
%\targtype{A}  	
\targtype{B}   	
%\targtype{C}   	
%\targtype{D}   	

% Desired integration time, in seconds (per visit).  For SAFTSNPs, enter 
% 2000 sec here.  For short science observations enter time needed to 
% achieve listed S/N.   See Phase 1 Proposal Instructions for more info.
\integrationtime{}	   % (Required)    	

%---------------------------------------------------------------------
% Repeat the above information as needed for each target/observation.
% (Note: grab 90 lines starting with \objectname{} if no comment lines 
% have been dropped.) 
%

\end{observations}

\end{document}