| 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: AGBT02A_011, ABB123, AGM057B, ABW083, etc. |
| Type T | Test data. The description will depend on the type of testing: (A) Tests/project checkout conducted for a specific proposal. Use either a full or shortened version of the formal proposal code name (TREG_050721, etc.) The initials of the tester may also be included. (B) Specific tests for pointing, calibrations, commissioning. Use a brief description noting the type of test. Note: The observer on duty will normally determine this name. (C) Tests conducted for a specific individual. Use the individuals NRAO user name (RNORROD, TMINTER, etc.) |
| Type J | Junk data. Use JMAINT or the individuals NRAO user name (RNORROD, TMINTER, etc.) |