% Template for applications for observing time at Calar Alto
%
% Updated version September, 2018 (S. Pedraz)
%
% requires dsaz0718.sty
%
% Changes with respect to previous versions:
%
% to template0102.tex / dsaz0102.sty :
% -- 1.23m-telescope removed
% -- PMAS as new CAHA instrument
% to template0702.tex / dsaz0702.sty :
% -- OMEGA2000 as a new instrument
% to template0103.tex / dsaz0103.sty :
% -- none thus far
% to template0703.tex / dsaz0703.sty
% arguments extended for \instrumentation in case of
% OMEGA Cass and PMAS
% to template0104.tex / dsaz0104.sty
% OMEGA-prime has been removed from offered instruments
%
% to template0107.tex / dsaz0107.sty
% -- New section 9b.: Comments on target sample
% -- Target list limited to 30 entries
%
% to template0707.tex / dsaz0707.sty
% -- Page 3a is now logistics page
%
% to template0110.tex / dsaz0110.sty
% -- New section on page 2: Strategic relevance for MPIA
%
% to template0111.tex / dsaz0111.sty
% -- OMEGA-Cass removed
% -- CAFE added
%
% to template0711.tex / dsaz0711.sty
% -- New column in publications list
% -- Instrument sheet modified
% -- New section 9c.: Comment on CAHA archive
%
% to template0112.tex / dsaz0112.sty
% -- New section 9d.: Comment on other archives
%
% to template0714.tex / dsaz0714.sty
% -- MAGIC removed
% -- PANIC added
%
% to template0115.tex / dsaz0115.sty
% -- TWIN and MOSCA removed
% -- CARMENES added
%
% to template0716.tex / dsaz0716.sty
% -- CAFE removed
%
% to template0717.tex / dsaz0716.sty
% -- PANIC removed
% -- CAFE added
%
% ************************************************************
% * This template contains explicit instructions as to how *
% * to fill in the LaTeX-commands (comments + examples). *
% * *
% * Please follow these instructions carefully! *
% * *
% * Since this LaTeX-file is automatically analysed to *
% * collect the statistical information and prepare the *
% * applications for the referees you must not manipulate *
% * this file (e.g. omit or permutate commands). *
% * Do not concatenate two commands into one line! *
% * Commands not needed have to be supplied with an empty *
% * argument (e.g. \SchedulingConstraints{} ). *
% ************************************************************
%
% General Information:
%
% Only proposals written in English are accepted!
%
% The Style-File and the Template-File were tested with LaTeX 2e
% (Version 2009/09/24) or TeX-Version 3.1415926-1.40.11.
%
% To create an empty form, empty calls {} have to be selected.
%
% Comments always refer to the argument or group of arguments
% of the *** PREVIOUS *** line.
%
% Forced linebreaks (\\ or empty line) do not work with most commands.
% Please use the command \newline instead!
%
% Type size and page format must not be changed, especially
% not within the scientific justification!
% The given number of pages and arrangement are checked! If your pages
% overflow the space provided, a LaTeX-error will occur.
%
% The list of publications and the citations from the scientific
% justification can (but do not have to) be created by LaTeX-command
% \cite{label} (see item publications). A mixture of manual entries
% and the use of \cite{label}, though, is not possible.
%
% Some frequent symbols are defined in the style-file:
% \etal \privcom \eg \ie \ibidem \dito
%
% Units for math-mode (in rm-Font)
% \GHz \MHz \Hz \pc \kpc \Mpc \cm \sec \Kelvin \Jy \mJy \microJy
%
%====================================================================
%
\documentclass{article}
\usepackage[dvips]{graphicx}
\usepackage{ifthen}
\usepackage{dsaz0718}
%
\begin{document}
%
%\TestRun
% Activate this command to create a test run
% checking your LaTeX file at CAHA.
% Do not forget to de-activate this command for
% actual submission!!!
%
% No records will be kept at CAHA for test runs,
% even if they are successful!
%
% ========================== p a g e 1 =============================
%
% Group, from which the application originates
% Comment/uncomment as appropriate
%
\RDSapplication % German institute other than MPIA
% RDS = Rat Deutscher Sternwarten
%\MPIAapplication% % MPIA
%\SPANISHapplication % Spanish institute
%\OTHER % all others
%
\noServiceMode % visitor mode
%\PartlyServiceMode % partly in service mode
%\ServiceMode % full service mode
%
% please select the appropriate mode for your application
% and comment out the other one.
%
\SpringApplication{2019}
%
\TelThreePointFive{}{}
%\TelTwoPointTwo{}{}
% {flag}{proposal reference ID}
%
% select only one telescope per application!
%
% -------------------------------------------------------------------
% Types of applications
% -------------------------------------------------------------------
%
% The type of your application - if applicable - is specified in
% the above command for the telescope selection as the 1. argument,
% perhaps together with the reference number of the previously
% submitted application as a 2. argument. If none of the cases
% described below is applicable, leave both arguments empty.
%
% MPIA or IAA guaranteed time: G
% ==============================
%
% Requests for MPIA or IAA guaranteed time must be flagged with a G.
% If you apply for MPIA time please fill in the
% \subsection*{Strategic relevance for MPIA} (see below).
%
% Long/Large/PhD projects (>2 semesters or >= 10 nights): P, L
% =============================================================
% Applications for PhD thesis work and long/large projects may be flagged,
% PhD thesis with a P, other long term projects with an L in the 1.
% argument to the telescope call above. If this flag is used, for both
% an additional page (item 8e) has to be filled in below, describing
% the current / planned logistics of the project. Is this an application
% to continue observations from previous semesters, please quote the
% reference number of the former application in the 2. argument.
%
% The purpose of flagging PhD programs is to request a particularly
% thorough initial application with an outline of all anticipated
% observations. In return, PhD programs can then usually expect
% subsequent approval within the framework of the initial request,
% as long as a satisfactory update on the PhD student's progress
% is provided in subsequent applications. Such a bonus will, however,
% not be given for long-term projects, which have to compete again fully
% with all other proposals currently submitted. For the latter the
% flag is intended to help the referees judging the overall project
% and its needs.
%
% Instrumental tests: I
% =====================
% Requests for observing time to test and commission a new
% instrument must be flagged with an I. Such an application must
% not be mixed with scientific observations and justification
% of this science. For the latter a separate proposal has to
% be submitted.
% Since January 2004 the CAHA director decides on time for instrumental
% tests
%
% Repetitive applications: W, T, C, R
% ===================================
% If a previous run has been lost due to weather or technical problems,
% the re-submitted proposal should be flagged. W indicates loss due to
% weather, T due to technical difficulties. Indicate the reference
% number of the previous application in the 2. argument.
% If you re-submit an application to continue a project (less than 3
% semesters in total duration) you may flag it with an C. Re-submission
% of a previously rejected application may be flagged with an R. Both
% should include the reference number of the former application in the
% 2. argument.
%
% Example:
% \TelThreePointFive{C}{H00-3.5-64} is a re-submission of an application
% analogous to application 64 at the 3.5m-telescope in autumn
% semester 2000.
%
% Multiple applications: M
% ========================
% Projects requiring different telescopes or instruments while using
% the SAME SCIENTIFIC JUSTIFICATION under item 8 for organizational
% reasons have to provide separate applications for each combination
% telescope/instrument needed. However, the detailed scientific
% justification may be provided only in one of these applications,
% in the other a short reference to the application with the full
% scientific justification is sufficient.
%
% In order to make it easier to relate them to each other, in the
% applications belonging together the first flag in the telescope
% call always has to be given as M.
%
% Example:
% A project needs optical as well as infrared observations.
% Then, two applications should be submitted, for which the telescopes
% e.g. \TelThreePointFive{M}{} and \TelTwoPointTwo{M}{} are specified.
% One of these contains the scientific justification.
%
% In applications, for which a special type is indicated as outlined
% above, a leading M in the 1. telescope argument signals, that for
% this type multiple applications are submitted.
%
% Example:
% \TelThreePointFive{MC}{S96-3.5-64} is the application to continue
% the project with the quoted reference number, together with which
% a further application is submitted,
% e.g. \TelTwoPointTwo{MC}{S96-2.2-28}.
%
% ---------------------------------------------------------------------
%
% Please, be careful when filling in the proposal, and provide complete
% information regarding previous applications. Help the TAC by supplying
% the requested info (accurate and complete).
%
% ---------------------------------------------------------------------
%
\Applicant{}{}{}
% Title Name Surname of the principal investigator (P.I.)
% ( =addressee of correspondence)
{}
% Institute
{}
% Street
{}{}
% ZIP-code Town
{}
% Country
{}
% complete e-mail address
%
% Not only give Smith.
% No space or TeX-format are to be used within this string
% because our procedure for the acceptance of the applications
% does use this string to send the confirmation to the P.I. !
%
\Collaborators{}{}
% collaborators: Name(s) Institute(s)
{}{}
% Name(s) Institute(s)
\Observers{}
{}
% Name(s) of the applicants/collaborators who will
% perform the observation.
\Category{} % category
% Please choose ONE category that comes closest to your
% application by giving the corresponding letter
% in the argument.
%
% This is an IMPORTANT INFORMATION needed for the
% the allocation of the referees. Please choose
% it carefully!
%
% A = Cosmology, intergalactic medium,
% clusters of galaxies, galaxies
% B = active galactic nuclei
% C = interstellar medium, star formation, milky way
% D = massive / hot stars
% E = low-mass / cold stars
% F = solar system
% G = instrumentation
\KeyWord{}
% unique keyword to mark the application
% (used to identify the application on the instrumentation
% sheet in addition to the P.I.'s name)
\Title{}
% Only one line!
\Abstract{}
% The length of the abstract must not change the page layout!
\Method{} % Instrument
{}
% observing method to be applied
% (e.g. long-slit spectroscopy)
\FluxLevel{} % from
{} % to
{} % unit of measurement of the brightness given
% (e.g. K-mag, Jy at 660nm)
%
% The following information has to contain the SUM of the time
% applied for as a (real) number (e.g. 3.5 or 0.2) to facilitate
% the electronic processing of the data.
% Further details (e.g. 3 x 1/2 night) are to be specified under
% item 11 with the command \SchedulingConstraints !
%
\Nights{} % no restriction % number of nights applied for
{} % grey % (without weather corrections!)
{} % dark % please specify only ONE of these!
{} % already awarded for this project (leave empty if none).
{} % nights expectedly needed to finish this project,
% in addition to the present application.
% ----> leave empty if you do not intend to submit further
% proposals in future semesters for this project.
% Only integer/real numbers (no blanks, no LaTeX-code) !
%
% Please, be careful when filling in the proposal, and provide complete
% information regarding previous applications. Help the TAC by supplying
% the requested info (accurate and complete).
%
% Specifically, supply the number of formerly granted nights for
% programmes directly related to the present application.
%
\ObsTimeRange{}{}
% best date range for observations {from} {to}
% Format to ease electronic processing: dd.mm.yy (no blanks !)
%
% examples:
% {15.11.99}{15.5.00} i.e. no limit in WS99
% {1.2.00}{15.4.00} i.e. beginning Feb. - mid-Apr. 2000
%
% Any scheduling constraints should be given under item 11.
\LST{}{}
% Optimum range in local sideral time (LST) in hours {from}{to}
% Format to ease electronic processing: hh:mm
% (e.g. {5:30}{10:00}, no blanks allowed!)
%
% ========================== p a g e 2 =============================
%
\begin{ObservingProgram}
%
% Scientific justification
% A maximum of 1 page text (no changes to font size should be made!)
% An additional page is at your disposal for pictures and tables to
% support your application!
%
% Please describe the following:
%
% -- outline of astrophysical problem
% -- scientific aim of the observations and what the novelty is,
% -- own previous work in this context,
% -- only in case of MPIA GTO proposals: Strategic relevance for MPIA
% (in this case please uncomment the corresponding subsection line)
% -- layout of the observation.
%
% In the last point please explain specifically how the
% observations planned will lead to the projected aim, i.e. the
% answer to the scientific questions.
%
% For long-term projects, nights allocated thus far have to be given
% (item 13) as well as the number of nights needed to finish the
% programme (item 6). Especially the results reached so far have to
% be presented under item 8.
%
% When wording your application, please take into consideration the
% following: Our committee consists of only 7 referees (HST has
% about 10x as many!). Its is, therefore, evident that we do not
% always have a specialist for each and every small area of interest.
% For this reason you should present aim and previous work in such a
% way that any experienced astrophysicist can follow your arguments
% (e.g. do not use unusual abbreviations, known to only a chosen few).
% Papers not yet published should be handed in as preprints (2 copies,
% one for each referee). As there is a large number of applications to
% be surveyed it is unreasonable to have to consult the web to be able
% to understand the background and previous work of an application!
% Reference to papers in preprint-servers, therefore, is pointless.
%
% Please do not change the layout of the scientific justification section
%
\subsection*{Astrophysical context}
\subsection*{Immediate aim}
\subsection*{Previous work}
%\subsection*{Strategic relevance for MPIA} %Only for MPIA GTOs
\subsection*{Layout of observations}
\end{ObservingProgram}
%
% ========================== p a g e 3 =============================
%
% This page is only for pictures and tables in support of the
% application. It must not be used for additional text!
%
% The following lines give an example of how to insert a single-column
% picture. Pictures that expand over both columns can be inserted
% likewise, with only the caption remaining single-column. When using
% the LaTeX-commando \begin{figure*} allowing a two-column caption,
% unfortunately an unwanted page-break occurs.
% Therefore please do not use this feature!
%
% Do not use a path to the PostScript-File. This will obviously
% not work during the LaTeX run at CAHA!
%
%\begin{SupportingMaterial}
%\begin{figure}
%\includegraphics[width=8.3cm,angle=0,clip=true]{image1.eps}
%\caption{\label{image1}Text for image 1}
%\end{figure}
%\end{SupportingMaterial}
%
% ========================== p a g e 3a ===========================
%
% Description of the current logistics for PhD thesis work
% and status report of long-term projects
% or large programmes (more than 10 nights per semester)
%
%\begin{Logistics}
%
%\end{Logistics}
%
% ========================== p a g e 3b =============================
%
% Backup project:
% Projects with special observing requirements (exceptionally good
% seeing, photometric conditions etc.) have to present a fully
% adequate backup programme (for details see
% http://www.caha.es/CAHA/Applications)
%
% The same comments as under item 8 above are applicable.
%
%\begin{BackupProgramm}
%\subsection*{Astrophysical context}
%\subsection*{Immediate aim}
%\subsection*{Previous work}
%\subsection*{Layout of observations}
%\end{BackupProgramm}
%
% ========================== p a g e 3c =============================
%
% This page is only for pictures and tables supporting the
% backup programme. It must not be used for additional text!
%
%\begin{BackupSupportingMaterial}
%\begin{figure}
%\includegraphics[width=8.3cm,angle=0,clip=true]{image1.eps}
%\caption{\label{image1}}
%\end{figure}
%\end{BackupSupportingMaterial}
%
% ========================== p a g e 4 ==============================
%
% If you wish to use a different heading instead of the brightness in
% the 4th column of the object table below (something more
% characteristic for your application, e.g. the redshift) you may
% change the text of the column-heading via the command
% \def\HeadLine{new heading}, e.g.
% \def\HeadLine{redshift\newline of the QSOs},
% which you insert here (before the \begin{Targets} command).
%
%\def\HeadLine{}
%
\begin{Targets}
%
%--------------------------------------------------------------------
% List only those objects scheduled for observation during the span
% of time applied for.
%
% Please limit the number of targets to a maximum of 30. If
% the actual list is longer, provide a subsample that includes
% the most representative examples and covers the whole RA range.
%
% Pay attention to observability and good use of the night!
%--------------------------------------------------------------------
%
% Examples of format
% (footnotes to the table are possible with \footnote{}):
%
% Name & \RA{h}{m}{s}{fract s} & \DEC{d}{'}{"} & mag & priority \\
% & \RA{}{}{}{} & \DEC{}{}{} & & \\
%
\end{Targets}
%
\CommentsSample{}
%
%--------------------------------------------------------------------
% Comments on the selection of the target sample.
% Please indicate, if not done in the general description,
% why these special targets have been selected, and in case
% they have been studied already by other groups, why
% it is justified to re-observe them.
%--------------------------------------------------------------------
%
% ========================== p a g e 5 =============================
%
\CommentsArchive{}
%
%--------------------------------------------------------------------
% Please verify whether data of your selected objects,
% taken in a similar observing configuration, are already
% available in the Calar Alto archive:
% http://caha.sdc.cab.inte-csic/calto
% If so, please justify why new observations are necessary.
%--------------------------------------------------------------------
%
\CommArch{}
%
%--------------------------------------------------------------------
% Please verify whether data of your selected objects,
% taken in a similar observing configuration, are already
% available in other archives.
% If so, please justify why new observations are necessary.
%--------------------------------------------------------------------
%
\TimeJustification{}
% Justification for the amount of time applied for.
% Please indicate also why this special telescope/
% instrument is needed or particularly suitable.
%
\SchedulingConstraints{}
% Leave empty if there are no restrictions.
%
% Otherwise, give the constraints and/or restrictions
% which are important for scheduling your observations.
% Please be brief here!
% Examples:
% Before 3.5m-observations !
% Not between ... and ... !
% Simultaneously to HST-observations at ... !
%
\ObsExperience{}
% Observational experience regarding the project applied for
%
% ========================== p a g e 6 =============================
%
\begin{Publications}
% Results and publications of campaigns during
% the past three years in form of a table (see example).
% ***** Please remain within the given format ******
% In the last column indicate the corresponding
% reference under item 14 and there under item
% \BibliographieListen in argument #2 list the full
% quotation (including title).
%
% With the optional command \StatusOfProjects a short
% summary of projects carried out during the last years on
% Calar Alto may be added to the table in support of this
% application.
% Columns of table:
% Tel. & instrument & proposal ID & period & nights & success [%] & publications
% Example:
% 3.5m & PMAS & F11-3.5-099 & Jan 11 & 3 & 33\% & \cite{CA-1}\\
% 2.2m & CAFOS & H10-2.2-099 & Jul 10 & 5 & 85\% & \cite{CA-2}\\
%
%\StatusOfProjects{}
%
% Please, be careful when filling in the proposal, and provide complete
% information regarding previous applications. Help the TAC by supplying
% the requested info (accurate and complete).
%
\end{Publications}
%
%
\BibliographyLists{auto}{}{}
%\BibliographyLists{manuell}{}{}
%
% ------------------------------------------------------------------
% The bibliographical details in argument 2 and 3 of this call above
% refer to item 8 resp. 13 of the application.
%
% If as first argument {auto} is used, all references within the
% text are carried out via LaTeX-command \cite{label}. The references
% have then to be given as second and third argument as follows:
%
% 2. argument =
% references relating to scientific justification (item 8):
%{\bibitem{label}{reference}
% \bibitem{label}{reference}
% ...
%}{
% These two brackets separate the 2nd and 3rd argument.
% 3. argument =
% references to past observations on Calar Alto (item 13):
%\bibitem{label}{reference}
%\bibitem{label}{reference}
% ...
%}% closes 3rd argument
%
% When using the Auto-Modus the entries to (8) receive
% consecutive numbers <100, those to (13) numbers >99.
%
% Example:
%
% If the text gives: "... produces $H_0=10$ \cite{Mei76} ...",
% insert in the 2. argument of \BibliographyLists the following:
% { ...
%\bibitem{Mei76}{Meier (1976): {\em The Hubble-constant},
% A\&A {\bf 123}, 1024}
% ... }
%
% If the references are inserted manually into the text and the
% literature list is formatted manually, the call has to be as
% follows:
%
%\BibliographyLists{manual}{references to 8}{references to 13}
%
% In this case the applicant has to take care of the necessary
% cross-references himself. The information under item 8 will
% automatically be separated by a horizontal line from those
% under item 13.
%
% Example:
%\BibliographyLists{manual}%
%{Meier (1976): {\em the Hubble-constant}, A\&A {\bf 123}, 1024\\
% Schmidt (1963): {\em Identification of 3C\,273}, Nature {\bf 197}, 10
%}{Ich (1997): {\em the XYZ-constant}, ApJ {\bf 123}, 987\\
% Ich und Du (1998): {\em Die Entfernung zu M\,31}, PASP {\bf 145}, 12}
%
% A T T E N T I O N:
% ================
%
% A mixture of the two modi in the arguments 2 und 3 is not possible!
% That is either ** ALL ** citations (in the scientific justification
% as well as those papers going back to observations on Calar Alto) are
% done by \cite{mark} or ** ALL ** citations and references are
% inserted manually.
%
% ========================== p a g e 7 =============================
%
%\TravelFunding{}
% Uncomment if you intend to apply for travel funds from DFG.
% The argument remains empty if only one observer will apply
% for travel funds at the DFG.
%
% The deadlines for DFG funding are:
% 15.11. for the spring semester
% 15.05. for the autumn semester
%
% !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
% ! Please, DEFINITELY give as argument the reason if it is !
% ! planned to apply for travel funds for TWO OBSERVERS! !
% !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
%
% Applicants from Max Planck institutes cannot apply for DFG funding!
%
\noTravelFunding
% Comment out, if you will apply for DFG funds.
%
%
% >>>> Please note that the observing data will be made public by the Virtual
% Observatory (VO), Madrid, after a proprietary period of one year after
% the end of the observation. This does not apply for IAA and MPIA
% guaranteed time.
%
% ========================== p a g e 8 =============================
%
\MinimumObservingRequirements
{} % worst tolerable seeing ["], e.g. {2.5}
{} % minimum transparency [%], e.g. {50}
{} % maximum airmass, e.g. {1.5}
{} % photometric conditions required [yes/no]
{/} % maximum moon phase [0-1 in units of illuminated fraction]
% / min. distance to object [degrees], e.g. {0.8/30}
{/} % min./max. time difference between individual observations
% in case of service observation [days/days], e.g. {2/10}
\Instrumentation{}{}{}{}{}{}{}
% THE ARGUMENTS HAVE CHANGED ! (see below)
% Specification of instrumentation
% Note that always 7 arguments have to be given!
% Arguments not needed have to be given as {} !
%
% Possible arguments are listed below ---
% behind \EndOfApplication --- !
%
\EndOfApplication
The rest of this file will not be processed by LaTeX!
In the following we provide
-- list of all valid entries for \Instrumentation
-- frame for your bibliographic data base entries
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Possible combinations for the arguments in \Instrumentation
--> Capitalization is important!
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++