Software for gbtdata Directory Naming Convention

To assist in both the operation of the e2e NRAO archiver presently being implemented for GB and the backup requirements of GBT data I propose adding a feature to GO (and whatever future program might replace GO) a software enhancement to enforce our gbtdata directory naming conventions (in GO this is the project id).

The convention is described elsewhere, in particular at www.gb.nrao.edu/~cbignell/GBT_Data_Directory_Naming_CL.htm

I have a suggestion how this can be implemented.

Replace the project id field with three fields:

• Observing type - this could be a drop down combobox with only three choices: Astronomy, Tests and Junk. The choice will set the first letter of the gbtdata subdirectory to the first letter of the choice made.


• Name - This text entry field accepts a maximum of 11 characters and automatically capitalizes all characters entered. When this field is exited (such as an onlost focus event) several actions take place than can modify the user entered value. The final adjusted value obtained from this field makes up characters 2 to 12 (max) of the gbtdata directory name (first character comes from (a)). The actions triggered by the on lost focus event fall into two categories: one that depends on the choice in (a) and one final one that is independednt of (a).


• Dependent on (a)


• Astronomy The contents are checked and modified for a valid proposal code. For example it could easily change 2a6, gbt2a-6 or gbt2a6 to GBT02A_006 (all - would be replaced by _). There are various forms to check for and/or convert to (I could review these at some point if this is to be implemented). Instead of using an algorithm a check against a list of valid proposal codes could be made (slight disadvantage to this is maintaining this list). If a valid proposal code cannot be recognized GO should not be allowed to start the observing.


• Tests The contents in this case can be almost anything. I beleive it may be possible to do verification/selection against a valid list of possibilities. This needs alittle more investigation.


• Junk The only acceptable value for the contents of the name in this case is a valid NRAO username. This could be chaecked against a list.


• Independent of (a) Once the first part of the gbtdata directory has been determined from the first two fields and quick scan of the gbtdata could be carried out to determined if there are any subdirectories by that name to pick up any existing sequence numbers currently in use for that subdirectory. The next available sequence number is calculated from existing ones and the sequence number ((c) below) is set to that number plus one as a default. In the case of no previous squence number the default should be set to one. If the directory does not exist it should be created.


• Sequence number This can be a numeric number from 1 to 99. This number is used to calculate the last three letters of the data subdirectory. In particular the format is _nn where nn is the sequence number converted to characters and formatted with a preceding "0" for numbers less than 10.

Feb 26, 2003