% soprop.tex       LaTeX2e proposal template for Steward Observatory proposals
%                  Version 1.3 [2007/08/01 R.A. Jansen]
%                  Version 1.31 [2015/09/01 D. Zaritsky]
%                  Version 1.32 [2016/02/29 D. Zaritsky]
%                  edited slightly by D. Zaritsky to support auto processing
%                  Version 1.33 [2018/03/05 K. Su]
%                  edited slightly by K. Su for instructions for PI Instrument,
%                  student project..etc. 
%                  Version 1.34 [2018-09-09 K. Su]
%                  edited for consisteny
%                  Version 1.35 [2019-02-22 K. Su]
%                  edited to restric SJ to 1+1 page
%
%        **** this file may be edited directly by the proposer;  ****
%        **** wherever a pair of curly brackets {} appears, some ****
%        **** information needs to be provided.                  ****
%
%        *** PROPOSERS ARE RESPONSIBLE FOR NOT MAKING CHANGES THAT ****
%        *** AFFECT AUTO PROCESSING. FOLLOW EXAMPLES AND GUIDELINES ****
%        *** CLOSELY ****
%
% Please read the instructions in  both  the current  Call for Proposals  and
% within this LaTeX proposal template *carefully*.  Note, that it is the sole
% responsibility of the proposer to verify  that the selected instrument will
% be available, and that proposals for the selected telescope are indeed sol-
% licited  in the  current  Call for Proposals.  In the case of  non-facility 
% instruments, contact the instrument PI  well before  the proposal dead-line 
% to obtain permission and arrange training.
% The Call for Proposals, along with the present proposal template file and a
% new Latex2e class file 'soprop.cls' constitute the proposal package.  It is
% available from:  http://www.as.arizona.edu/telescope-proposals 
% Copy the template file  'soprop.tex'  and associated class file to the same
% directory and edit the template file using your favorite ascii text editor.
% Be sure to provide all required information in the template file (anywhere
% you see an empty pair of {}, information is expected!)  using the specified
% format, and then compile it into a device independent DVI output format:
%
%     latex soprop.tex 
%
% If you see warning messages, please follow the hints to resolve the problem.
% To convert the DVI output format into printable PostScript format, type:
%
%     dvips -Pamz -Pcmz -t letter soprop.dvi -o soprop.ps
%
% (if you submit from Europe, replace the "-t letter" option with "-t a4").
% The "-Pamz -Pcmz" option provided to 'dvips' cause all fonts to be included
% in the PS file, ensuring fast and legible rendering of the text on computer
% screens and platform independence.  Should you wish to create PDF (Portable
% Document Format) output instead, then (on linux systems) type:
%     ps2pdf13 soprop.ps 
% 
% Alternatively, you can also use:
%     pdflatex soprop.tex 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

% **********   T H E   T E M P L A T E   S T A R T S   H E R E   *************

% Please do not modify or delete the following line. If you are submitting
% from Europe, you may replace the default 'letter' option with 'a4paper'.
\documentclass[letter]{soprop}

% Please do not modify or delete the following line.
\begin{document}

% User defined Latex commands may be inserted below. Note that a number of
% AASTeX/AMSTeX symbols are already pre-defined in 'soprop.cls'  (see also
% the Call for Proposals).  Please do not redefine or adjust any fonts.

% In the following \begin{proposalterminfo} .. \end{proposalterminfo} block,
% provide information on the observing cycle (year and term) of the proposed
% observations, the type of proposal and whether this is a continuation of a
% program that was previously awarded time.
\begin{proposalterminfo}
   \propyear{}    % enter a 4-digit year in the range 2006--2016, e.g. 2006
   \propterm{}    % A or B for semesters.  A: Feb to Jun, B: Jul to Jan
   \propcont{}    % enter 'true' or 'yes' (without quotes) if this is a
                  %   continuation of a program that was previously awarded
                  %   time; the default is 'false' (new program)
   \proplong{}    % enter 'true' or 'yes' (without quotes) if this is a
                  %   long-term proposal; default is 'false' (short-term)
   \propltnr{}    % enter your previously assigned program number if you
                  %   specified 'true' in both items above.  Please enter
                  %   digits only (or LaTeX will exit with an error), e.g.
                  %   '148' (without quotes)
   \propeduc{}    % enter 'true' or 'yes' (without quotes) if this is an
                  %   education or public outreach proposal; default is 
                  %   'false'. This flag will override the \proplong flag.
   \propengr{}    % enter 'true' or 'yes' (without quotes) if this is an
                  %   engineering proposal; default is 'false'.  This flag
                  %   will override the \proplong and \propeduc flags.
\end{proposalterminfo}


