%ADASS_PROCEEDINGS_FORM%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% SAMPLE1.TEX -- ADASS XII (2002) ASP Conference Proceedings sample
% paper with minimal markup. Based on the sample from ADASS XI (01).
%
% This is a simple example.  If you want to see a more comprehensive
% sample paper,  take a look at sample2.tex.
%
% 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.  
%
% 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.
%

\paperID{P4-26}
%%%% ID=P4-26

%-----------------------------------------------------------------------
%		            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{Modeling and Developing the Information System for the SuperAGILE Experiment}
\titlemark{The Information System for the SuperAGILE Experiment}

%-----------------------------------------------------------------------
%		          Authors of Paper
%-----------------------------------------------------------------------
% Enter the authors followed by their affiliations.  The \author and
% \affil commands may appear multiple times as necessary.  List each
% author by giving the first name or initials first followed by the
% last name.  Authors with the same affiliations should grouped
% together. 
%
% Try to limit the front matter to no more than three \author
% commands.  Group authors with the same affiliations.  Too many
% \author commands fills the first page of the paper with little
% actual text.

\author{Francesco Lazzarotto}
\affil{DISP Tor Vergata \& IASF-CNR, via del Fosso del Cavaliere, 100, 00133, Rome, Italy, e-mail: lazza@rm.iasf.cnr.it}
\author{Enrico Costa, Ettore Del Monte \& Marco Feroci}
\affil{IASF-CNR, Rome, Italy}
%\altaffiltext{1}{Physics Department, The Duck Institute}

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

\contact{Francesco Lazzarotto}
\email{lazza@rm.iasf.cnr.it}

%-----------------------------------------------------------------------
%		      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{Lazzarotto, F.}
\aindex{Costa, E.}     
\aindex{Del Monte, E.} 
\aindex{Feroci, M.}  
%-----------------------------------------------------------------------
%                     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{Lazzarotto, Del Monte, Feroci \& Costa}

