GBT OPERATIONS PROCEDURES

 Number: OP-10
Title: GBT Data Directory Naming Conventions Last Revision: 25 Oct 02

General

All astronomical data collected using standard backend instruments (Spectrometer, Spectral Processor, DCR, or BCPM) is stored in specific subdirectories of the /home/gbtdata directory. No files should be placed directly in the /home/gbtdata directory. Subdirectory naming is accomplished by entering the applicable name in the GO project ID box located on either the GO Main Screen panel or the Scan Coordinator Cleo application. To ensure consistency and standardization in directory naming, a specific naming convention has been established. Guidelines concerning this naming convention are outline below. 

Info

Rules applicable to the naming of all subdirectories:

Directory Naming Convention

Directory names will consist of three parts:  (type) (description) (version) 

TYPE
The TYPE is entered as a single character and will depend upon the type of data collected.
A Used for Astronomy data.
T Used for test data to include commissioning, calibrations, or other tests requiring the data to be archived. 
J Used for very temporary data not requiring archival (aka "junk" data). 

 

DESCRIPTION

The DESCRIPTION will depend on the type of data as noted above.
Type A Astronomy data. The description is the full formal proposal code name. No hyphens ("-") may be used however, because of Aips++ limitations. Therefore, all GBT proposal codes should have their hyphens ("-") replaced by an underscore ("_"). Examples of acceptable descriptions:  GBT02A_011, BB123, W404, etc.
Type T Test data. The description will depend on the type of testing:
  • Tests conducted for a specific proposal. Use either a full or shortened version of the formal proposal code name (GBT02A_011, BB123, etc.) The initials of the tester may also be included.
  • Specific tests for pointing or calibrations. Use a brief description noting the type of test. Note: Ron Maddalena will normally assign this name.
  • Tests conducted for a specific individual. Use the individuals NRAO user name (RNORROD, TMINTER, etc.) 
Type J Junk data. Use the individuals NRAO user name (RNORROD, TMINTER, etc.) 

 

VERSION

The VERSION is a sequence number of the form _nn. It is used to indicate the chronological order for collecting data any time the complete set of data cannot be stored within the same subdirectory. Bottom line: If you need to store data under more than one directory, you need to include a version number. The nn will be an incrementing number starting with 01.

Directory Name Examples

Here are some examples of directory names using the above naming convention:

AGBT02C_011  Routine astronomy data associated with a formal proposal. All data is in one subdirectory.

AGBT02A_057_02  Routine astronomy data associated with a formal proposal. Note that a version number has been used and shows this as being the 2nd directory.

TRNORROD_07  Test data for Roger Norrod spanning over several directories. 

TPNTHIGHGREG_03  More test data (pointing) using a Gregorian receiver at X-band or higher and spanning more than one directory.

JRPRESTAG  Temporary data file directory for Richard Prestage. 

Prepared by: Dave Rose

Last modified: 25Oct02