From Tauwiki

When all else fails, read the directions. --Allen's Axiom

Contents 1 Introduction 1.1 UVS Data Pipeline 1.2 Design Philosophy 1.3 Status 1.4 Open Bugs

[edit] Introduction

You are reading the user guide of TAUVEX data pipeline software. This document uses a cook book style approach and it takes you through the various steps involved in installing and running the UVS data pipeline software. The cook book is for the user community to get familiar with data pipeline software. If this is your first try with our software, we recommend you to read it carefully(!) and try out the examples. It is assumed that you are somewhat familiar with your operating system and basic astronomy.

[edit] UVS Data Pipeline

As we type this down, there are two upcoming UV space missions from India. The first one - Tauvex, aboard GSAT-4 is scheduled for a 2009 launch and second, the UVIT on Astrosat is expected to be operational at some time in the next decade. Data from the instruments require considerable processing before they can be used for science analysis. Thanks to the amount of data, this reduction is better done by an automated data pipeline. Given the specifications of these two missions, there is plenty of room to re-use software. Moreover, a sufficiently modular software will allow addition or substitution of individual programs by any mission specific module.

The UVS data pipeline software is designed to be a general purpose data pipeline modules, usable by various UV missions. In designing this software, the primary concerns were:

1. A general purpose software should be prepared to run on any platform.
2. Code should be highly modular, so that different projects can easily introduce mission specific programs along with the rest of the software.
3. The software should be handling large amounts of data and therefore automated analysis is preferred (not interactive).

The design considerations, discussed in the next section, were mainly driven by these factors.

[edit] Design Philosophy

1. The software must run on a variety of architectures and so is entirely programmed in Java (1.4.x)
2. Where possible, we use code developed by other projects.
3. The code must be modular so that individual parts may be substituted as required.
4. Each logical step will be a separate module with a standard data product which can be verified or used as a base for further analysis, independently.
5. The pipeline system will be run from a script or command file.
6. The program operation will be governed by a parameter file.
7. Each data file will be fully self-documenting. The history of that file will be contained in the data header.

[edit] Status

The development of UVS data pipeline began in January 2005. We reached a beta stage in October 2006. Development of additional modules and testing is continuing.

[edit] Open Bugs

ID	Severity	Assigned to	Description
327	normal	mohd.fayaz.r_AT_gmail.com	Keywords value not filled
328	normal	mohd.fayaz.r_AT_gmail.com	Binary table header keywords consideration
430	minor	reks_AT_users.sf.net	Author list must be updated
515	normal	reks_AT_users.sf.net	centre mispelt in many places
544	normal	reks_AT_users.sf.net	UVS_linearity_corr.jar not in bugzilla
215	blocker	vaicool16_AT_yahoo.co.in	display level1a-Image not loaded
251	enhancement	mohd.fayaz.r_AT_gmail.com	Keywords not organized
383	critical	reks_AT_iiap.res.in	hard crash in program
58	blocker	vaicool16_AT_yahoo.co.in	UVS_data_pipeline won't run on windows