% Provide a descriptive, but concise (at most 2 lines), title for the proposal
% in the \proptitle command.  If the title doesn't fit on a single line, LaTeX
% will automatically break and continue on the next line. 
%

%  *****  NO COMMAS, NO LINE BREAKS, ONLY SINGLE LINE  ******
%  *****  AVOID TO USE SPECIAL CHARACTERS "{" AND "}"
\proptitle{}


% Identify a Principal Investigator for this project. Do not comment out or
% change the \begin{PrincipalInvestigator} and \end{PrincipalInvestigator}
% statements.
\begin{PrincipalInvestigator}
    \PIname{}                % Enter the first and last name of the PI
    \PIinstitution{}         % Enter (abbreviation of) the PI institution;
                             %   the default is 'SO' (Steward Observatory).
    \PIemail{}               % Enter the PI e-mail address, which is used 
                             %   for email acknowledge/resubmittion/comment
    \PIphone{}               % Enter the phone number (incl. area code) via
                             %   which you may be contacted
    \PIcertified{}           % Enter 'true' or 'yes' (without quotes) if the
                             %   PI is certified on the telescope/instrument;
                             %   the default is 'false'.
    \PIstudent{}             % Enter 'true' or 'yes' (without quotes) if the
                             %   PI is a (graduate) student; the default is
                             %   'false'.
\end{PrincipalInvestigator}


% Identify all Co-Investigators and provide (1) affilliation, (2) whether they
% are certified on telescope/instrument, and (3) whether they are a student.
% Uncomment and replicate the \begin{CoInvestigator} .. \end{CoInvestigator}
% block for each additional Co-Investigator as needed.  The list of Co-Is
% should run no more than three lines on the proposal coverpage.
%
%\begin{CoInvestigator}
%    \CoIname{}              % Enter the first name (or initial) and last
%                            %   name of the Co-investigator
%    \CoIinstitution{}       % Enter (abbreviation of) the PI institution;
%                            %   default is 'SO' (Steward Observatory).
%    \CoIcertified{}         % Enter 'true' or 'yes' (without quotes) if the
%                            %   CoI is certified on the telescope/instrument;
%                            %   the default is 'false'
%    \CoIstudent{}           % Enter 'true' or 'yes' (without quotes) if the
%                            %   CoI is a (graduate) student; default 'false'
%\end{CoInvestigator}


% Enter an abstract of the science justification here between \propabstract{
% and }.  Summarize what observations you wish to obtain, what the science
% goals of these observations are, and why the proposed science is important.
% Write the abstract with a generic astrophysicist, outside your own field of
% expertise, in mind. The abstract must be a single paragraph. Do not change
% the default font for more than a single sentence.  Note, that the abstract
% text cannot contain blank lines, or a Latex error will result.
%
\propabstract{}


