Input file convention

File name

• in* for the code *. For example, infastran for fastran while innubeam for nubeam

File format

• fortran namelist

What is in in*

• Generally, in* is very similar to the code *'s input file, but not necessarily exactly same.

• For example:

1. infastran is exactly same as the input file of fastran

2. intoray contains

    &intoray
     idamp  = 8
     ....
    /
    &adjust
     width = 0.0
     ...
    /
    &eqdat
     powinc = 1.0e+13
     ...
    /
   

&eqdat ... / is same as the content of "toray.in", which is an input file for toray. idamp ... under &intoray ... / is used to generate "echin". &adjust ... / is used by the IPS toray component to control post-process, etc. The naming of each variable, for example, idamp is kept same as the name of variable that toray uses.

3. ingenray is same as the input file of genray except that a few variables have __IPS_CONTROL__ value:

    ZEFF1 = '__IPS_CONTROL__'
   

, meaning that ZEFF1 will be updated by the IPS genray component