%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{O7-5}
%%%% ID=O7-5

%-----------------------------------------------------------------------
%		            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{AstroGrid: Initial Deployment of the UK's Virtual Observatory}
%\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{Nicholas A.\ Walton}
\affil{Institute of Astronomy, University of Cambridge, Madingley Road, 
Cambridge, CB3 0HA, UK}
\author{Andrew Lawrence}
\affil{Institute for Astronomy, University of Edinburgh, Royal
  Observatory, 
Blackford Hill, Edinburgh, EH9 3HJ, UK}
\author{Tony Linde}
\affil{Department of Physics \& Astronomy, University of Leicester,
University Road, Leicester, LE1 7RH, UK}

%-----------------------------------------------------------------------
%			 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{Nic Walton}
\email{naw@ast.cam.ac.uk}

%-----------------------------------------------------------------------
%		      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{Walton, N. A.}
\aindex{Lawrence, A.}     
\aindex{Linde, T.}     


%-----------------------------------------------------------------------
%		      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{Walton et al.}

%-----------------------------------------------------------------------
%			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{AstroGrid, Virtual Observatory, distributed: systems}

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

AstroGrid, a UK eScience project with collaborating groups drawn from
the major UK data archive centres, is creating the UK's virtual
observatory.

AstroGrid has now completed its requirements capture and design
stages, and has begun to release software capabilities on a three
monthly cycle. It is using the iterative process, with eight
iterations, with each successive iteration release building a working
system comprising increasing capabilities.

AstroGrid's first functional release with it's 'Iteration 2' product,
and the capabilities and functionality that this provides, is
described. AstroGrid's technical input into joint products in
conjunction with the European Astrophysical Virtual Observatory, and
the Australian VO, is discussed.  

The component based AstroGrid architecture and how external
projects may be able to deploy components of interest in constructing
there 'VO' - for instance the use of MySpace to provide secure
intermediate 'grid' user storage areas, is discussed.

\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{Introduction}

\htmladdnormallinkfoot{AstroGrid}{http://www.astrogrid.org/} is a UK
eScience project with collaborating groups drawn from the major UK
data archive centres, is creating the UK's first virtual
observatory. Together with the other major world-wide virtual
observatory projects (see the \htmladdnormallinkfoot{International
Virtual Observatory Alliance}{http://www.ivoa.net}), AstroGrid is
creating a set of co-operating and interoperable software systems that
will: allow users to interrogate multiple data centres in a seamless
and transparent way; provide powerful new analysis and visualisation
tools; and give data centres and providers a standard framework for
publishing and delivering services using their data.

AstroGrid is developing a standardised framework to allow creative
diversity, which will:

\begin{itemize}
\item to improve the quality, efficiency, ease, speed, and
  cost-effectiveness of on-line astronomical research 
\item to make
  comparison and integration of data from diverse sources seamless and
  transparent 
\item to remove data analysis barriers to interdisciplinary
  research 
\item to make science involving manipulation of large datasets
  as easy and as powerful as possible.
\end{itemize}


\section{The AstroGrid Architecture}

In it's fist year, AstroGrid produced a
\htmladdnormallinkfoot{detailed Phase-A
report}{http://wiki.astrogrid.org/bin/view/Astrogrid/PhaseAReport},
setting out the science requirements for the project, and outlining
the general architecture and software components that would be
produced during the two year 'build phase' of the project. The current
AstroGrid architecture, is diagrammatically shown in
Figure~\ref{O7-5:arch}. 

It should be noted that AstroGrid is being constructed in a modular
fashion. Thus, various modules, such as MySpace, could be deployed by
other projects, in a standalone manner, or in combination with other
AstroGrid modules, such as the Registry module. AstroGrid is in active
discussion with other global VO projects as to how they might be able
to benefit from use of part or all of the AstroGrid component
framework.

An overview of the architecture can be found on the AstroGrid Wiki
site at
\htmladdURL{http://wiki.astrogrid.org/bin/view/Astrogrid/ArchOverview}.
This also shows various deployment scenarios, of how user groups, such
as data centres, tools providers, other VO projects, might employ
AstroGrid components in their specific situation.

\begin{figure}
\epsscale{.80}
\plotone{O7-5_1.eps}
\caption{The AstroGrid architecture} \label{O7-5:arch}
\end{figure}

For a more detailed description of a number of the components of
AstroGrid, see elsewhere in these proceedings: MySpace (Davenhall et
al. 2004), Registry (Auden et al. 2004).


\section{AstroGrid Development Activities}

AstroGrid has now completed its requirements capture and design
stages, and has begun to release software capabilities on a,
nominally, three monthly cycle. In its two year build phase, AstroGrid
is using the iterative process, with eight iterations, typically of
three months, with each successive iteration release building a
working system with progressively enhanced functionality.  The first
iteration was released March 31, 2003, with iteration two being
released June 30, 2003. These two iterations laid down the initial
component framework.

\subsection{The Iteration 2 Release}

This iteration included the following components:

\begin{itemize}
\item Portal: developed with Cocoon, and including portal pages for
          Workflow, MySpace Explorer, Data Viewer, with a simple
          interface to the AstroPass component
\item Registry \& AstroMQ: implemented with IVOA schema standards,
          with a registry management portal page
\item Data Centre, Dataset Access, Job Control:  allows a query of,
  and data return from a dataset/database
\item MySpace: enabling the creation of files in MySpace (not tables),
          a MySpace registry and data mover component. 
\end{itemize}


\subsection{The AstroGrid/ Australian-VO Visualiser}

AstroGrid and the Australian Virtual Observatory (Aus-VO) have jointly
produced a visualisation system for data cubes that allows real-time
control of the user's viewpoint via a "virtual camera". The visualiser
software runs on powerful compute clusters. The data inputs are user
selected and transfered to the computer process using grid service
technologies. This product is fully described in Rixon et al
(2004). It is an example of the types of applications that will be
made available through the AstroGrid infrastructure.. 


\subsection{AstroGrid and the Astrophysical Virtual Observatory (AVO) 1st 
Light Demonstrator} 

In the context of the
\htmladdnormallinkfoot{AVO}{http://www.euro-vo.org} 1st Light
demonstrator, Quinn et al., 2004, AstroGrid developed the web service
wrapper to the SExtractor source extraction application (Bertin \&
Arnouts, 1996). This enables user initiated re-extractions of image
data, a powerful additional capability. 


\section{AstroGrid Beta Testing}

With the recent deployment of its iteration 3 release, AstroGrid has
embarked on a rigorous 'beta-testing' programme. In the early stages,
when science functionality is somewhat limited, a small group of
interested scientists have been invited to gain hands on experience of
the AstroGrid system. Their feedback and input will help the
project understand issues such as functionality provision, usability
and reliability. As further iteration releases are rolled out, it is
anticipated that the 'beta-test' community will enlarge, as the system
begins to meet the needs of a wider range of research programmes.
Information concerning the Beta test programme is available at: 
\newline \htmladdURL{http://wiki.astrogrid.org/bin/view/Astrogrid/BetaTesting}


\section{The AstroGrid Future}

By the end of 2004 AstroGrid will have constructed a fully functional
prototype VO system, linking together major data centres in the UK,
and providing seamless access to high value data sets such as that
being generated from the UKIRT infrared camera through the
\htmladdnormallinkfoot{UKIDSS}{http://www.ukidss.org} survey.  In
order to ensure that the AstroGrid system is hardened into a robust
production system, further funding is being agreed through end 2007,
to support the necessary functional enhancements to the system. 




%-----------------------------------------------------------------------
%			      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 Auden, E.\ C., Linde, A.\ E., Noddle, K.\ T., Richards, A.\
    M.\ S., Walton, N.\ A., 2004, \adassxiii, \paperref{P3-24}

\reference Bertin, E., Arnouts, S., 1996, \aaps, 117, 393

\reference Davenhall, A.\ C., Qin, C.\ L., Noddle K.\ T. \& Walton,
    N.\ A.\ 2004, \adassxiii, \paperref{P3-21}

\reference Lawrence, A.\ 2003, in Proceedings of UK e-Science All Hands
Meeting, Nottingham, ed. S.\ J.\ Cox (Swindon: EPSRC), 428  % pp428-435.

\reference Quinn, P.\ J., et al., 2004, \adassxiii, \paperref{P3-13}

\reference Rixon, G.\ T., Barnes, D., Beeson, B., Ortiz, P., Yu, J.,
    2004, \adassxiii, \paperref{P5-2}


\end{references}

% Do not place any material after the references section

\end{document}  % Leave intact
