setenv HALLA_DIR /work/halla/software
setenv HALLA_BIN $HALLA_DIR/bin
setenv LOC_HALLA_BIN $HALLA_BIN/$OSNAME
setenv PATH $LOC_HALLA_BIN/:$PATH
You can type source .cshrc to set the above variables without a logout and login. In your home directory execute the command cp -R /work/halla/e93027/cosmic espace. This will create an analysis directory. Create the directory /work/halla/e93027/name/hbook where name is whatever you want. Then type the command ln -s /work/halla/e93027/name/hbook espace. This creates a symbolic link between your espace/hbook directory and where the espace kumac will put the hbook files. Just makes it easier to find things in paw++. The work disk is not backed up so it is recommended to work on the home disk which is backed up and store hbook files on the work disk. If you want to save the hbook files then copy them to /mss/home/username .
setup mss
request_file -f /mss/halla/ exp/raw/ exp_####.da t
exp is the experiment number, for example e89003, e89033, e93050, e93027 etc. The file will be taken from the MSS and put in the directory /cache/halla/exp/raw . An email will be sent to you when this process is complete. One needs to put the data on the cache disk to replay the data interactively either on the jsub machines (not recommended, very slow) or on the ifarm machines. When replaying data in batch mode on the farm machines one can get the data file directly from the mss and not have to put it on the cache disk. There are also the commands jget and jput which can be used to move data to and from the work or home disk to the mss and also get files from the cache disk. ( More information of batch commands)
Replaying data on the batch farms machines (farms1, farms2 etc) can be done using the jsub command. (More details on batch farm at JLAB). The jsub command needs a script file and also a command file to run espace on the batch computer. A command file has been written called replay_fpp which creates the jsub script file, the espace command file and executes the jsub command. To check the status of the batch job use the command jobstat .