You can run any MC model without the GUI. You need GUI only to create ``name.mc'' file and to be able to communicate with the MC. But this can be done without the graphical interface as well.
Before doing this, it is advisable first to run JRunMC and create a project file. Go to ``Options'' and select ``Do not update'' and ``Do not show plots''. Then you can save this project (the default name is ``analmc.mc'').
Next step is to run this MC model. Look at ``bin''. This directory has binary files for each MC model. These files read the input file ``.runmc.in'' located in your current directory. This is just a link to your input project file, say ``project.mc''. One can edit this file, to set additional settings you want. Then, execute the MC binary file in shell. For example, to run ARIADNE, just type: ``runmc.ariadne > runmc.log''
It is likely that you will get the message in the log file:
PROCESS PID=2331 renice 10 2331
2331: old priority 0, new priority 10 output file: analmc
$RUNMC/pipes/pipe_<date>.stop has 1
where ``date'' is a string containing the time when your job was started. This means that the communication file ``pipe_<date>.stop'' forbids this run since it has ``1''. To start the run, you should replace ``1'' in ``pipe_<date>.stop'' by ``0''. If you set ``0'' in this file, you can run this MC. If you will want to stop the MC run, again set ``1'' to ``pipes/pipe_date.stop''. After 3-5 seconds, the run should be terminated and all histograms will be saved. Since all pipe files are not identical, you can run as many jobs as you like at the same time.
If you get the message that ``pipe_date.stop'' is not find, you should create this file in the ``pipes'' directory and make sure that the name of this file was set correctly in the ``project.mc'' file (it should not contain any extension like ``.stop''!).
The easiest way to learn this - use first RunMC GUI and analyse changes in the project file ``project.mc'' file.
In addition to the ``pipe_<date>.stop'' file, each run has another file called ``pipe_<date>.events'', which contains the number of generated events.
The RUNMC will clean the ``pipes'' directory from the old files. At present, it will clean pipe files which more than 20 days old.