Naming Conventions for Files Produced During Data Processing, Level I
      _____________________________________________________________________

1. Raw IDL files


FITS data files are converted to IDL .sav files and automatically named:

examples: 

504511911.sav		drift scan, normally of 600 records
504511911CALOFbegin.sav CalOFF scan, artificially created from the first record of 504511911.sav
504511911CALOFend.sav   CalOFF scan, artificially created from the last record of 504511911.sav

These files are produced soon after completion of an observing session. They are then
transferred to Ithaca and stored in various disks. Currently, we are using

/home/arecibo2/galaxy

and data are stored by observing session, in a directory named after the date of the observing 
session, e.g., 

/home/arecibo2/galaxy/idlraw/05.02.14 

where 05.02.14 is the date of the first drift scan of the observing session.


2. Files used in Level I processing

CALIB1, CALIB2 and BPD are ran by diffferent members of the team. A "reducer" gets
assigned a data block, which may consist of all scans in one or more observing sessions.
It will be the responsibility of the reducer to run calibration procedures (CALIB1, CALIB2),
bandpass clibrate and baseline the data (run BPD) and inspect and flag the data for
rfi and other problems (run FLAGBB). Suppose the observing session data was stored in a 
directory /home/arecibo2/galaxy/idlraw/05.02.14. The reducer will deliver the following 
files, for each observing session contained in his/her data block:

- cal050214.list	text list of scans used as input to CALIB1 

- ncalib_050214.sav     an IDL .sav file containing the ncalib structure
			produced by CALIB2
Whenever the power is adjusted during a block (e.g. WAPP restart; changing to a different
drift), the calibration must be derived for only the period since the last adjustment.
If calibration had to be broken down into several segments, then the calibration should be
stored in separate NCALIB files, identified by "_N", when N = 1,2,3 etc, e.g.
ncalib_050214_1.sav, ncalib_050214_2.sav, etc., with an indication in a log_processing
text file of what set of scans each ncalib file was applied to.

- drift050214.list	a text list of the drift scans processed with BPD

- A set of processed IDL .sav files containing the IDL structures and arrays produced
by BPD for each of the drift scans, with the naming convention as automatically assigned
by BPD, e.g. as many files as there are drift scans in driftscan050214.list, with
names such as, e.g., d154256+114757.504523283.sav

- calsession_050214.sav	an IDL .sav file containing the calsession structure for the
  			observing session

- pos_050214_+114757s.sav	an IDL .sav file containing the pos structure for all the
  			processed drift scans of the observing session. This structure
			will have been produced by BPD and modified by FLAGBB. Note
			that the +114757 refers to the DecJ of Beam 0 (i.e. the drift)
			and the "s" before ".sav" refers to the fact that this is a
			"spring" dataset; alternatively, use "f".

- log_processing_050214	a text file with the reducer's comments on the processing of
			the data