%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{P5-1}
%%%% ID=P5-1

%-----------------------------------------------------------------------
%		            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{New User Requirements for Astronomical Data Visualization}
%\titlemark{ }

%-----------------------------------------------------------------------
%		          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{W. A. Joye and E. Mandel}
\affil{Smithsonian Astrophysical Observatory
       60 Garden St., Cambridge, MA 02138}

%-----------------------------------------------------------------------
%			 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{William Joye}
\email{wjoye@cfa.harvard.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{Joye, W. A.}
\aindex{Mandel, E.}     % 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{Joye \& Mandel}

%-----------------------------------------------------------------------
%			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{SAOImage DS9, DS9, visualization: DS9, Virtual Observatory: DS9}

%-----------------------------------------------------------------------
%			       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
The astronomical community has benefited greatly from the dramatic
increase of speed and storage capacity of computers and the wide
availability of high speed Internet access. Armed with the latest
hardware, users have placed increased demands on astronomical data
visualization software that no one could have imagined just a few
years ago.

Until recently, a typical FITS file was composed of a single image
less than 100Mb in size. Now FITS files composed of mosaics images,
multiple-extension FITS images, FITS data cubes, and RGB composite
images are common. These FITS files now test the limits of hardware
and operating systems with regard to file size and address space.  And
along with this explosion of new data file representations comes
demands for more flexibility in visualization, support for external
and remote analysis, and seamless Web integration.

We will present a discussion of new user requirements and solutions we
have encountered in development and support of SAOImage DS9.
\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{FITS File Interpretation}

There has been an explosion of new data representations within the
FITS file framework. In the past, a FITS file consisted of a primary
header, followed by image data. Now, multiple extension FITS files are
common. Users are taking advantage of the flexibility of the FITS
format to store a dynamic range of data representations. They
naturally demand the ability to display and render these data in a
variety of ways. Today's data visualization software must be flexible
enough to support such options. SAOImage DS9 provides the user several
different ways to interpret and render a FITS file. For example, a
multiple extension FITS file can be opened as a Single Image, a Mosaic
Image, an RGB Image, or a 3D Data Cube.

\begin{figure}
\plottwo{P5-1_1.eps}{P5-1_2.eps}
\caption{FITS Multiple Extension Images}
\end{figure}

\section{Breaking the 2Gb File Size Barrier}

Concomitant with the explosion of FITS file representations has been
an explosion of FITS file size. Users routinely require the ability to
display images that have a combined sizes of over 2Gb. This can be
accomplished by implementing Large File Support (LFS). LFS allows the
user to read, write, and seek into files over 2Gb in size. To support
LFS, software must be modified to support I/O addressing beyond 2Gb and
must be linked against 64-bit-aware standard libraries. GCC 3.x now
supports LFS on most platforms. By recompiling with the correct
options, GCC will seamlessly substitute 64-bit-aware library
procedures for their 32-bit counterparts. SAOImage DS9 now supports
LFS for most platforms.

\section{Remote Analysis}

One of the exciting trends in astronomical analysis software has been
the growth in remote analysis projects. With the availability of large
on-line data archives, a wide range of specialized analysis software,
and high speed Internet connectivity, it is now possible to provide
users with a complete analysis suite of tools, not restricted to one
or two popular packages, but incorporating parts of many different
packages.

SAOImage DS9 supports a wide range of remote analysis services. Any
XPA-enabled site can permit DS9 to register itself with the XPA name
server running at that site. The DS9 web interface then will display
the site's web page, which can be used to send FITS data to DS9 for
display.

\begin{figure}
\plottwo{P5-1_5.eps}{P5-1_6.eps}
\caption{Chandra Education Remote Analysis Site}
\end{figure}

For example, the Chandra Education site,
\htmladdURL{http://chandra-ed.harvard.edu}, offers Chandra-based
educational activities. Once DS9 is connected to Chandra-Ed, FITS
images can be sent back to DS9 for display and further analysis as
part of these activities.

Chandra-Ed sends to DS9 compressed FITS images along with definitions
of analysis tools that can operate on the original event data
maintained at the Chandra-Ed site. These CGI-based definitions become
part of the DS9 Analysis Menu. Thus, after setting up regions of
interest, the user can select a remote analysis program.  The
associated CGI call sends parameter information back to the Chandra-Ed
site, where the remote analysis program is executed on the original
event data. Results are sent back to DS9 for display. All such
analysis requests are processed in a secure chroot'ed environment.

In this way, DS9 can be used as a local front-end to remote
archive/education servers that offer both data and analysis support.
Moreover, this can be done without moving large data sets or complex
software to the local machine.

\begin{figure}
\plottwo{P5-1_3.eps}{P5-1_4.eps}
\caption{Web Based Archive Servers}
\end{figure}

\section{The Virtual Observatory}

The term {\it Virtual Observatory} means different things to different
people. The VO promises to '\htmladdnormallinkfoot{``make data easier 
to use, easier to find, and easier to join with other data''}{http://www.us-vo.org}. Users require easy access to
on-line image and catalog servers. This support must be fully
integrated into data visualization software and provide full access to
existing and future web services as they become
available. $^1$\htmladdURL{http://www.us-vo.org/}

SAOImage DS9 now supports access to web-based image archive servers
via HTTP. Support for MAST, SkyView, 2MASS, ISSA, NVSS, First, NED and
many others are provided. FITS images are automatically displayed
within DS9, while other image formats, such as GIF, TIFF, JPEG, are
displayed within the web display window. When a user first invokes an
archive server Web page, DS9 automatically fills in certain form
fields such as RA and DEC with coordinates from the current
image. This allows the user to browse and retrieve images from the
archive quickly and easily. As new VO web services become
available, they will be supported within DS9.

\section{Availability}

DS9 is available on the Web at
\htmladdURL{http://hea-www.harvard.edu/saord/ds9} or via anonymous FTP
from \htmladdURL{ftp://sao-ftp.harvard.edu/pub/rd/ds9}.

\section{Acknowledgments}

This work was performed in large part with support from the
Educational Outreach Program of the Chandra X-ray Science Center
(NAS8-39073) and from the High Energy Astrophysics Science Archive
Center (NCC5-568).

%-----------------------------------------------------------------------
%			      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}




%\end{references}

% Do not place any material after the references section

\end{document}  % Leave intact
