Child pages
  • PROOF on Demand
Skip to end of metadata
Go to start of metadata
Table of Contents

Setup ATLAS Local Root Base (ALRB):

export ATLAS_LOCAL_ROOT_BASE=/cvmfs/atlas.cern.ch/repo/ATLASLocalRootBase
alias setupATLAS='source ${ATLAS_LOCAL_ROOT_BASE}/user/atlasLocalSetup.sh'
setupATLAS

Setup PoD

Simply source PROOF on Demand (PoD) from CVMFS and start the server:

lsetup pod
generatePoDSetups
pod-server start 

Submit PROOF workers via HTCondor

You can now set up PROOF workers by using the PoD submit script with the HTCondor batch plugin:

pod-submit -r condor -n [number of jobs]


You should see PROOF workers running via HTCondor:

$ condor_q
-- Submitter: login.atlas.ci-connect.net : <192.170.227.199:38061> : login.atlas.ci-connect.net
 ID      OWNER            SUBMITTED     RUN_TIME ST PRI SIZE CMD
1381.0   lincolnb        3/3  11:20   0+00:17:07 R  0   1220.7 PoDWorker.sh
1381.1   lincolnb        3/3  11:20   0+00:17:07 R  0   1220.7 PoDWorker.sh
1381.2   lincolnb        3/3  11:20   0+00:17:07 R  0   1220.7 PoDWorker.sh
1381.3   lincolnb        3/3  11:20   0+00:17:07 R  0   1220.7 PoDWorker.sh
1381.4   lincolnb        3/3  11:20   0+00:17:07 R  0   1220.7 PoDWorker.sh
1381.5   lincolnb        3/3  11:20   0+00:17:07 R  0   1220.7 PoDWorker.sh
...

Note

You can also see PROOF workers running with "pod-info --list"

A simple functionality test

From ROOT, you can run the following benchmark:

 root> TProofBench pb("pod://")
 root> pb.RunCPU()

Shutting down PoD

Please remember to shut down your PROOF workers once you're done! To do so:

pod-server stop

Known caveats

This is new functionality and there may be bugs. One known issue is that there is currently no way to steer jobs to particular resources, so PROOF workers might end up at different sites and communicate over the WAN.

References

  • No labels
Write a comment…