% NOAOPROP.TEX -- template for NOAO STANDARD telescope proposals.
% Revised for the 2004B observing semester (Aug 2004 - Jan 2005)
% For later semesters, the current form may be obtained from our Web
% page at http://www.noao.edu/noaoprop/noaoprop.html

% DEADLINE FOR SUBMISSIONS: 11:59pm MST WEDNESDAY MARCH 31 2004.

% This LaTeX template has been returned to you upon request through
% our Web-based proposal form.  The template has been customized for
% you based on the run information that you entered via the Web form.
% As an option you may complete this form locally and submit it by
% email following the instructions below.  If the run information is
% incomplete you should go back to the Web form, complete all the
% suggested run information and then obtain another customized 
% template before proceeding.  In particular, Gemini run information 
% including targets and guide stars must be completed through the Web 
% form.
%
% We encourage Web submissions but if you prefer to submit this
% template by email, follow the instructions below.
%
%   1. Where/how/when to submit this form electronically:
%      Send THIS file (NOT the PostScript version) to
%      noaoprop-submit@noao.edu.  The proposal and any figures
%      must be submitted as separate email messages.  Figures can be
%      submitted only AFTER the proposal ID has been sent to you via
%      email. See the end of this file for further submission details.
%
%   2. Before submitting this form electronically, run it through latex
%      and print it out to make certain that it looks the way that you
%      wish the review panel to see it.
%
%   3. If the proposal is a thesis or if the principal investigator is
%      a graduate student, the student's faculty advisor must send a
%      letter citing the graduate student's observing experience and,
%      if the program is a thesis, how this particular observing
%      proposal fits into the overall thesis plans.  This letter must
%      be sent by the faculty advisor to noaoprop-letter@noao.edu
%      BEFORE the proposal deadline.  Graduate students proposing
%      thesis observations should consult NOAO policies concerning
%      thesis programs and travel support.
%
%   4. If you are planning to bring a Visitor Instrument, you must
%      send a separate letter or email (noaoprop-letter@noao.edu) prior
%      to Oct 15 to make sure we fully understand what will be involved
%      in interfacing your equipment to our telescopes.
%
%   5. QUESTIONS?  If you have questions about submitting your proposal
%      send email to noaoprop-help@noao.edu.  Information about
%      instrumentation and observing facilities at Gemini, CTIO, KPNO,
%      Keck, Magellan, MMT, and the HET can be found at the NOAO Web 
%      site at http://www.noao.edu/noaoprop/noaoprop.html.  Specific 
%      instrumentation or facility questions for CTIO, KPNO, Keck, MMT,
%      Magellan or HET can also be sent to the respective sites at 
%      ctio@noao.edu, kpno@noao.edu, keck@noao.edu, mmt@noao.edu,
%      magellan@noao.edu or het@noao.edu.  Gemini questions can be 
%      emailed to the US mirror scientists at ngsc@noao.edu.
%
%   6. When your proposal is received at NOAO you will be sent an
%      automatic email message verifying its receipt along with a
%      proposal ID number.  If you do not receive this message within
%      15 minutes of the time you sent your proposal send email to
%      noaoprop-help@noao.edu for assistance.  You may track your
%      proposal processing by the proposal ID number at the following
%      web page:   http://www.noao.edu/cgi-bin/noaoprop/propstatus
% ___________________________________________________________________
% THE FORM STARTS HERE
%

% Please do not modify or delete this line.
\documentstyle[nprop29,11pt]{article}

\newcommand{\lya}{\mbox{${\rm Ly}\alpha$}}
\newcommand{\cmjj}{\mbox{${\rm cm^{-2}}$}}
\newcommand{\etal}{et al.}
\newcommand{\apg}{\:^{>}_{\sim}\:}
\newcommand{\apl}{\:^{<}_{\sim}\:}
\newcommand{\hI}{\mbox{${\rm H\ I}$}}

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

% Uncomment the following line and enter a previous semester and ID
% (e.g. 01B-0987) if you wish to flag this proposal as a resubmission
%\pastid{}

% Please do not modify or delete this line.
\proposaltype{Standard}
% Do not delete the following uncommented line which is required for Gemini 
% proposals.  This line indicates whether or not the proposal is being 
% submitted to multiple partner countries - only "yes" or "no" is valid.
\geminidata{mpartners}{no}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

% SCIENTIFIC CATEGORIES
%
% Please select a "scientific category" that best describes your
% program by uncommenting only ONE of the selections below.  Your
% \sciencecategory selection will be used to assign a review panel to
% your proposal.  DO NOT MODIFY THE SELECTION YOU UNCOMMENT.  A
% description of each of these categories is available on our Web page
% at http://www.noao.edu/noaoprop/help/scicat.html

% EXTRA-GALACTIC LIST (do not uncomment this line)
%\sciencecategory{Active Galaxies}
%\sciencecategory{Cosmology}
%\sciencecategory{Large Scale Struc.}
%\sciencecategory{Clusters of Galaxies}
\sciencecategory{High Z Galaxies}
%\sciencecategory{Low Z Galaxies}
%\sciencecategory{Resolved Galaxies}
%\sciencecategory{Stellar Pops (EGAL)}
%\sciencecategory{EGAL - Other}

% GALACTIC/LOCAL GROUP LIST (do not uncomment this line)
%\sciencecategory{Star Clusters}
%\sciencecategory{Stellar Pops (GAL)}
%\sciencecategory{HII Reg., PN, etc.}
%\sciencecategory{ISM}
%\sciencecategory{Star Forming Regions}
%\sciencecategory{Young Stellar Obj.}
%\sciencecategory{Massive Stars}
%\sciencecategory{Low Mass Stars}
%\sciencecategory{Stellar Remnants}
%\sciencecategory{Galactic - Other}