%-----------------------------------------------------------------------
%			Subject Index keywords
%-----------------------------------------------------------------------
% Enter 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 ADASS
% proceedings (http://adass.org/adass/proceedings/).

\keywords{DBMS, SQL, object oriented, data: models, Entity-Relationship,
          X-gamma detectors}

%-----------------------------------------------------------------------
%			       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
We will present some formal description of the SuperAGILE (SA) detection system data, the relationships among them and the operations applied on data, with the aid of instruments such as Entity-Relationship (E-R) and UML diagrams. We just realized  functions of reception, pre-processing, archiving and analysis on SA data making use of Object Oriented and SQL open source software instruments.
\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. 

\section{Introduction}
The data stream expected from the SuperAGILE instrument, onboard the AGILE gamma-ray mission, are continuous and massive flows (20 kb/s) of raw information sent to ground for a minimum of 3 years, plus a larger rate during ground tests (see figure \ref{P4-26:SAflightuse-fig-1-2}).
Data coming from the instrument concern physical measurements and equipment housekeepings. 
We have developed and are improving an information system to handle and archive the data produced at first by the prototypes and later on by the SA flight model. A big effort in the design phase has led us to achieve an integrated modular software system responding to most of the functions needed to extract knowledge from SA archives.
%Reader, this is my paper.  Paper, this is our reader (be polite).

\section{Requirements and Conceptual Design}
The SuperAGILE experiment is described by processes, the processes scheme induces a scheme on the SA information system. We arrive at the goal of extracting scientific knowledge from SA data following these steps: first we pursued an accurate operation of requirements definition joined with reflections on our past work (Feroci et al. 1999; Lazzarotto 2001) and the study of some standards coming from other researches (see IVOA working team 2003).  Then we developed an E-R scheme to have a conceptual level project, modeling the data items and operations on them. It describes concepts of interest to the application s such as detectors, analogue and electronical hardware, software components and operators and the relationships among these concepts, in a simple but precise way, not 
computer specific (see Fig. \ref{P4-26:SAcomposed-fig-3-4}). At this level we isolated some metadata describing measurement data. The metadata will be contained in the persistent Data Base Management System (DBMS), massive measurement data are stored in a repository (e.g. large computer hard-disks).

  \begin{figure}
    \epsscale{.50}
    \plottwo{P4-26_1.eps}{P4-26_2.eps}
    \caption{Use cases for SA ground and flight prototypes data applications} \label{P4-26:SAflightuse-fig-1-2}
  \end{figure}


\section{Performance Study and Logical Design}
Logical rendering of the conceptual model materializes in the realization of a relational database scheme (Fig. \ref{P4-26:SAmeas_sess-fig-5-6}) for 'run' (measurement or simulation) metadata. Also the scheme of scientific contents data is realized following the object oriented and the relational paradigms. The definition of a metaformat for experimental data and a formal model for the operations on them, make it possible to do a performance study on the applications (see part of the model in the Operation Table (Table~1)).

\begin{table}
\begin{center}
\caption[SA data operation table]{SA data operation table}
\begin{tabular}{|c|c|c|}
\hline
{\bf Operation}  & {\bf Type(I/B)}& {\bf Frequency}\\
\hline
ReadData&I&50 per day\\
\hline
CreateAddLUT&B&1 per month\\
\hline
CreateResMat&B&1 per day\\
\hline
AddCalibrate&I&50 per day\\
\hline
EnCalibrate&I&50 per day\\
\hline
GetDetImg&I&20 per day\\
\hline
GetSpectrum&I&20 per day\\
\hline
GetLightCurve&I&20 per day\\
\hline
GetSkyImage&I&15 per day\\
\hline
\end{tabular}
\end{center}
\label{P4-26:specoptbl}
\end{table}

\section{Physical Scheme of DBMS and Architecture of the Analysis Software}
To handle the experiment archive we use a DBMS based on SQL to store metadata realizing a RAM persistent short projection of the repository. We save archiving, summarizing instrumental information and textual information from the acquisition logfile. The content of the database image at a certain time is given in html format and put in a public web area, from where every authorized user can read useful information and download desired files with ftp links. The procedures are written in C++ embedding mySQL and science libraries, Root (Brun 1997; see also \makeURL{http://root.cern.ch}), cfitsio (Pence 1999; see also \makeURL{http://heasarc.gsfc.nasa.gov/docs/software/fitsio/fitsio.html} ), AstroRoot (Beck 2004; see also \makeURL{http://isdc.unige.ch/index.cgi?Soft+astroroot} ). The implementation is also realized with the help of a C/C++ interpreter "Cint" that permits development and easy tests of C++ code macros. We also used postgresSQL to implement DBMS functions, the linking with the Root library is more efficient with mySQL. For data analysis software we use OO approach, (a simple classes scheme is reported in figure \ref{P4-26:SAmeas_sess-fig-5-6}), it implements functions analysis operations and produces higher level of abstraction scientific data products such as light curves, detector images and spectra.
\begin{figure}
\epsscale{.50}
\plottwo{P4-26_3.eps}{P4-26_4.eps}
\caption{Composition and gerarchy of SA data} \label{P4-26:SAcomposed-fig-3-4}
\end{figure}

%\begin{figure}
%\epsscale{.50}
%\plotone{SAdataTree.eps}
%\caption{SA data tree} \label{P4-26:SAdatatree-fig-4}
%\end{figure}

\begin{figure}
\epsscale{.50}
\plottwo{P4-26_5.eps}{P4-26_6.eps}
\caption{SA measurement session conceptual scheme and classes for sadas software}\label{P4-26:SAmeas_sess-fig-5-6}
\end{figure}

\section{The Final Goal of the System: Scientific Knowledge Extraction Applications}
The idea is to save structured reports regarding automatic analysis on large amounts of data, in other metadata saved in the DBMS archive. Then it will be possible apply comparative studies on SA data sets, with the application of advanced statistical and Computer Science techniques. The results of analysis operators will be stored in compact data sets rendered, for istance, in XML. We created a raw prototype of this system in 2001 using SAX mission data archives, then we defined the whole Scientific Knowledge Extraction (SKE) process for our contest expressed above, suggesting the approach we are developing and testing now on laboratory and simulations SA data with the purpose of applying the refined and tested SKE system also to SA flight data soon after its launch in 2005.
%\section{}

% You can also add an acknowledgments section as indicated below.

%\acknowledgments

%\clearpage
%-----------------------------------------------------------------------
%			      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 for a listing "macro-ized" journals.   
%
% Note the following are some of the tricks that can be used:
%
%   o  \& is used to format an ampersand symbol (&).
%   o  \'e puts an accent grave over the letter e.  See the User Guide
%      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 IX.
%   o  When referencing a paper in the current volume, use the
%      \adassix 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 Beck, M. et al. \ 2004, \adassxiii, \paperref{P4-19}
\reference Brun, R. \& Rademakers, F. \ 1997 ROOT - An Object Oriented Data Analysis Framework, Proceedings AIHENP'96 Workshop, Lausanne, Sep. 1996, Nucl. Inst. \& Meth. in Phys. Res. A 389, 81-86
\reference Derriere S. et al \ 2004, \adassxiii, \paperref{P3-17}
\reference Derriere, S., Ochsenbein, F., Boch, T., \& Rixon, G. T. \ 
    2003, \adassxii, 69
\reference Feroci, M. et al, 1999, astro-ph/9912488, Proceedings of the $5^{th}$ Huntsville Gamma-Ray Bursts Symposium, 711-715 
\reference IVOA working team \ 2003, Resource Metadata for the VO (\makeURL{http://www.ivoa.net})
\reference Lazzarotto, F., 2001, Computer Science Thesis at ``La Sapienza'', Rome 
\reference Pence, W. D. \ 1999. \adassviii, 487
\reference Wenger, M. et al. \ 2000, \aaps, 143, 9

\end{references}

% Do not place any material after the references section

\end{document}  % Leave intact
