Hints on Using the ONETWO Code

Not all users of the ONETWO transport code may be aware of the tools that are available to assist them. What follows, in no particular order, are a few of the basics that are not widely known. The information here applies equally to all platforms on which ONETWO runs: CRAY (UNICOS), HP (HP-UX), DEC Alpha (Digital Unix), SGI (IRIX) and Sun (Solaris).

1. You must have the environment variable ONETWO set. (See article 1 above.)

2. You should have the directory $ONETWO/codes in your PATH, although it is not required if you are willing to tolerate some inconvenience. (See article 1 above.)

3. The files $ONETWO/codes/{inone.*,eqdsk.*} comprise more than 70 sample ONETWO input cases. You should never have to create an inone file from scratch.

4. The interactive command inputs12 fully describes all inputs to ONETWO. It does this by extracting the relevant comment lines directly from the source code of the latest version. You can page forward and back, search for text strings (even regular expressions), extract a printable file, and so on. For help, type inputs12 -h. The article displayed by the command docview onetwo_inputs was in fact generated by the inputs12 command. (However, this article is not kept absolutely up to date, whereas the output from input12 is always current.)

5. The run12 command makes it easy to run ONETWO - in foreground, background, batch and even under control of the debugger. It is especially useful if you want to make several concurrent runs. For help, type run12 -h.

6. You only need the xview, tekview and cgmplot commands to view and print the CGM files that are produced by ONETWO's graphical post-processors. For help, type xview -h, tekview -h and cgmplot -h respectively.