= Running a GiBUU simulation =

After the GiBUU code has been [wiki:compiling compiled] successfully, the executable "GiBUU.x" can be found in the subdirectory "objects/", and a symbolic link to it is placed in the "testRun/" directory. The executable can either be run directly from one of these places, or it can be put into a separate directory of your choice together with a suitable [wiki:jobCards jobcard] (which we recommend for the sake of a cleaner environment).

In principle the executable can also be transferred to a different machine, but it may not necessarily run there (depending on CPU architecture and available libraries). In such a case it can be useful to link the executable statically, as described [wiki:compiling#Staticvs.DynamicLinking here].


== Program invocation ==

To run GiBUU, just go to the directory where the executable is located and type

{{{
./GiBUU.x < my_setup.job
}}}

The file "my_setup.job" should be a valid GiBUU [wiki:jobCards jobcard], containing all the options and parameters for the desired simulation. Several example jobcards are provided in the directory "testRun/jobCards/" and on this [wiki:jobCards wiki page]. If the executable is invoked without specifying a jobcard, i.e. like this

{{{
./GiBUU.x
}}}

then it will just print some version information and exit. When reporting any problems with GiBUU, please provide the information given in this header (which will help us to reproduce the problem).

After starting a simulation with a proper jobcard, it will print a lot of information to the screen and produce several output files. It can be useful to print the output to a log file (for later reference and inspection), which is achieved via

{{{
./GiBUU.x < my_setup.job > log.txt
}}}

This will produce a file "log.txt", which contains all the screen output from GiBUU after the simulation is finished (and be be inspected already while the simulation is running).


== Input files ==


== Output files ==