Structure of the ONETWO Directory Tree

The diagram below illustrates the structure of the directory tree for the ONETWO transport code. Note that the tree always has the same structure on all hosts on which ONETWO is available; only the starting point of the tree varies, and this is determined by the value of the ONETWO environment variable.

$ONETWO
       /codes              <-- public executables
           /backup
           /{various}
       /curray
       /data               <-- required data files
           /adas           <-- ADAS data files
       /eqplot
           /baseline
           /debug
           /latest
       /fastcd
           /baseline
           /debug
           /latest
       /fixbdry
           /baseline
           /debug
           /latest
       /gafit
           /baseline
           /debug
           /latest
       /nubplt
           /baseline
           /debug
           /latest
       /mepc
           /baseline
           /debug
           /latest
       /onetwo             <-- main transport code
           /baseline       <-- source code for developers to start with
           /debug          <-- unoptimized, debugger-compatible version
           /latest         <-- temporary location for latest version
       /ploteq
           /baseline
           /debug
           /latest
       /preplt
           /baseline
           /debug
           /latest
       /psiplot
           /baseline
           /debug
           /latest
       /toray
           /baseline
           /debug
           /latest
       /trplot
           /baseline
           /debug
           /latest
       /verdi
           /baseline
           /debug
           /latest
       /xplot
           /baseline
           /debug
           /latest