User Tools

Site Tools


asc:tutorials:2014october

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
asc:tutorials:2014october [2014/10/29 15:31]
asc [Lesson 4: Filling histograms]
asc:tutorials:2014october [2014/10/29 21:17] (current)
asc [xAOD tutorial at ANL (October 28-29, 2014)]
Line 4: Line 4:
 However, the lessons given below are simplified for a faster start. Also, the last 2 lessons are designed for the ANL cluster that uses condor for job submissions. However, the lessons given below are simplified for a faster start. Also, the last 2 lessons are designed for the ANL cluster that uses condor for job submissions.
 In addition, we we will test US ATLAS connect as explained at the bottom of this page. In addition, we we will test US ATLAS connect as explained at the bottom of this page.
 +
 +Agenda of this tutorial is [[https://indico.cern.ch/event/330836/]].
  
  
Line 272: Line 274:
  
 <code bash> <code bash>
-source setup.sh 
 mkdir lesson_3; cd lesson_3 mkdir lesson_3; cd lesson_3
 +source setup.sh    # setup ATLAS enviroment
 rcSetup -u; rcSetup Base,2.0.12 rcSetup -u; rcSetup Base,2.0.12
 rc find_packages  # find needed packages rc find_packages  # find needed packages
Line 326: Line 328:
  
  
 +<note tip>If the program fails saying that some shared library has a wrong format, clean ROOTCORE as "rc clean", and then compile everything again with "rc find_packages; rc compile"</note> 
 + 
 ====== Lesson 4: Filling histograms ====== ====== Lesson 4: Filling histograms ======
  
Line 453: Line 456:
  
  
-Now run "./A_RUN" to launch 2 jobs using 2 cores. Each job will read a portion of the original "inputdata.txt"  +Now let us  launch 2 jobs using 2 cores. Each job will read a portion of the original "inputdata.txt". Do this: 
 + 
 +<code bash> 
 +./A_RUN 
 +</code>  
  
 You can monitor jobs with this command (launched in a separate terminal): You can monitor jobs with this command (launched in a separate terminal):
Line 467: Line 474:
  
  
-If it does not work: Debug it as:+If it does not work: debug it as:
 <code> <code>
 testRun 00 testRun 00
 </code> </code>
 +The command runs one job using the input list inputs/list00.  It  shows where the problem is.
 +(Typically, this is due to wrong location of the goodrunlist)
 +
 +
 +If you run this program second time, clean the output directory:
 +
 +<code>
 +rm -rf outputs/*
 +</code>
 +(ROOTCORE does not like existing output directories)
  
-This will process inputs/list00 (first part of the input list) and shows where the problem is. 
-(Typically, this is due to wrong location of the goodrunlist). 
  
 **Attention:** **Attention:**
Line 530: Line 545:
 </code> </code>
  
-When the jobs are done, the output files will be inside "Jobs" directory. Merge the ROOT outputs into one file as:+When the jobs are done, the output files will be inside the "Job" directory. Merge the ROOT outputs into one file as:
  
 <code bash> <code bash>
Line 558: Line 573:
 See the instruction on how  See the instruction on how 
 {{:asc:tutorials:atlas_connect_handout_-_xaod_2014.pdf| to use ATLAS connect for this tutorial}} {{:asc:tutorials:atlas_connect_handout_-_xaod_2014.pdf| to use ATLAS connect for this tutorial}}
 +
 +
 +
 +======Using Eclipse to develop ATLAS code======
 +
 +[[asc:tutorials:eclipse| here is the link to this tutorial]]
  
 //[[[email protected]|Sergei Chekanov (ANL)]] 2014/10/09 13:50// //[[[email protected]|Sergei Chekanov (ANL)]] 2014/10/09 13:50//
asc/tutorials/2014october.1414596684.txt.gz · Last modified: 2014/10/29 15:31 by asc