% Summarize the requested observations per observing run.  Replicate the 
% \begin{ObservingRun} .. \end{ObservingRun} block for each additional
% observing run as needed.
% Occasionally, a different telescope/instrument configuration may suffice
% to achieve the same science goals.  If so, an alternate run to a given
% observing run may be specified within a \begin{AlternateRun} ..
% \end{AlternateRun} block, a commented-out example of which can be found
% following the \begin{ObservingRun} .. \end{ObservingRun} block below.
% Note, that the total of primary (and any alternate) runs should not
% exceed 12 lines on the proposal coverpage.  On rare occasions (proposals
% for long-term status), more lines may be needed.  If so, insert a page
% with the full observing runs table, similar in format to the one on the
% cover page, before the "Scientific Justification" section into the
% proposal. For all requested entries, see the Call for Proposals for a
% table with the telescope/instrument configurations that are currently
% offered and their proper identifiers/abbreviations.
%
\begin{ObservingRun}
  \telescope{}               % Enter the telescope identifier. You must use 
                             %   either LBT, MMT, MAG1, MAG2, UKIRT, 90, 61, 60,
                             %   60MN, VATT, 40 (with no extra spaces)
                             %
                             % ***** USE ONLY THE DESIGNATIONS GIVEN ABOVE
                             %
  \secondary{}               % Enter the telescope secondary cage identifier,
                             %   e.g 'f/5','f/9','f/15','PF'(prime focus),...
                             %   (without the quotes). Consult the Call for
                             %   Proposals or instrument web-pages if unsure.
  \instrument{}              % Enter the instrument identifier, e.g. 'Blue',
                             %   'Red','Megacam','Hectospec','Hectochelle','MMIRS',
                             %   'IMACS f/2','IMACS f/4','MIKE','MIKE+fibers',
                             %   'BCSpec','90Prime','LBC', etc. (without the
                             %    quotes)
                             %
                             % **** DO NOT USE COMMAS, FOR MULTIPLE INSTRUMENTS USE INSTRUMENT1/INSTRUMENT2
                             %
  \piflag{}                  % Enter 'true' if this is a PI instrument. You
                             %   must obtain PI approval for its use before
                             %   submitting your proposal. Default 'false'.
  \aoflag{}                  % Enter 'true' if you request use of Adaptive
                             %   Optics (MMT). Consult the Call for Proposals
                             %   regarding approval and signature(s) on the
                             %   "Approval for Instrument Use from PI" line.
                             %   Default is 'false'.
  \numnights{}               % Enter the number of nights you are requesting
                             %   even for queue-scheduled instruments. ROUND
                             %   TO THE NEAREST HALF a NIGHT, e.g. '2.5'.
                             %   NUMERICAL NUMBER ONLY, NO TEXT. 
                             %
  \nightsky{}                % You must Enter one of 'bright', 'grey', 'dark',
                             %   'dark/grey', 'grey/bright' or 'any' to
                             %   specify your sky brightness constraints.
                             %   (no quotes, no spaces). No preference, put 'any'
                             %   Justify your selection in the Experimental
                             %   Design section.
                             %
                             % ***** USE ONLY THE DESIGNATIONS GIVEN ABOVE

  \optimalmonths{}           % Enter the optimal month-range for the proposed
                             %   observations using three-letter abbreviations
                             %   for the months separated by a double-dash,
                             %   e.g., 'Sep--Oct' or 'Jan--Jan'.
  \acceptablemonths{}        % Enter the acceptable month-range for the
                             %   proposed observations using the same format,
                             %   e.g., 'Sep--Nov' or 'Dec--Feb'.
  \sharingpossible{}         % Enter 'true' or 'yes' if sharing of nights is
                             %   possible; default is 'false'.
  \sharingadvisable{}        % Enter 'true' or 'yes' if sharing of nights is
                             %   advisable; default is 'false'.
  \altrun{}                  % Is there an associated alternate run
                             %   default is no (if yes, uncomment and fill out
                             %    the alternate run section below)
\end{ObservingRun}


%\begin{AlternateRun}
%    \alttorunnumber{}        % Number of the observing run to which this is
%                             %   the alternate run
%    \alttelescope{}          % Enter the telescope identifier
%    \altsecondary{}          % Enter the telescope secondary cage identifier
%    \altinstrument{}         % Enter the instrument identifier
%    \altpiflag{}             % Enter 'true' if this is a PI instrument
%    \altaoflag{}             % Enter 'true' if you require Adaptive Optics
%    \altnumnights{}          % Enter the number of nights you are requesting
%    \altnightsky{}           % Enter one of 'bright', 'grey', 'dark', 
                              %   'dark/grey', 'grey/bright' or 'any'
%    \altoptimalmonths{}      % Enter the optimal month-range
%    \altacceptablemonths{}   % Enter the acceptable month-range
%    \altsharingpossible{}    % Enter 'true' if night-sharing is possible
%    \altsharingadvisable{}   % Enter 'true' if night-sharing is advisable
%\end{AlternateRun}


