%APN3_PROCEEDINGS_FORM%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% TEMPLATE.TEX -- APN3 (2003) ASP Conference Proceedings template.
%
% Derived from ADASS VIII (98) ASP Conference Proceedings template
% Updated by N. Manset for ADASS IX (99), F. Primini for ADASS 2000,
% D.Bohlender for ADASS 2001, and H. Payne for ADASS XII and LaTeX2e.
%
% Use this template to create your proceedings paper in LaTeX format
% by following the instructions given below.  Much of the input will
% be enclosed by braces (i.e., { }).  The percent sign, "%", denotes
% the start of a comment; text after it will be ignored by LaTeX.  
% You might also notice in some of the examples below the use of "\ "
% after a period; this prevents LaTeX from interpreting the period as
% the end of a sentence and putting extra space after it.  
% 
% You should check your paper by processing it with LaTeX.  For
% details about how to run LaTeX as well as how to print out the User
% Guide, consult the README file.  You should also consult the sample
% LaTeX papers, sample1.tex and sample2.tex, for examples of including
% figures, html links, special symbols, and other advanced features.
%
% If you do not have access to the LaTeX software or a laser printer
% at your site, you can still prepare your paper following the
% instructions in the User Guide.  In such cases, the editors will
% process the file and make any necessary editorial adjustments.
% 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% 
\documentclass[11pt,twoside]{article}  % Leave intact
\usepackage{adassconf}

% If you have the old LaTeX 2.09, and not the current LaTeX2e, comment
% out the \documentclass and \usepackage lines above and uncomment
% the following:

%\documentstyle[11pt,twoside,adassconf]{article}

\begin{document}   % Leave intact

%-----------------------------------------------------------------------
%			    Paper ID Code
%-----------------------------------------------------------------------
% Enter the proper paper identification code.  The ID code for your
% paper is the session number associated with your presentation as
% published in the official conference proceedings.  You can           
% find this number locating your abstract in the printed proceedings
% that you received at the meeting or on-line at the conference web
% site; the ID code is the letter/number sequence proceeding the title 
% of your presentation. 
%
% This will not appear in your paper; however, it allows different
% papers in the proceedings to cross-reference each other.  Note that
% you should only have one \paperID, and it should not include a
% trailing period.
%
% EXAMPLE: \paperID{O4-1}
% EXAMPLE: \paperID{P7-7}
%

\paperID{P10-4}
%%%% ID=P10-4

%-----------------------------------------------------------------------
%		            Paper Title 
%-----------------------------------------------------------------------
% Enter the title of the paper.
%
% EXAMPLE: \title{A Breakthrough in Astronomical Software Development}
% 
% If your title is so long as to fill the page header when you print it,
% then please supply a short form as a \titlemark.
%
% EXAMPLE: 
%  \title{Rapid Development for Distributed Computing, with Implications
%         for the Virtual Observatory}
%  \titlemark{Rapid Development for Distributed Computing}
%

\title{SIRTF Tools for DIRT }
%This work was supported in part by a NASA AISRP grant
%NAG 5-10751 and the SIRTF Legacy Science Program provided by
%NASA through an award issued by JPL under NASA contract
%1407.

%-----------------------------------------------------------------------
%		          Authors of Paper
%-----------------------------------------------------------------------
% Enter the authors followed by their affiliations.  The \author and
% \affil commands may appear multiple times as necessary (see example
% below).  List each author by giving the first name or initials first
% followed by the last name.  Authors with the same affiliations
% should grouped together. 
%
% EXAMPLE: \author{Raymond Plante, Doug Roberts, 
%                  R.\ M.\ Crutcher\altaffilmark{1}}
%          \affil{National Center for Supercomputing Applications, 
%                 University of Illinois Urbana-Champaign, Urbana, IL
%                 61801}
%          \author{Tom Troland}
%          \affil{University of Kentucky}
%
%          \altaffiltext{1}{Astronomy Department, UIUC}
%
% In this example, the first three authors, "Plante", "Roberts", and
% "Crutcher" are affiliated with "NCSA".  "Crutcher" has an alternate 
% affiliation with the "Astronomy Department".  The fourth author,
% "Troland", is affiliated with "University of Kentucky"

