SetMeUp

WARNING: This page is obsolete.

Please look at https://atlas-software.docs.cern.ch/analysis/analysis_tutorial/basicSetup/alrb/#diagnostics.

Users and Site Admins

(You can also do this on lxplus so that you have the same structure as at other sites)

Users and site admins can fetch the datasets and files required for the tutorials by doing

setupATLAS
diagnostics
setMeUpData <tutorial version> <local download dir>

Afterwords, define the environment variable $ALRB_TutorialData to point to the directory <local download dir>/tutorial/<tutorial version> and users running setMeUp next will use it automatically.

Users

Users who want to run the tutorial exercises at their own Tier3s, desktops, laptops or CernVM may be able to do so instead of on lxplus. There is a test they should first run to ensure that their setup is ready for the tutorial. This can be accessed by doing

setupATLAS
diagnostics
setMeUp <tutorial version>

where <tutorial version> is also the name of the configuration file maintained by the tutorial conveners and contains the requirements for the tutorial.

setMeUp will do the following (depending on the configuration):

• print requirements for tutorial which the user should check prior to continuing.

• os:
  • check for OS version and type
  • check cvmfs validity
  • check computer is ATLAS ready with required software
  • check domain name

• grid:
  • check if voms proxy is successful
  • check /atlas role exists
  • check /atlas/lcg1 role exists
  • check nickname exists

• env:
  • check disk space is enough
  • check password-less svn access (kerberos and if that fails, public key) works
  • check RUCIO_ACCOUNT environment variable is defined

• ami
  • check if user can access ami using proxy

• panda:
  • submit prun (checks grid submission and nickname)

and it prints a summary of the testing and state if the tutorial can be run in that user's environment.

In addition, a summary will be available for the conveners to view on a web page.

Conveners

There is a web page containing:

• config.txt: a file configured for the tutorial
• ds*.txt: output from each dataset collection's \dq2-ls
• any other tarball or file to be downloaded must have a matching md5sum file (same filename with .md5sum extension) containing the md5sums of all files (e.g. : find . -type f -exec md5sum {} \; > ../<myfile>.md5sum)

-- Asoka De Silva - 2014-08-22