% Enter here, between \schedulingconstraints{ and }, any unusable dates and/
% or scheduling constraints for any of the runs specified, (i.e., other than
% the default lunar phase requirements or when your object is up).  And tell
% us why unusable dates are unusable. This is also the place to advise us of
% any special constraints which affect the scheduling of your observing run
% (e.g. "schedule run #1 before run #2" or "run dates must be coordinated
% with HST observations"), and to identify any constraints on sharing of
% nights.  Note that the text between the curly brackets cannot contain any
% blank lines, or a Latex error will result.   If there are no constraints,
% you must enter 'None.' (without the quotes).
%
\schedulingconstraints{}


% Provide the list of proposed targets. Replicate and fill out as many of the
% \begin{Target} .. \end{Target} blocks as you have objects (up to 26).  For
% more than 26 objects, provide a list here of up to 26 targets that show the
% full range in RA and Dec.
\begin{Target}
    \targname{}    % Enter the target name or catalog number
    \targra{}      % Enter the target Right Ascension (HH:MM:SS.ss)
    \targdec{}     % Enter the target Declination ($+$ or $-$DD:MM:SS.s)
    \targinfo{}    % Enter relevant target properties such as magnitude
                   %   color, type. E.g.: '$V$=23, $z$=0.83, Cluster'
\end{Target}

% For PI instruments, an e-mail message from the instrument PI approving
% of the proposed use of the instrument should be sent to the TAC Chair.
% Give the name/email of the instrument PI in the field of \piapproval{}.
\piapproval{}


% For each graduate student named as PI or CoI on the cover page, provide the 
% following information. Advisor must send confirmation email to TAC Chair, 
% and identify whether or not the student's 2nd-year project or PhD thesis 
% depends on the proposed observations.   
% Uncomment and replicate the \begin{graduatestudent} .. \end{graduatestudent}
% block for each additional graduate student as needed (up to 8).
%
% \begin{graduatestudent}
%    \student{}      % Enter the first name (or initial) and last name of the
%                    %   graduate student
%    \advisorname{}  % Enter the name of the graduate student's advisor
%    \advisoremail{} % Enter the email of the graduate student's advisor         
%    \secondyr{}     % Enter 'true' or 'yes' (without quotes) if the student's
%                    %   2nd-year project depends on the proposed observations
%    \thesis{}       % Enter 'true' or 'yes' (without quotes) if the student's
%                    %   PhD thesis depends on the proposed observations.
% \end{graduatestudent}

% Please do not move, modify or delete the following line.
\makecoverpages


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% In the following "essay question" sections, the delimiting pieces of markup
% (\sciencejustification, \experimentaldesign, etc.) act as LaTeX \section*{}
% commands.  If you want to have numbered subsections within any of these, 
% LaTeX's \subsection{} command may be used.  A number of LaTeX symbols have
% been defined in the class file and are tabulated in the Call for Proposals.
%
% DO NOT REDUCE THE FONT SIZE, do not use any font-modifiers other than:
%
%    \rm, \rmfamily, \textrm{}    % to produce upright roman text (default)
%    \sf, \sffamily, \textsf{}    % to produce sans serif text
%    \tt, \ttfamily, \texttt{}    % to produce typewriter text
%    \it, \itshape,  \textit{}    % to produce italicized text
%    \sl, \slshape,  \textsl{}    % to produce slanted text
%    \sc, \scshape,  \textsc{}    % to produce small caps text
%    \bf, \bfseries, \textbf{}    % to produce boldface text
%    or LaTeX2e-style combinations thereof (e.g., \bfseries\itshape )
%    {\em }, or \emph{}           % to emphasize a short portion of text
%    $\bm $, or \boldmath$ $      % to produce bold font in math mode
%
% and do not otherwise fiddle with the format to get more on a page.  We will
% attempt to reset any changes back to the default font and ---even if you
% succeed--- annoying the TAC rarely helps.

% SCIENTIFIC JUSTIFICATION
% Give the scientific justification for the proposed observations.  This
% section should consist of paragraphs of text followed by any references
% and up to three figures and their captions.  The page limit for this section
% is 1 pages of text + 1 of Figures and other supporting  materials.
%
\sciencejustification


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Please do not remove the following command.
\clearpage

% EXPERIMENTAL DESIGN
% This section should consist of text only (no figures). There is a limit of
% one page of printed text.

% Describe your overall observational program.  How will these observations
% contribute toward the accomplishment of the goals outlined in the science
% justification?  Be sure to describe not only the observations to be done
% this term, but the scope of the entire program.  For long-term programs, 
% detail how many nights will be necessary in future terms to complete the
% program.
\experimentaldesign


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Please do not remove the following command.
\clearpage

% SUMMARY OF TIME REQUESTED AND AWARDED
% The TAC needs to understand the scope of this project. First, tell us how 
% many UAO nights you've already had for this project, how many you're      
% asking for this time, and give a good guess for how many you'll need to   
% complete the project.  Second, if substantial amounts of the observing for
% this project are coming from non-UAO telescopes, tell us about that obser-
% ving, and tell us how the UAO part fits in.  Third, if you are collabora- 
% ting with people who have telescopes, and especially if you are part of a 
% very large collaboration, tell us who is leading the project, and how UAO 
% time and your participation fit into the large project. (up to 1 page)
\timerequest


% Please do not remove the following command.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\clearpage

% PAST USE OF STEWARD OBSERVATORY FACILITIES
% How effectively have you used the facilities available through UAO in the 
% past?  List ALL allocations of telescope time for the present project and 
% allocations for other projects on facilities available through UAO during 
% the past 2 years, together with the current status of the data, and cite  
% publications that were based (to a significant extent) on data obtained at
% UAO facilities.  Mark those allocations related to the present proposal  
% by preceding the text with a \related command. (up to 1 page)
\pastuse


% OTHER INFORMATION
% Include information that you believe is relevant to the evaluation 
% of the program. This could include the relation of the work to 
% externally funded programs, mission critical aspects of the work, 
% timing related to your status (e.g. needing to finish the observations
% before moving to another position). (up to 1 page)
\otherinfo


% Please do not modify or delete the following command. Any subsequent text
% will be ignored.
\end{document}
