Software/Geant4/UCL HEP Batch Farm: Difference between revisions
No edit summary |
No edit summary |
||
| Line 15: | Line 15: | ||
=== Sourcing the pbt production environment === | === Sourcing the pbt production environment === | ||
The submitted bash script needs to load the pbt production environment before you can direct into your build directory and run the compiled simulation. This can be done in the following way: | The submitted bash script needs to load the pbt production environment (SL6) before you can direct into your build directory and run the compiled simulation. This can be done in the following way: | ||
<pre> | <pre> | ||
Revision as of 13:41, 20 July 2017
This page describes how to run a Geant4 simulation on the HEP Batch Farm.
Keep in mind that the current maximum CPU time for jobs on the batch farm is 120 hours. It is therefore important to split the simulation into jobs that do not exceed this time limit.
Send jobs to the batch farm
Jobs are submitted to the batch farm by using the command qsub. Type man qsub to see the available options. The submission of one such script corresponds to one job.
qsub name-of-bash-script.sh
Sourcing the pbt production environment
The submitted bash script needs to load the pbt production environment (SL6) before you can direct into your build directory and run the compiled simulation. This can be done in the following way:
scl enable devtoolset-3 bash <<EOF source /unix/pbt/software/scripts/prod-sl6/pbt-prod-sl6.bashrc cd /your/simulation/build/directory ./name-of-executable-simulation EOF
scl enable devtoolset-3 bash provides the new gcc compiler and the use of the here document <<EOF ... EOF makes sure the following block of code is executed in the new environment.