Description of the status of design and developing activities of the data analysis software of SuperAGILE instrument of the AGILE Space Mission, one year before the launch.

1. SASOA
(SuperAGILE Standard Orbital
data Analysis pipeline)
Francesco Lazzarotto, INAF - 12/04/2006
francesco.lazzarotto@inaf.it

2. 12/04/2006 – slide 2/17
Francesco Lazzarotto, INAF
SASOA
design documents

3. 12/04/2006 – slide 3/17
Francesco Lazzarotto, INAF
SASOA General guidelines
s/w environment & libs
Languages Compiler Interpreter Standard
C++ Gcc 3.3.6 ISO/IEC 14882:2003
C Gcc 3.3.6
Fortran Gcc 3.3.6
IDL RSI IDL 6.2
Shell GNU bash, version 3.00.16 IEEE POSIX P1003.2/ISO 9945.2
Operating System Distribution Kernel
LINUX Suse 9.3 professional “2.6.11”
Libraries Function PackageVersion Language Type
Ftools Hea data handling Heasoft 6.0.4 C/C++/perl Bin
Cfitsio FITS I/O C Src
Qt GUI/gen. Utils 3.x C++ Src
Root Hep data analysis 5.10/00 C++ Src
Astrolib Astro. Data analysis 23/02/06IDL Src

4. 12/04/2006 – slide 4/17
Francesco Lazzarotto, INAF
SASOA
state diagram
(sd001)

5. 12/04/2006 – slide 5/17
Francesco Lazzarotto, INAF
SASOA
activity
diagram
(ad001)

6. 12/04/2006 – slide 6/17
Francesco Lazzarotto, INAF
SASOA Commandlist = list of commands separed by commas
and ending with a backslash char
A command is a pair <instruction, argument>
or <parameter, value>, commandline example:
sasoa[1] entrystage 0, exitstage 1, filename pippo.lv1
SASOA
working modes

7. 12/04/2006 – slide 7/17
Francesco Lazzarotto, INAF
SASOA
handling exceptions
Exceptions in the SASOA are handled with the try-throw-catch
construct, this mechanism and a hierarchy of exceptions allow to
jump from the normal flow of the application to the suitable
recovery action.

8. 12/04/2006 – slide 8/17
Francesco Lazzarotto, INAF
SASOA
data quality factor
•Tasks performed by SASOA steps produce merit parameters.
•During the elaboration, the pipeline handler controls the parameter
values and the pipeline execution can be conditioned by the quality
factor, launching alternative tasks, reexecuting some steps.
•At the end of the execution a global quality factor express the level
of reliability of SASOA products.

9. 12/04/2006 – slide 9/17
Francesco Lazzarotto, INAF
SASOA
elaboration steps
Stage 0 [Data reduction]
Stage 1 [Photon List Building]
Stage 2 [Multiple sources extraction]
Stage 3 [Single source analysis]

10. 12/04/2006 – slide 10/17
Francesco Lazzarotto, INAF
● 0a - Engineering Quality Check and
Filter
● 0b - Contact Telemetry Rebuild
● 0c - Data Type Separation
● 0d - Electr. Cal. Data Processing (LUTs)
● 0e - Gain Equalization (per Detector)
● 0f - Absolute Time Building (+OBT
correction)
● 0g - Dead Time Computing
(deadtime.fits)
● 0h - Level_1.9 Event List Generation
SASOA
Stage 0

11. 12/04/2006 – slide 11/17
Francesco Lazzarotto, INAF
SASOA
Stage 1
● 1a - Data Quality Filtering
● 1b - PLOSAP Accumulation with Dead Time
Corr.

12. 12/04/2006 – slide 12/17
Francesco Lazzarotto, INAF
SASOA
Stage 2
● 2a - Attitude and Systematic Offset
Correction
● 2b - Energy and Time Standard Filtering
● 2d - Detector Images Accumulation
● 2e - Multi- D IROS
● 2f - Generate Source Orbital Products

13. 12/04/2006 – slide 13/17
Francesco Lazzarotto, INAF
SASOA
Stage 3
● 3a - Select GTI for each source and each detector
● 3b - Extract Science Products (Energy Spectra, Light Curve,
PSD)
● 3c - Add- up 2 or 4 Detectors

14. 12/04/2006 – slide 14/17
Francesco Lazzarotto, INAF
SASOA
S/W Architecture

15. 12/04/2006 – slide 15/17
Francesco Lazzarotto, INAF
SASOA
Integration & developing
● Each pipeline module can be independently executed.
● A Global pipeline handler module can manage pipeline
stages in a (re)configurable mode.
● Yet developed routines are integrated in the pipeline
modules in one of these way:
● Calling source libraries from C++, C and F77;
● Launching batch IDL programs using shell scripts;
● Launching batch executables using shell scripts.
● User interface is provided by command line or GUI.

16. 12/04/2006 – slide 16/17
Francesco Lazzarotto, INAF
● Developing versions control is assured by CVS (Concurrent Version
System).
● Every code unit (routine/class/script) is associated with a 3digit version
number [v1.v2.v3] (e.g. 0.1.3).
● Changes in the code reflects changes in the version number:
● each simple modification produces changes in v3
● algorithm modifications produces changes in v2
● modifications of routines I/F produces changes in v1
● General test phases are provided, an alpha test is going to be made by the
developing team for xx/xx/2006 and a beta version should be delivered to
ASDC by zz/zz/2006.
SASOA
Developing & testing

17. 12/04/2006 – slide 17/17
Francesco Lazzarotto, INAF
References
1) Trifoglio, M. et al, AGILE-ITE-ID-007 AGILE Scientific Data Center TM
Pre-Processing System ICD, 2006.
2) AGILE Team @ ALENIA Milano checked by Vettorello, V., AGILE-LAB-
ID-004 AGILE telecommand and telemetry interface control document,
2006.
3) Donnarumma, I. et al, The on-ground calibrations of SuperAGILE: II.
Finite distance radioactive sources, proc. of SPIE, 2006 (in press).
4) Pacciani, L. et al, Instrumentation for Ground Test of SuperAgile
Detectors and Front-End Electronics, proc. of SPIE, 2004.