...
However I would suggest to run it with the flag --log DEBUG, so that a logfile ($HOME/fred.log) is created, and you can try to figerout what happens if FRED crashes or does not want to run. Besides that logfile, a directory $HOME/.fred with other logfiles are created. But those ones did not help me when FRED was not working due to configuration errors...You can use the simple script myfred (from csh or tcsh) as an example of how to run the fred version you want (in debug mode) with the ruby package you want.
FRED will be acting as a client of Gleam which will be the engine processing the events.
The configuration of the execution of Gleam is performed via the FRED GLAST pannel.
Run FRED by executing the script fred (or myfred) in the noric machines. You will get a FRED display. In order to configure FRED to display the data you want to see you have to open the FRED GLAST pannel, which is the button with a satellite image in the upper part of FRED.
There are 5 fields that we have to fill. They are listed below:
- A personal script defining some environment variables related to teh software to use (CMTPATH, GLAST_EXT...)
- A "Gaudi" configuration script
- A "Gaudi" executable (is the Gleam executable)
- A job options ascii file defining, among other things, the input data and geometry to be used
- A working directory
Those 5 files are given to FRED by means of the GLAST front panel
(icon on the top right part of the FRED panel).
IMPORTANT REMARK
FRED requires to run in BASH shell. That implies the usage of
BASH shell scripts.