The PROJECTS.cfg has only one keyword which is defined many times over for the entire list of projects. Think of this file as a list of lists which span the hierarchy of project, mission, experiment, instrument, and virtual instrument. This hierarchy is essentially one big tree with the root having no value, and each project is the first level of limbs. Each project has its associated missions and these are the second level of limbs. The experiments is the third level and so forth until the virtual instrument is reached.
Comments can be placed in the PROJECTS.cfg also. Use the "#" character to indicate a comment. Everything on the line after the "#" will be ignored.
Everything in the PROJECTS.cfg is a string and to indicate it as such, quote marks (") must be placed around each string. The only items which do not get quotes are the keywords and the values prefacing the keyword.
If the entire value for the line does not fit on a line, you may use the "\" character to continue to the next line.
The first value in the PROJECTS.cfg is the word Strings. After the Strings, place each of the projects you wish defined seperated by a space. Remember, each project name must be enclosed in quotes. Furthermore, if you define a new project, it must also be defined in the DB.cfg.
Examples:
Strings "TSS" "UARS" "AMPTE" "ARIA" "DE" "DMSP" "ISEE" \
"SPACERAD" "INTERBALL" \
"IMP" "GeoSolarInd" "CosmicRayMon" "ASTRID" \
"CLUSTERII" "MARS" "PROGNOZ" "VIKING" "FREJA"
Now, for each of the items defined in Strings, you must define the next set of Strings. This next set defines the missions under each project. The set after that defines the experiments under each mission under the project and so on.
The way you define them is to put the project name, the mission name, etc. in one string each seperated by a "." with the keyword Strings after it. This "token" is the piece of the hierarchy that you are defining. After the token, simply put the names of the next level enclosed in quotes and seperated by spaces.
Example:
#----------------------------------------------------- ##################### INTERBALL ###################### #----------------------------------------------------- INTERBALL.Strings "TAIL" INTERBALL.TAIL.Strings "PROMICS-3" "SCA-1" INTERBALL.TAIL.PROMICS-3.Strings "HK" "MEPS" "TRICS" INTERBALL.TAIL.PROMICS-3.HK.Strings "MONITOR" "STATUS" INTERBALL.TAIL.PROMICS-3.MEPS.Strings "12_19" "1314_17_18" "FULL_MOM" "PART_MOM" INTERBALL.TAIL.PROMICS-3.TRICS.Strings "1__10P" "1__10S" "2__9P" "2__9S" "3_8P" "FULL_MOM" INTERBALL.TAIL.SCA-1.Strings "EU-1" INTERBALL.TAIL.SCA-1.EU-1.Strings "IBNP1" "IBNP2" "IBM12" "IBU1E" "IBU1A"
In this example, the full tree of INTERBALL is defined.