\author{Marc W. Pound, Mark G. Wolfire, N.S. Amarnath }
\affil{Astronomy Department, University of Maryland,College Park, MD 20742 }

%-----------------------------------------------------------------------
%			 Contact Information
%-----------------------------------------------------------------------
% This information will not appear in the paper but will be used by
% the editors in case you need to be contacted concerning your
% submission.  Enter your name as the contact along with your email
% address.
% 
% EXAMPLE:  \contact{Dennis Crabtree}
%           \email{crabtree@cfht.hawaii.edu}
%

\contact{Marc Pound}
\email{mpound@astro.umd.edu}

%-----------------------------------------------------------------------
%		      Author Index Specification
%-----------------------------------------------------------------------
% Specify how each author name should appear in the author index.  The 
% \paindex{ } should be used to indicate the primary author, and the
% \aindex for all other co-authors.  You MUST use the following
% syntax: 
%
% SYNTAX:  \aindex{Lastname, F. M.}
% 
% where F is the first initial and M is the second initial (if
% used).  This guarantees that authors that appear in multiple papers
% will appear only once in the author index.  
%
% EXAMPLE: \paindex{Crabtree, D.}
%          \aindex{Manset, N.}        
%          \aindex{Veillet, C.}        
%
% NOTE: this information is also used to build the author list that
% appears in the table of contents.  Authors will be listed in the order
% of the \paindex and \aindex commmands.
%

\paindex{Pound, M. W.}
\aindex{Wolfire, M. G.}     % Remove this line if there is only one author
\aindex{Amarnath, N. S.}     % Remove this line if there is only one author

%-----------------------------------------------------------------------
%		      Author list for page header	
%-----------------------------------------------------------------------
% Please supply a list of author last names for the page header. in
% one of these formats:
%
% EXAMPLES:
% \authormark{Lastname}
% \authormark{Lastname1 \& Lastname2}
% \authormark{Lastname1, Lastname2, ... \& LastnameN}
% \authormark{Lastname et al.}
%
% Use the "et al." form in the case of seven or more authors, or if
% the preferred form is too long to fit in the header.

\authormark{Pound, Wolfire, \& Amarnath }