% SOLAR SYSTEM LIST (do not uncomment this line)
%\sciencecategory{Kuiper Belt Objects}
%\sciencecategory{Small Bodies \& Moons}
%\sciencecategory{Planets}
%\sciencecategory{Extrasolar Planets}
%\sciencecategory{Solar System - Other}

% KEYWORDS (1-5 keywords are required for Gemini).  Note that the keywords
% are different for the extra-galactic, galactic and solar system lists
% above, so if you change your science catagory you will need to check to
% be certain your keywords are still valid (see the list of keywords at
% http://www.noao.edu/noaoprop/help/keywords.html).
\geminidata{keyword1}{Dust}
\geminidata{keyword2}{Elliptical galaxies}
\geminidata{keyword3}{Evolution}
\geminidata{keyword4}{Proto-galaxies}
\geminidata{keyword5}{Starburst galaxies}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

% TITLE
%
% Give a descriptive title for the proposal in the \title command.
%
% Note that a title can be quite long; LaTeX will break the title into
% separate lines automatically.  If you wish to indicate line breaks
% yourself, do so with a `\\' command at the appropriate point in
% the title text.  Use both upper and lower case letters (NOT ALL CAPS).

\title{Deep Near-IR Spectroscopy of Massive Starforming Galaxies at $z > 3$}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

% INVESTIGATOR'S (PI AND CoI) INFORMATION BLOCKS
%
% Please give the PI's name (first name first followed by middle
% initial and last name), affiliation, department and complete mailing
% address, as well as an email address.  Also give a complete phone
% number, and a number for a fax machine if you have access to one.
% You must also indicate the principal investigator's status with one
% of the one-letter codes inside the \invstatus{} curly braces, as
% indicated below.
%
% The affil{}, \department{}, \address{} (use a comma separate list as
% needed), \city{}, \state{}, \zipcode{}, and \country{} (for non-US
% addresses) fields will be used together as your full postal mailing
% address.  Please be sure this information is complete.  Note that
% some institutions will not deliver postal mail if a department is
% not included in the postal mailing address.  Non-US addresses should
% include the country and any local postal codes.
%
% The fax number does not print on the form.
%
% For each CoI please include a name, affiliation, email address and
% investigator's status within the \begin{CoI} and \end{CoI} lines.
%
% For each \invstatus{} field, please fill in the appropriate
% investigator status code from the following list.  If the investigator
% is a graduate student, indicate "T" if this proposal is related to a
% thesis project, or "G" otherwise.  This code should represent the
% status of the individuals at the time of the proposal submission.
% This information is necessary to assist us with our required reporting
% to the NSF.
%
% \invstatus{P} % investigator has obtained PhD or doctorate
% \invstatus{T} % investigator is grad student, proposal is thesis
% \invstatus{G} % investigator is grad student, proposal not thesis
% \invstatus{U} % investigator is an undergraduate student
% \invstatus{O} % investigator has other status (none of the above)
%
%
% DO NOT remove the \begin{PI} and \end{PI}.  Only one individual's
% name per \name field is allowed.

\begin{PI}
\name{Hsiao-Wen Chen}
\affil{Massachusetts Institute of Technology}
\department{Center for Space Research}
\address{77 Massachusetts Ave., 37-664B}
\city{Cambridge}
\state{MA}
\zipcode{02139}
\country{USA}
\email{hchen@space.mit.edu}
\phone{(617) 452-5113}
\fax{}
\invstatus{P}
\end{PI}

\begin{CoI}
\name{Ron Marzke}
\affil{San Francisco State University}
\email{marzke@stars.sfsu.edu}
\invstatus{P}
\end{CoI}

\begin{CoI}
\name{Scott Burles}
\affil{Massachusetts Institute of Technology}
\email{burles@mit.edu}
\invstatus{P}
\end{CoI}

\begin{CoI}
\name{Robert A. Simcoe}
\affil{Massachusetts Institute of Technology}
\email{simcoe@space.mit.edu}
\invstatus{P}
\end{CoI}

%\begin{CoI}
%\name{}
%\affil{}
%\email{}
%\invstatus{}
%\end{CoI}



% You can supply more CoI blocks, but only the first six will be
% printed in the main body of the proposal - others will be printed
% in the right margin.  All investigator names will be available to
% the review panel and stored in our database.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

% ABSTRACT
%
% Give a general abstract of the scientific justification appropriate
% for a non-specialist.  Write between the \begin{abstract} and 
% \end{abstract} lines.  Limit yourself to approximately 175 words.
% Abstracts of accepted proposals will be made publicly available.

% DO NOT remove the \begin{abstract} and \end{abstract} lines.

\begin{abstract}

We propose to obtain rest-frame optical spectra of four massive starforming 
galaxies identified at $z>3$ in the Hubble Ultra Deep Field.  The galaxies are
selected to be luminous in the near-infrared ($> 1 \mu$Jy in the 
HST/NICMOS F160W band) and to have spectral energy 
distributions that are best matched by either an E/S0 or an Sab galaxy template in
our photometric redshift analysis.  Even at these early epochs, these galaxies have 
accumulated large stellar masses and are likely
to be the progenitors of present-day early-type galaxies.  A detailed analysis
of the star formation properties at this early epoch will offer important
constraints on models of galaxy formation,
including measures of star-formation efficiency and dust content.  
The goals of the proposed
observations are the following.  First, we will determine the star formation 
rate of these near-infrared selected galaxies using the observed [O\,II] line 
flux.  Second, we will estimate the dust content by comparing the rest-frame UV
flux (measured using the HST/ACS broad-band images) with the observed [O\,II] 
line strength.  Finally, we would like to obtain a lower limit to the dynamical
mass of each galaxy based on the [O\,II] line width.  
%We also select three
%secondary targets to be included in each slit setup.  For these, our aim is to
%measure the H$\alpha$ line fluxes of early-type galaxies at $z\approx 1.3$.

\end{abstract}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

% SUMMARY OF OBSERVING RUNS REQUESTED
%
% List a summary of the details of the observing runs being requested,
% for UP TO SIX runs.  The parameters for each run are segregated
% between \begin{obsrun} and \end{obsrun} lines.  Please be sure
% that the information is isolated properly for each run.
%
%   \begin{obsrun}
%   \telescope{}        % For example, \telescope{KP-4m}
%   \instrument{}       % For example, \instrument{ECHUV + T2KB}
%   \numnights{}        % For example, \numnights{6}
%   \lunardays{}        % For example, \lunardays{grey}
%   \optimaldates{}     % For example, \optimaldates{Sep - Nov}
%   \acceptabledates{}  % For example, \acceptabledates{Aug - Jan}
%   \end{obsrun}
%
% The following telescope identifiers MUST be used in the \telescope{}
% field.  Some of the telescope identifiers must include an observatory
% code as well since the same form can be used to submit a single 
% proposal for all facilities available through NOAO.
%
% Keck: Keck-I, Keck-II
% Gemini: GEM-N, GEM-NQ, GEM-S, GEM-SQ
% Hobby-Eberly Telescope: HET
% Magellan: Magellan-I, Magellan-II
% MMT:  MMT
% CTIO: CT-4m, CT-1.5m, CT-1.3m, CT-1.0m, CT-0.9m
% KPNO: KP-4m, WIYN, WIYN-2hr, WIYN-SYN, WIYN-TOO, KP-2.1m, KP-0.9m
%
% Select the instrument and detector identifiers from the list on our
% Web page at http://www.noao.edu/noaoprop/help/facilities.html.
% The correct codes MUST be used to ensure your correct
% instrument + detector combination.
%
% \numnights should give the number of nights of the run (for WIYN-SYN,
% WIYN-TOO, YALO, HET, GEM-NQ, and GEM-SQ use 10-hour equivalent nights,
% and 0.25 nights for the WIYN 2-hr queue).  Formats such as 5x0.5 are
% acceptable.
%
% \lunardays should contain the word "darkest", "dark", "grey", or
% "bright", which in turn reflects the number of nights from new moon
% where darkest<=3, dark<=7, grey<=10, bright<=14.  Particular lunar 
% phase requirements dictated by the science program (e.g., "<=12", 
% "+9, -6", or "full moon more than 2 hours away from Taurus") should
% be noted in the "scheduling constraints or non-usable dates" section 
% below.
%
% \optimaldates should contain the range of OPTIMAL months, as shown 
% below.
%
% \acceptabledates should give the range of ACCEPTABLE months (i.e.,
% you would not accept time outside those limits).
% NOTE THAT DUE TO INSTRUMENT BLOCKING RESTRICTIONS YOU SHOULD MAKE 
% THIS RANGE AS GENEROUS AS POSSIBLE.
%
% For QUEUE-SCHEDULED observations, you may set the date range to the 
% full semester range and set \lunardays to the brighest moon your
% observations could tolerate if the program were scheduled classically.
%
% To enter the acceptable and optimal date ranges, please use two
% dash-separated months with 3-letter abbreviations for the month
% (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec).
% For example:  \optimaldates{Nov - Dec}.
% We appreciate your help in not using vague range specifications
% like "October dark run" or "mid-January" which will require human
% intervention.
%
% FOR LONGTERM STATUS PROPOSALS SPECIFY ONLY THE RUNS FOR THE CURRENT
% SEMESTER, AND NOT FOR ANY SUBSEQUENT SEMESTERS.

% DO NOT remove any of the \begin{obsrun} and \end{obsrun} blocks, 
% even if the blocks are empty.

\begin{obsrun}
\telescope{GEM-SQ}
\instrument{GNIRSs}
\numnights{1.5}
\lunardays{bright}
\optimaldates{Oct - Dec}
\acceptabledates{Aug - Jan}
\end{obsrun}

\begin{obsrun}
\telescope{}
\instrument{}
\numnights{}
\lunardays{}
\optimaldates{}
\acceptabledates{}
\end{obsrun}

\begin{obsrun}
\telescope{}
\instrument{}
\numnights{}
\lunardays{}
\optimaldates{}
\acceptabledates{}
\end{obsrun}

\begin{obsrun}
\telescope{}
\instrument{}
\numnights{}
\lunardays{}
\optimaldates{}
\acceptabledates{}
\end{obsrun}

\begin{obsrun}
\telescope{}
\instrument{}
\numnights{}
\lunardays{}
\optimaldates{}
\acceptabledates{}
\end{obsrun}

\begin{obsrun}
\telescope{}
\instrument{}
\numnights{}
\lunardays{}
\optimaldates{}
\acceptabledates{}
\end{obsrun}


% If there are scheduling constraints or non-usable dates for any of
% the runs specified, (i.e., other than the default lunar phase 
% requirements or when your object is up) please give the dates by 
% filling in the curly braces in \unusabledates{}.  Note here if you 
% are requesting runs in an "either/or" situation, e.g. run 1 or run 2, 
% but not both. 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").
% 
% Proposals being sent to multiple Gemini National TACs (e.g. US and
% Canada) should include a detailed breakdown of the requested time in
% this field.  For example: "6 hours US, 4 hours Canada."
%
% Please limit your text to 4 lines on the printed copy.

\unusabledates{}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

% In the following "essay question" sections, the delimiting pieces of
% markup (\justification, \expdesign, etc.) act as LaTeX \section*{}
% commands.  If the author wanted to have numbered subsections within
% any of these, LaTeX's \subsection could be used.
%
% DO NOT REDUCE THE FONT SIZE, and do not otherwise fiddle with the
% format to get more on a page.  We will reset any changes back to the
% default font.

% 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 captions.  Be sure to include
% overall significance to astronomy.  THE SCIENTIFIC JUSTIFICATION
% SHOULD BE LIMITED TO ONE PAGE (the review panels have requested that
% we not send them more than one page), with up to two additional pages
% for references, figures (no more than three), and captions. WIYN 2-hr
% proposals are limited to one-half page of scientific justification.

% If you wish to use our "reference" environment, follow the following
% example (journal commands are compatible with AASTeX v4.0):
%
%\begin{references}
%\reference Armandroff \& Massey 1991 \aj, 102, 927.
%\reference Berkhuijsen \& Humphreys 1989 \aap, 214, 68.
%\reference Massey 1993 in Massive Stars: Their Lives in the 
% Interstellar Medium (Review), ed. J. P. Cassinelli and E. B. 
% Churchwell, p. 168.
%\reference Massey \& Armandroff 1999, in prep.
%\end{references}

% Only EPS figures may be included with your proposal.  In order to
% include an EPS plot, you should use the LaTeX "figure" environment.
% The plot file is included with the \plotone{FILENAME} command; two
% side-by-side plot files can be included by typing
% \plottwo{FILENAME1}{FILENAME2}.  Use \caption{} to specify a caption.
% The \epsscale{} command can be used to scale \plotone plots if they
% appear too large on the printed page.  Contact us if you have any
% figure questions or encounter any problems with figures
% (noaoprop-help@noao.edu).
%
% \begin{figure}
% \epsscale{0.85}
% \plotone{sample.eps}
% \caption{Sample figure showing important results.}
% \end{figure}
%
% If you need to rotate or make other transformations to a figure, you
% may use the \plotfiddle command:
% \plotfiddle{PSFILE}{VSIZE}{ROTANG}{HSCALE}{VSCALE}{HTRANS}{VTRANS}
% \plotfiddle{sample.eps}{2.6in}{-90.}{32.}{32.}{-250}{225}
% where HSCALE and VSCALE are percentages and HTRANS and VTRANS are
% in PostScript units, 72 PS units = 1 inch.
%
% Note that the Web form provides several useful and simple figure 
% options.

\sciencejustification

The Hubble Ultra Deep Field (HUDF) imaging observations, covering $3\times 3$
arcmin$^2$ of sky area, recorded by far the deepest images of distant universe 
both at optical wavelengths using the ACS (Beckwith \etal\ 2004) and at 
near-infrared wavelengths using the NICMOS camera (Thompson \etal\ 2004).  The 
optical and near-infrared images together have revealed not only the exquisite 
details of galaxies and galaxy groups at intermediate redshifts, but also 
numerous proto-galaxy candidates at redshift $z>5$ (e.g.\ Bunker \etal\ 2004).
A particularly exciting development is the opportunity to identify evolved 
galaxies at epochs earlier than $z=2$, where the presence of massive galaxies 
becomes difficult to explain as the result of time-consuming hierarchical 
galaxy assembly (e.g.\ Somerville \etal\ 2004).

We have performed an independent analysis of the drizzle-stacked optical and 
near-infrared images provided by the HUDF team and the NICMOS treasury team,
and identified 1800 objects in the NICMOS region that have measured infrared 
fluxes in the F110W and/or F160W bands.  The object detection algorithm is 
similar to those described in Chen \etal\ (2002).  We have also measured the 
redshifts and redshift likelihood functions for all the objects using a 
photometric redshift analysis outlined in Chen \etal\ (2003), which compares 
the observed spectral energy distribution (established from photometric 
measurements in the ACS F435W, F606W, F775W, F850LP, and NICMOS F110W and F160W
bandpasses) with a grid of model templates calculated at different redshifts.  
Comparison of our photometric redshift measurements with known spectroscopic 
redshifts published by the VIMOS team (Le F\'evre \etal\ 2004) for 23 galaxies 
in the HUDF/NICMOS region confirms that our photometric redshifts are accurate 
(Figure 1).

Figure 1 presents the observed optical F775W ($I$) and near-infrared F160W 
($H$) color versus photometric redshift for $\sim 1800$ near-infrared selected 
galaxies in the HUDF.  We have identified four near-infrared-luminous
galaxies at $z\approx 3.5$ that have observed spectral energy distributions
best-described by an early-type galaxy template (Figure 2).  Each has an 
observed near-infrared flux of $> 1 \mu$Jy in the HST/NICMOS F160W band, 
indicating a substantial stellar mass.  In addition, the spectral energy 
distributions of these galaxies are inconsistent with reddened, 
moderate-redshift galaxies, and in two of the four cases their rest-frame 
optical and near-UV morphologies are compact.   These galaxies may be the 
progenitors of present-day early-type 
galaxies that are still in the process of forming stars.  Because they are red and 
therefore optically faint ($AB(I) \sim 26$), they are well beyond the reach of existing optical spectrographs, and the Gemini 
Near-infrared Spectrograph (GNIRS) provides a unique opportunity to study the 
spectral properties of these galaxies at a critical time in their history. 

We propose to obtain deep near-infrared spectra of these four massive 
starforming galaxies identified at $z>3$ in HUDF.  Their moderate rest-frame 
UV colors indicate ongoing star formation and thus suggest significant 
emission in [O\,II].  Our primary goal is to detect this [O\,II] line using 
high-resolution spectroscopy in the $H$-band.  This detection would provide 
strong confirmation of the photometric redshifts and would enable critical 
probes of the internal properties of evolved galaxies at $z >3$.  In addition,
we include three early-type galaxies identified at $z\approx 1.3$ as secondary 
targets.  For each slit setup, we will place the slit on one of the primary 
targets and orient the slit in order to cover one of the secondary targets for 
identifying the redshifted H$\alpha$ emission feature in the same bandpass.  
The proposed observations will yield rest-frame optical spectra of massive 
star-forming galaxies selected by rest-frame optical flux, which is much more closely tied to stellar mass than the rest-frame UV fluxes used to select galaxies by the Lyman-break
technique.  Selection by stellar mass reveals a slice of the population largely disjoint
from the starburst galaxies identified in Lyman-break samples  
(Pettini \etal\ 2001) and therefore complementary constraints on models of galaxy
formation.

\newpage

\begin{figure}
\epsscale{0.5}
\plottwo{zcomp.eps}{IH_z.eps}
\caption{Left: Comparison of photometric redshifts and spectroscopic redshifts
for 23 galaxies observed in the NICMOS region of the Hubble Ultra Deep Field.
The spectroscopic redshift measurements were obtained by the VIMOS team 
(Le F\'evre \etal\ 2004).  The solid line indicates $z_{\rm phot}=z_{\rm 
spec}$.  Right: The observed ACS/F775W $-$ NICMOS/F160W color versus best-fit 
photometric redshift measurements for $\sim\,1800$ galaxies identified in the
NICMOS region of the Hubble Ultra Deep Field.  Different symbols represent
different best-fit template types, from early-type templates (stars), through
intermediate-type (closed circles), and through late-type templates (squares).
Larger symbols represent galaxies with an observed F160W flux brighter than 
1\,$\mu$Jy, and smaller ones are for the fainter galaxies.  The curves show the
expected optical and near-ir color evolution with redshift for elliptical/S0 
(solid curve), Scd (short dashed curve), and starburst (long dashed curve).}

\end{figure}

\vspace{0.25in}

\small
\noindent\underline{\bf references}:

Abraham, R. \etal\ 2004, AJ in press (astro-ph/0402436) \\
Bechwith, S. \etal\ 2004, in preparation 
(http://www.stsci.edu/hst/udf) \\
Bunker, A. J., Stanway, E. R., R. S. Ellis, \& McMahon, R. G. 2004,
           astro-ph/0403223 \\
Chen, H.-W. \etal\ 2002, ApJ, 570, 54 \\
Chen, H.-W. \etal\ 2003, ApJ, 586, 745 \\
Erb, D. \etal\ 2003, ApJ, 591, 101 \\
%Fontana, A. \etal\ 2003, ApJ, 594, L9 \\
%Glazebrook, K. \etal\ 2004, Nature submitted (astro-ph/0401037) \\
Le F\'evre, O. \etal\ 2004, A\&A submitted (astro-ph/0403628) \\
Pettini, M. \etal\ 2001, ApJ, 554, 981 \\
Savaglio, S. \etal\ 2004, ApJ, 602, 51 \\
Somerville, R. \etal\ 2004, ApJ, 600, L135 \\
Thompson, R. \etal\ 2004, in preparation
(http://www.stsci.edu/hst/udf) \\

\normalsize

\begin{figure}
\epsscale{1.0}
\plotone{pcomb.eps}
\caption{Summary of our photometric redshift analysis for the four massive
starforming galaxies identified at $z>3$ in the Hubble Ultra Deep Field.  In
each panel, the combined ACS and NICMOS images are presented on the left.  The
observed spectral energy distribution established based on optical and near-ir
broad-band photometric measurements is presented in the upper-right corner of
each panel, together with the best-fit template (solid curve) and model fluxes
(open squares).  The redshift likelihood function for each galaxy is presented
in the lower-right corner of each panel, indicating the most likely photometric
redshift according to the likelihood analysis.  We see in every case that the
large flux decrement between the NICMOS F110W and F160W is identified as the
4000-\AA\ break in the rest frame.}
\end{figure}


\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?  If you've requested 
% long-term status, justify why this is necessary for successful 
% completion of the science.
%
% NOTE: In previous versions of the proposal form, this section
% requested details about the use of non-NOAO observing facilities. 
% Such information should now be entered in the following "Other
% Facilities" section.

\expdesign

We propose to obtain deep near-infrared spectra of four massive starforming 
galaxies identified at $z>3$ in the Hubble Ultra Deep Field.   The sample includes
all galaxies matched by either an E/S0 or an Sab galaxy template in the photometric redshift analysis and also bright enough to be observable spectroscopically.  In order 
to satisfy the latter requirement, we limited the sample to those galaxies with observed near-infrared fluxes brighter than $ 1 \mu$Jy in the HST/NICMOS F160W band.   

The moderate optical colors suggest ongoing star formation and therefore [O\,II] emission.  The primary challenge is to detect this [O\,II] emission line amidst the forest 
of OH sky lines.   Our plan is to use the short camera with the 110 l/mm grating in the $H$ band, which offers a spectral resolution $R\sim 6000$ ($\lambda \sim 3 \AA$/pixel) 
and thus allows us to resolve the sky lines.  Taking the photometric redshift as the 
best estimate of the true redshift and using the Integration Time Calculator on the 
GNIRS website, we obtain the 10-$\sigma$ [O\,II] flux limits listed for each galaxy in Table 1.

These detection limits are of course quite sensitive to the precise value of the redshift.
The large redshift uncertainties inherent in the photometric-redshift technique
introduce the possibility that the targeted emission lines will fall
on top of rather than between the OH lines.  We assess the success rate
of finding the [O\,II] lines in between the OH lines using the sky spectra 
generated by the Integration Time Calculator.  Based on the expected photometric 
redshift errors, we find
that for each galaxy there is a 25\%  chance that the line will fall between the OH lines and conclude that in the worst case scenario we will 
successfully identify at least one galaxy in the sample.   The expected 
line fluxes are calculated using spectral-line diagnostics described in Kennicutt 
(1998) for the adopted star formation rate.  We adopt a nominal star formation 
rate of $\sim 30\,{\rm M}_\odot/{\rm yr}$ observed in massive, starforming 
galaxies found at $z>1.3$ by the Gemini Deep Deep Survey team (Savaglio \etal\ 
2004).

We have also selected three secondary targets listed in Table 1.  These 
galaxies have an observed spectral energy distribution best described by an 
E/S0 template and have a best-fit photometric redshift at $z\sim 1.3$.  Using 
the same grating setup, we will be able to identify the redshifted 
H$\alpha\,\lambda6563$ emission feature and constrain the underlying star 
formation rate of these quiescent systems using the observed H$\alpha$ line 
flux.  For each setup, we will place the slit over one of the primary targets 
and align the slit so that it will cover one of the secondary targets.  The 
final goal is to obtain deep near-infrared spectroscopy of seven near-infrared 
selected massive galaxies at high redshift.

\begin{center}
\begin{tabular}{p{1.0 in}ccrrrr}
\multicolumn{7}{c}{Table 1.\ Massive Starforming Galaxies at $z>3$}\\
\hline
\hline
 & & & \multicolumn{1}{c}{SFR} & Spectral & $\lambda_{\rm obs}$ & Line Flux \\
\multicolumn{1}{c}{Object} & $z_{\rm phot}$ & $AB_{\rm F160W}$ & (${\rm M}_\odot/{\rm yr}$) & Feature & $(\mu m)$ & (${\rm ergs}/{\rm sec}/{\rm cm}^2$) \\
\hline
\multicolumn{7}{c}{Primary targets}\\
\hline
9024 \dotfill & 3.11 & $23.852\pm 0.008$ & 30 & [O\,II] & 1.53 & $2.5\times 10^{-17}$ \\
1223 \dotfill & 3.46 & $22.593\pm 0.003$ & 30 & [O\,II] & 1.66 & $2.0\times 10^{-17}$ \\
5256 \dotfill & 3.74 & $23.141\pm 0.004$ & 30 & [O\,II] & 1.77 & $1.6\times 10^{-17}$ \\
6548 \dotfill & 3.89 & $23.815\pm 0.007$ & 30 & [O\,II] & 1.82 & $1.5\times 10^{-17}$ \\
\hline
\multicolumn{7}{c}{Secondary targets}\\
\hline
6037 \dotfill  & 1.18 & $23.134 \pm 0.004$ &  1 & H$\alpha$ & 1.43 & $1.6\times 10^{-17}$ \\ 
4353 \dotfill  & 1.27 & $22.480 \pm 0.002$ &  1 & H$\alpha$ & 1.49 & $1.3\times 10^{-17}$ \\ 
10780 \dotfill & 1.58 & $23.033 \pm 0.006$ &  1 & H$\alpha$ & 1.69 & $7.8\times 10^{-18}$ \\ 
%5143 \dotfill  & 1.17 & $22.445 \pm 0.003$ &  1 & H$\alpha$ & 1.42 & $1.6\times 10^{-17}$ \\ 
\hline
\end{tabular}
\end{center}


% PROPRIETARY PERIOD
% 
% Enter the propietary period for your data between the braces.
% The normal duration is 18 months from when the data are taken at
% the telescope.  Requests for longer proprietary periods must
% be approved by the NOAO Director.

\proprietaryperiod{18 months}


% OTHER FACILITIES
% 
% This section should consist of text only (no figures).
% Please limit to about a half page of printed text.
% 
% We are interested in understanding how observations made through
% NOAO observing opportunities complement or support data from other
% facilities both on the ground and in space.   We will use this
% information to guide the evolution of the NOAO program; it will not
% affect the success of your proposal in the evaluation process.
%
% Please describe how the proposed observations complement data from  
% other facilities, including private observatories and both ground-
% and space-based telescopes.  In addressing this question, take a
% broad view of your research program.  Are the data to be obtained 
% through this proposal going to help select samples for detailed
% observations using larger telescopes or from space observatories?
% Are these data going to be directly combined with data obtained
% elsewhere to test a hypothesis?  Will these observations have
% relevance to other observations, even though the proposal stands
% on its own?  For each of these other facilities, indicate the nature
% of the observations (yours or those of others), and describe the
% importance of the observations proposed here in the context of the
% entire program.

\otherfacilities

N/A.

% LONG-TERM DETAILS
%
% If you are requesting long-term status for this proposal briefly 
% state the requirements for telescope time (telescope, instrument, 
% number of nights) needed in subsequent semesters to complete this 
% project in % \longtermdetails (be sure to uncomment the 
% \longtermdetails line below).
%
% If this is a long-term request you MAY ALSO NEED to modify the
% \proposaltype keyword at the top of this form changing "Standard"
% to "Longterm" (where is says "Please do not modify or delete this 
% line!").  It is this keyword that will flag this proposal as a 
% long-term status request, regardless of what may be entered here 
% in \longtermdetails!
%
% If this is not a long-term status request then please ignore this
% section.
%
% Long-term status is not applicable to CNTAC proposals.
%
%\longtermdetails


% PAST USE
%
% How effectively have you used the facilities available through NOAO
% in the past?
% List allocations of telescope time on facilities available through 
% NOAO to the Principal Investigator during the past 2 years, together 
% with the current status of the data (cite publications where 
% appropriate).  Mark any allocations of time related to the current 
% proposal with a \relatedwork{} command.

\thepast

N/A.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

% OBSERVING RUN DETAILS - REQUIRED FOR EACH OBSERVING RUN REQUESTED
%
% For each run requested earlier in the \begin{obsruns}-\end{obsruns}
% sections of this proposal form, further run information must be
% specified.  Enter this block of information for each Gemini run.

% The \runid field must contain the run number plus 
% telescope/instrument-detector information as it appears for each 
% run in the obsruns sections. For example, \runid{1}{GEM-NQ/NIRI6}

\runid{1}{GEM-SQ/GNIRSs}

% Describe the observations to be made during this observing run in
% the \technicaldescription section. Justify the specific telescope, 
% the number of nights, the instrument, and the lunar phase requested. 
% Target information is included in the Gemini Target Table later in
% this section and is required for all Gemini runs.  To ensure that
% the target tables are complete, including guide stars, it is required
% that these tables be done through our Web form. 
%

\technicaldescription

The proposed GNIRS observations are outlined in Table 2 below.  Based on the
scientific objectives described in the previous sections, we propose to use
the short camera with the 110.5 l/mm grating to resolve [O\,II] emission-line 
features of the primary targets.  A 0.45-arcsec slit with the proposed grating
setup will yield a spectral resolution of $\approx 4 \AA$ per resolution 
element, allowing us to resolve the numerous OH sky lines and to identify weak
emission features between the OH lines.  To maximize the scientific return of 
the proposed observations, we plan to align the slit so that one of the three 
secondary targets listed in Table 1 will also be observed in each slit setup.
We estimate the required exposure times according to the Integration Time
Calculator at the GMOS website as well as prior experiences found in the
literature (e.g.\ Erb \etal\ 2003), taking into account the various sources of
noise.  

  The total exposure time listed in Table 2 will allow us to reach the
10-$\sigma$ level of significance at the expected line-flux level described for
each target in Table 1.  Including necessary overhead to set up the instrument 
for every field (estimated 30 min) and to observe one spectrophotometric 
standard on each night that the observations are carried out, we therefore ask 
for 15 hours to complete the proposed observations.

\begin{footnotesize}
\begin{center}
\begin{tabular}{p{1.0 in}ccrrrrc}
\multicolumn{8}{c}{Table 2.\ Summary of Proposed Observations}\\
\hline
\hline
 & RA & DEC & & & & $\lambda_{\rm obs}$ & \multicolumn{1}{c}{Exptime} \\ 
\multicolumn{1}{c}{Object} & (J2000) & (J2000) & $z_{\rm phot}$ & $AB_{\rm F160W}$ & \multicolumn{1}{c}{Grating} & \multicolumn{1}{c}{Filter} & \multicolumn{1}{c}{(min)} \\
\hline
9024 \dotfill & 03:32:35.08 & $-$27:46:47.5 & 3.11 & 23.85 & short/110\,l/mm & $H$ & 180 \\
1223 \dotfill & 03:32:39.67 & $-$27:48:50.6 & 3.46 & 22.59 & short/110\,l/mm & $H$ & 180 \\
5256 \dotfill & 03:32:42.74 & $-$27:47:33.9 & 3.74 & 23.14 & short/110\,l/mm & $H$ & 180 \\
6548 \dotfill & 03:32:34.64 & $-$27:47:20.9 & 3.89 & 23.82 & short/110\,l/mm & $H$ & 180 \\
\hline
\end{tabular}
\end{center}
\end{footnotesize}


\geminidata{pcontactnum}{1}
{\bf Principal Contact:} Hsiao-Wen Chen


% A list of resources is requested with your Gemini run.  Fill these
% in as appropriate for each Gemini run.
%
%\begin{resources}
%\filters{} 
%\dispersers{}
%\focalplanemasks{}
%\end{resources}

\begin{resources}
\filters{}
\dispersers{}
\focalplanemasks{}
\end{resources}



% COORDINATE RANGES OF PRINCIPLE TARGETS
% Use the \targetsra and \targetsdec fields to specify the range
% of right ascension (in hours) and declination (in degrees) of your
% principle targets for this observing run.
% 
% For example:
% 
%  \targetsra{14 to 17}
%  \targetsdec{-10 to 35}

\targetsra{3 to 4}			% RA range in hours
\targetsdec{-25 to -30}			% Dec. range in hours



% Target tables are required for all Gemini runs.  These tables must
% be generated through the Web form to ensure their completeness.  
% Guide stars are required for each target in the table - the guide 
% stars are found automatically by the Web software and appear at the 
% end of this section. The guide stars will not be printed as part 
% of your printed proposal.  Be warned!  If you modify your list of 
% targets through the LaTeX file then your guide stars could no 
% longer be correct and you will have an invalid proposal!
%
% Note that for iterative targets, only the parameters that need
% to be changed have to be specified.  Once a parameter is specified
% in a targettable environment, it is retained until explicitly 
% changed.
%
% The \endtarget command is REQUIRED for each target entry and 
% must be the last item; this command forces each target line to be
% printed.
%
% The \begin{geminitargettable}{} command for each table must contain
% the telescope/instrument-detector information for that particular
% run, i.e,. \begin{geminitargettable}{GEM-NQ/GMOSN}.
%
%
%\begin{geminitargettable}{}
%\objid{}         % a unique 4-digit number identifying the target
%\object{}        % 20 characters maximum
%\ra{}            % e.g., xx:xx:xx.x
%\dec{}           % e.g., +-xx:xx:xx.x
%\epoch{}         % all targets must be B1950 or J2000
%\magnitude{}       
%\obstime{}       % total exptime + overhead in minutes for all filters
%\imagequality{}  % these next 4 parameters are given as percentages as 
%\cloudcover{}    %  described at 
%  http://www.gemini.edu/sciops/ObsProcess/obsConstraints/obsConstraints.html
%\watervapor{}
%\skybackground{}
%\guidestars{}    % P=PWFS, 0=OIWFS, A=AOWFS, lower case=marginal star
%\gemcomment{}    % 20 characters maximum
%\endtarget       % required for each target
%\end{geminitargettable}
%

\begin{geminitargettable}{Run 1: GEM-SQ/GNIRSs}

\objid{1001}
\object{9024}
\ra{03:32:35.08}
\dec{-27:46:47.5}
\epoch{J2000}
\magnitude{23.8}
\obstime{180}
\guidestars{PP}
\imagequality{70}
\skybackground{50}
\watervapor{50}
\cloudcover{50}
\endtarget

\objid{1002}
\object{6548}
\ra{03:32:34.64}
\dec{-27:47:20.9}
\epoch{J2000}
\magnitude{23.8}
\obstime{180}
\guidestars{PP}
\imagequality{70}
\skybackground{50}
\watervapor{50}
\cloudcover{50}
\endtarget

\objid{1003}
\object{5256}
\ra{03:32:42.74}
\dec{-27:47:33.9}
\epoch{J2000}
\magnitude{23.1}
\obstime{180}
\guidestars{PP}
\imagequality{70}
\skybackground{50}
\watervapor{50}
\cloudcover{50}
\endtarget

\objid{1004}
\object{1223}
\ra{03:32:39.67}
\dec{-27:48:50.6}
\epoch{J2000}
\magnitude{22.6}
\obstime{180}
\guidestars{PP}
\imagequality{70}
\skybackground{50}
\watervapor{50}
\cloudcover{50}
\endtarget

\end{geminitargettable}

% Gemini guide stars for preceding table -- must be completed on Web.
\geminidata{pwfs1001_1}{3:32:10.459 -27:45:06.62 J2000 14.20}
\geminidata{pwfs1001_2}{3:32:46.785 -27:42:12.06 J2000 13.90}
\geminidata{pwfs1002_1}{3:32:46.785 -27:42:12.06 J2000 13.90}
\geminidata{pwfs1002_2}{3:32:10.459 -27:45:06.62 J2000 14.20}
\geminidata{pwfs1003_1}{3:33:05.102 -27:51:30.12 J2000 13.30}
\geminidata{pwfs1003_2}{3:32:40.248 -27:42:23.64 J2000 12.90}
\geminidata{pwfs1004_1}{3:32:24.709 -27:53:59.72 J2000 12.90}
\geminidata{pwfs1004_2}{3:32:40.248 -27:42:23.64 J2000 12.90}


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

% Detailed information as noted below must be provided for all runs 
% up to SIX runs.  Since Gemini runs must be specified through the 
% Web form this section only applies to non-Gemini runs - use the 
% Web form to generate detailed information and target tables for 
% Gemini runs.  Target Tables are required for WIYN-2hr, WIYN-SYN, 
% and YALO runs but are optional for other telescopes and instruments.
%
%\runid{}{}
%\technicaldescription
%\begin{configuration}
%\filters{}
%\grating{}
%\order{}
%\crossdisperser{}
%\slit{}
%\multislit{}
%\wstart{}
%\wend{}
%\cable{}
%\corrector{}
%\collimator{}
%\adc{}
%\end{configuration}
%\specialrequest    % remove and not use for HET runs
%\begin{targettable}{}
%\objid{}           % WIYN: specify a 3-digit number for each target
%\object{}          % 20 characters maximum
%\ra{}              % e.g., xx:xx:xx.x
%\dec{}             % e.g., +-xx:xx:xx.x
%\epoch{}           % e.g., 1950.3
%\magnitude{}
%\filter{}
%\exptime{}         % WIYN: in seconds PER EXPOSURE
%\nexposures{}      % Number of exposures
%\moondays{}        % Days from new moon, use a number 0-14
%\skycond{}         % "spec" or "phot"
%\seeing{}          % max allowable PSF FWHM (arcsecs)
%\obscomment{}      % 20 characters maximum - REQUIRED COMMAND
%  - repeat target entry parameters as needed to complete Table -
%\end{targettable}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

% Please do not modify or delete this line.
\end{document}

% Send the completed proposal file to noaoprop-submit@noao.edu.
%
% Figures should be submitted to noaoprop-submit@noao.edu AFTER
% the proposal identification number has been returned to you
% via email; this acknowledgement message will contain instructions
% on what to do.  If you submit figures without supplying
% the proper identifying information (per the email explanation), the
% figures stand a reasonable chance of being lost.  You will receive
% an acknowledgement message for each properly submitted figure.
%
% Expect these acknowledgement messages to be returned rather quickly.
% If you have not received email from us within 10-15 minutes of
% your submission contact us at noaoprop-help@noao.edu for assistance.
% And as a final reminder you may track your proposal processing by
% the proposal ID number at the following web page:
%         http://www.noao.edu/cgi-bin/noaoprop/propstatus
%
% Thank you for your interest in NOAO.  Contact us at
% noaoprop-help@noao.edu if you have any suggestions or comments.