% Begin file here % % NOTE: This template has only extremely minor changes from Cycle 3. % The style file it calls is gross overkill for what is now needed for GALEX proposals % (leftover from earlier cycles). % However, we provide it for those proposers who may wish to resubmit a Cycle 3 % proposal with only modest changes. % To convert a Cycle 3 to a Cycle 4 proposal, comment out the line about Proposal % Number, (" nasapropno" ) and % change the style file to galex4.sty. % % % GALEX Phase 1 observing proposal LaTex template (version 1.0) % Closely adapted from FUSE Phase 1 LaTex template (version 5.0) % % Date - 7 November, 2003. (SGN) % Revised - 14 February, 2004 (SGN) % 23 March, 2004 (SGN) (text only, not function) % 17-19 March, 2005 (SGN) (for Cycle 2) % 25 April, 2006 (JEH) (for Cycle 3) % 10 May, 2007 (SGN, for Cycle 4) % % % % WHAT, WHERE, AND WHEN TO SUBMIT YOUR PROPOSAL %------------------------------------------------------------------------- % %See iinformation at: % http://galexgi.gsfc.nasa.gov/propforms/ProposalChecklist.html % % First, perform various target checks as outlined in the checklist. % Then, the complete Phase 1 proposal submission consists of the % following steps. % % 1) Fill out either this LaTeX proposal template, the Word proposal % template, or make one of your own that follows guidelines and page % limits given in long NRA. Use to produce a .pdf file. % % 2) Fill out cover and observation (target) forms on RPS/AKBAR, verify, and Submit. % http://heasarc.gsfc.nasa.gov/akbar/ % % % 3) In AKBAR, go to "Recent Activity" Page, click on the "Files" button, and % upload your GALEX proposal .pdf file % % % % Please see the GALEX GI website for the due date for submitting the % Cycle 4 Phase 1 PDF justification and the AKBAR forms. % % % 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 GALEX 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{} . If your text % requires the use of a colon, you can use the latex % $\colon$ % % % 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 GALEXGI % cannot provide any support or advice to those who choose these approaches.. % % % 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. % ( http://galexgi.gsfc.nasa.gov/propforms/index.html ) %---------------------------------------------------------------------- % DO NOT DELETE THE NEXT TWO LINES \documentclass[12pt]{article} \usepackage{galex4} % 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. 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{} % 3. NASA Proposal Number %Please see http://galexgi.gsfc.nasa.gov/propforms/ProposalChecklist.html %for instructions on how to obtain a proposal number. %\nasapropno{} % NOTE: Complete Cover Page information such as the abstract, CoI % information, etc. will be collected in the xml target list template. % % 3. 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 GALEX data are needed to % address your goals. The Scientific Justification is limited to three % pages for standard and survey proposals and five pages for Legacy % proposals, including figures, tables, and/or references. % PLEASE DO NOT USE ANY COLONS IN ANY TEXT FIELD % (use $\colon$ ). % PLEASE DO NOT ATTEMPT TO CHANGE THE FONT SIZES OR SPACINGS. % <=3 pages of 11pt text, except for Legacy % proposals, which may use up to 5 pages for text. \justification % 4. Description of Observations. (text block, not for Archival proposals) % 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 % explanation of special scheduling issues or other non-standard % requirements. Justify any observations of previously observed % targets (e.g. need to go deeper, need particular timing, etc.) % See Phase 1 Instructions document at: % http://galexgi.gsfc.nasa.gov/propforms/index.html for more information. % % PLEASE DO NOT USE ANY COLONS IN ANY TEXT FIELD %(use $\colon$ ). % PLEASE DO NOT ATTEMPT TO CHANGE THE FONT SIZES OR SPACINGS. % <=1 page \describeobservations % 5. Feasibility and Safety. (Required for all but Archival, text block) % Not to exceed 1 page single spaced (12 pt). % Enter text after the \feasibility keyword. Discuss the target % availability in terms of the spacecraft observing constraints. % Discuss in detail your signal-to-noise calculations, sensitivity % requirements, and resolution requirements for your proposed % observations. Describe the quality of your flux estimates % and explain how you arrived at them. 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 with sufficient information for % technical reviewers to reproduce your results. % If your targets are expected to be near the bright limits for % a single object or for the field, or if you are requesting FUV-only % observations, explain why these observations do not pose a safety % risk to the instrument. If you are proposing observations that % exceed the brightness limits, you must make a convincing case % for obtaining a waiver and explain why the proposed observations % will not damage the instrument. See the discussion of brightness % limits on our website % % PLEASE DO NOT USE ANY COLONS IN ANY TEXT FIELD %(use $\colon$ ). % PLEASE DO NOT ATTEMPT TO CHANGE THE FONT SIZES OR SPACINGS. % <=1 page \feasibility % 6. Additional Information. (Data analysis plan required for Archival proposals % or for mixed observing + archival proposals, % otherwise 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, % existence of corrolary data, justification for any coordinated % observations, willingness to forgo proprietary time, etc.). % PLEASE DO NOT USE ANY COLONS IN ANY TEXT FIELD %(use $\colon$ ). % PLEASE DO NOT ATTEMPT TO CHANGE THE FONT SIZES OR SPACINGS. % <=1 page \additionalinfo % 7. Investigator Information. (Optional, text block) % If desired, 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 % (use $\colon$ ). % PLEASE DO NOT ATTEMPT TO CHANGE THE FONT SIZES OR SPACINGS. % <= 1 page \vita %---------------------------------------------------------------------- % 8. Target List and Cover Page Information %---------------------------------------------------------------------- % % Cover and Target forms now submitted through AKBAR. % DO NOT submit a LATEX target file from an earlier cycle. % Instead, proposers are REQUIRED to submit their target lists and % Cover Page information through AKBAR. Please see % http://galexgi.gsfc.nasa.gov/propforms/index.html % or % http://heasarc.gsfc.nasa.gov/AKBAR % information. % \end{document} % % End file here