%-----------------------------------------------------------------------
%			Subject Index keywords
%-----------------------------------------------------------------------
% Enter a comma separated list of up to 6 keywords describing your
% paper.  These will NOT be printed as part of your paper; however,
% they will be used to generate the subject index for the proceedings.
% There is no standard list; however, you can consult the indices
% for past proceedings (http://adass.org/adass/proceedings/).
%
% EXAMPLE:  \keywords{visualization, astronomy: radio, parallel
%                     computing, AIPS++, Galactic Center}
%
% In this example, the author noticed that "radio astronomy" appeared
% in the ADASS VII Index as "astronomy" being the major keyword and
% "radio" as the minor keyword.  The colon is used to introduce another
% level into the index.

\keywords{Java, Virtual Observatory, visualization, astronomy: infrared, SIRTF}

%-----------------------------------------------------------------------
%			       Abstract
%-----------------------------------------------------------------------
% Type abstract in the space below.  Consult the User Guide and Latex
% Information file for a list of supported macros (e.g. for typesetting 
% special symbols). Do not leave a blank line between \begin{abstract} 
% and the start of your text.

\begin{abstract}          % Leave intact
% Place the text of your abstract here - NO BLANK LINES
The Dust InfraRed ToolBox (DIRT -- a part of the Web Infrared
ToolShed, or \htmladdnormallinkfoot{WITS}{http://dustem.astro.umd.edu})
is a
Java applet for modeling astrophysical processes in circumstellar
shells around young and evolved stars.\footnote{This work was supported in part by a NASA AISRP grant
NAG 5-10751 and the SIRTF Legacy Science Program provided by
NASA through an award issued by JPL under NASA contract
1407.}
DIRT has been used by the
astrophysics community for about 5 years.  Users can automatically
and efficiently search grids of pre-calculated models to fit
their data.   A large set of physical parameters and dust types
are included in the model database, which contains over 500,000
models.   \\
We are adding new functionality to DIRT to support new missions like
SIRTF and SOFIA.  A new Instrument module allows for plotting of the
model points convolved with the spatial and spectral responses of
the selected instrument.  This lets users better fit data from
specific instruments. Currently, we have implemented modules for
the Infrared Array Camera (IRAC) and Multiband Imaging Photometer
(MIPS) on SIRTF.  \\
The models are based on the dust radiation transfer code of Wolfire
\& Cassinelli (1986) which accounts for multiple grain sizes and
compositions. The model outputs are averaged over the instrument
bands using the same weighting ($\nu~F_{\nu} =$ constant) as the SIRTF data
pipeline which allows the SIRTF data products to be compared directly
with the model database.  
\end{abstract}

%-----------------------------------------------------------------------
%			      Main Body
%-----------------------------------------------------------------------
% Place the text for the main body of the paper here.  You should use
% the \section command to label the various sections; use of
% \subsection is optional.  Significant words in section titles should
% be capitalized.  Sections and subsections will be numbered
% automatically. 
%
% EXAMPLE:  \section{Introduction}
%           ...
%           \subsection{Our View of the World}
%           ...
%           \section{A New Approach}
%
% It is recommended that you look at the sample papers, sample1.tex
% and sample2.tex, for examples for formatting references, footnotes,
% figures, equations, html links, lists, and other special features.  
\section{Using DIRT}
A typical user query will return about 50-100 models, which
the user can then interactively filter as a function of 8 model
parameters (e.g., extinction, size, flux, luminosity). A flexible,
multi-dimensional plotter (Figure 1) allows users to view the models,
rotate them, tag specific parameters with color or symbol size,
and probe individual model points (Pound et al. 2000; Amarnath et al. 2003).
For any given model, auxiliary plots such as dust grain properties,
radial intensity profiles, and the flux as a function of wavelength
and beamsize can be viewed. The user can fit
observed data to several models simultaneously and see the results
of the fit; the best fit is automatically selected for plotting.

\section {The Instruments}
The Infrared Array Camera (IRAC) and Multiband Imaging Photometer for
SIRTF (MIPS) are two of SIRTF's three science instruments.  IRAC is
a four-channel camera that provides simultaneous $5.12\arcmin \times
5.12\arcmin$ images at 3.6, 4.5, 5.8, and 8 \micron.  MIPS provides
imaging at 24, 70, 160 \micron and limited spectroscopy from 50 to
100 \micron. The MIPS field of view varies from about $5\arcmin
\times 5\arcmin$ at the shortest wavelength to about $0.5\arcmin
\times 5\arcmin$ at the longest wavelength.

\section{ ``Cores To Disks'' SIRTF Legacy Project}
%The SIRTF Legacy Science Program is comprised of six projects
%selected following a solicitation of proposals and competitive
%peer review. The Program was motivated by a desire to enable major
%science observing projects early in the SIRTF mission, with the
%goal of creating a substantial and coherent database of archived
%observations that can be utilized by subsequent SIRTF researchers.

DIRT is specifically supporting the SIRTF Legacy project ``Cores To Disks,''
or C2D. C2D is meant to investigate the life cycle of star formation,
following evolution from starless cores to planet-forming disks. It
will comprise a complete database for nearby ($< 350$ pc), low mass
star formation. The C2D project will provide
IRAC and MIPS maps of 5 large molecular clouds;
photometry of 200 stars; and
spectroscopy of disk material for about 200 targets.
In support of C2D, we have substantially expanded our previous model
database, computing nearly 218,000 models of very low-luminosity 
($10^{-5}~L_\odot < L < 10~L_\odot$) and low-mass 
protostars ($M < 1~M_\odot$). At the request
of the C2D team (of which UMD is partner), we are now computing a
grid of models using Ossenkopf \& Henning (1994) ice mantle grains. Upon
completion of the new dust grain grid, we will have doubled our
database size to $\sim10^6$ models.

\section{DIRT and the Virtual Observatory}
We are currently investigating how to ``VO-enable'' both DIRT and the
model database itself.  The model database provides a large uniform
set of spectra which would be a good use-case for putting theory in the VO
(Teuben et al. 2002).  Other papers in this volume investigate both
a general spectral format and instrument models for the VO.
These developments could provide a useful interface
for the ``raw'' and instrument-convolved models.

\begin{figure}
\plotone{P10-4_1.eps}
\caption{
DIRT's main Model Viewer showing computed models (light cubes),
IRAC band averages of the models (dark circles), MIPS band
averages of the models (light circle), the user's input data
(large circles). The model the user has selected is highlighted
(dark cubes). Once a model is selected, the user can click on 
{\bf Details} to further investigate that model (e.g., Figure 2). } 
\end{figure}

\begin{figure}
\plotone{P10-4_2.eps}
\caption{
Source model Intensity as a function of impact parameter p and
wavelength for the model selected in Figure 1. If no Instrument is
selected in the main Model Viewer, the plot will show the computed
model only (top). If an Instrument has been selected, the Instrument
responses for that source model are shown (bottom).
}
\end{figure}



%-----------------------------------------------------------------------
%			      References
%-----------------------------------------------------------------------
% List your references below within the reference environment
% (i.e. between the \begin{references} and \end{references} tags).
% Each new reference should begin with a \reference command which sets
% up the proper indentation.  Observe the following order when listing
% bibliographical information for each reference:  author name(s),
% publication year, journal name, volume, and page number for
% articles.  Note that many journal names are available as macros; see
% the User Guide listing "macro-ized" journals.   
%
% EXAMPLE:  \reference Hagiwara, K., \& Zeppenfeld, D.\  1986, 
%                Nucl.Phys., 274, 1
%           \reference H\'enon, M.\  1961, Ann.d'Ap., 24, 369
%           \reference King, I.\ R.\  1966, \aj, 71, 276
%           \reference King, I.\ R.\  1975, in Dynamics of Stellar 
%                Systems, ed.\ A.\ Hayli (Dordrecht: Reidel), 99
%           \reference Tody, D.\  1998, \adassvii, 146
%           \reference Zacharias, N.\ \& Zacharias, M.\ 2003,
%                \adassxii, \paperref{P7.6}
% 
% Note the following tricks used in the example above:
%
%   o  \& is used to format an ampersand symbol (&).
%   o  \'e puts an accent agu over the letter e.  See the User Guide
%      and the sample files for details on formatting special
%      characters.  
%   o  "\ " after a period prevents LaTeX from interpreting the period 
%      as an end of a sentence.
%   o  \aj is a macro that expands to "Astron. J."  See the User Guide
%      for a full list of journal macros
%   o  \adassvii is a macro that expands to the full title, editor,
%      and publishing information for the ADASS VII conference
%      proceedings.  Such macros are defined for ADASS conferences I
%      through XI.
%   o  When referencing a paper in the current volume, use the
%      \adassxii and \paperref macros.  The argument to \paperref is
%      the paper ID code for the paper you are referencing.  See the 
%      note in the "Paper ID Code" section above for details on how to 
%      determine the paper ID code for the paper you reference.  
%
\begin{references}

\reference Amarnath, N.~S., Pound, M.~W., \& Wolfire, M.~G.\ 2003, \adassxii, 12, 381

\reference Ossenkopf, V.~\& Henning, T.\ 1994, \aap, 291, 943 

\reference Pound, M.~W., Wolfire, M.~G., Mundy, L.~G., Teuben, P.~J., \& Lord, S.\ 2000, \adassix, 9, 628

\reference Teuben, P., %%% SIMPLIFIED FO 
    et al.\  %%% DeYoung, D., Hut, P., Levy, S., Makino, J.,
             %%% McMillan, S., Portegies Zwart, S., \& Slavin, S.\ 
    2002, \adassxi, 11, 7

\reference Wolfire, M.~G.~\& Cassinelli, J.~P.\ 1986, \apj, 310, 207 

%\reference McDowell, J. C., \adassxiii, \paperref{P3.4}

\end{references}

% Do not place any material after the references section

\end{document}  % Leave intact
