Babar/CM2 A-to-Z at Manchester

James Werner

Load local database with experiment data and Monte Carlo simulation

Before start following this stage, prepare one data distribution over your file system that gives better performance and easy codification. When I download the data, I didn't know about the KanAccess.cfg file (to map real file to skim) and I performed first everything from RAL, and the remains from SLAC in one disk (this disk contains lots of different datasets)..

I believe that I should map the files and experiments grouped by experiment (MC Tau11, MC Tau1N, etc all together), downloading each one from RAL and following the download from SLAC. Now the download was done, and I will keep as it is. If you are doing for the first time, read this section, the reference and after this make a smart KanAccess.cfg before starting downloading files.

The solution came with a new file server (cap.hep.man.ac.uk). The RAID5 disk server provide us with 1.8 TB, and allow us to copy all files from sun1 to the raid disk and fix the KanAccess.cfg file (See the end of the page).

 ssh -l jamwer bfb.tier2
 cd BbSoft
 srtpath
enter release number (CR=14.4.2a):

Select/enter BFARCH (CR=1):
1) Linux24RH72_i386_gcc2953    [prod][test]
2) Linux24RH73_i386_gcc2953    [active]
 BbkDatasetTcl --dbsite=man | grep Tau
SP-1005-Tau11-R14
... lots of MC
SP-uds-Tau33-Run1-R14
SP-uds-Tau33-Run4-R14
Tau11-Run1-OffPeak-R14
Tau11-Run1-OnPeak-R14
Tau11-Run2-OffPeak-R14
Tau11-Run2-OnPeak-R14
Tau11-Run3-OffPeak-R14
Tau11-Run3-OnPeak-R14
Tau11-Run4-OffPeak-R14
Tau11-Run4-OnPeak-R14
Tau1N-Run1-OffPeak-R14
Tau1N-Run1-OnPeak-R14
Tau1N-Run2-OffPeak-R14
Tau1N-Run2-OnPeak-R14
Tau1N-Run3-OffPeak-R14
Tau1N-Run3-OnPeak-R14
Tau1N-Run4-OffPeak-R14
Tau1N-Run4-OnPeak-R14
Tau33-Run1-OffPeak-R14
Tau33-Run1-OnPeak-R14
Tau33-Run2-OffPeak-R14
Tau33-Run2-OnPeak-R14
Tau33-Run3-OffPeak-R14
Tau33-Run3-OnPeak-R14
Tau33-Run4-OffPeak-R14
Tau33-Run4-OnPeak-R14
ignore-1749-Tau11-Run1-OnPeak-R14
ignore-1751-Tau1N-Run1-OnPeak-R14
... lots of ignore files
ignore-5884-Tau1N-Run4-OnPeak-R14
ignore-5885-Tau33-Run4-OnPeak-R14

Each Tau topology is defined deppending the number of particles scaterred in each direction. OnPeak correspond to 10.58 GeV and OffPeak to 10.54GeV.

Verify each topology

> BbkFiles --dbsite=man --dataset=Tau11-Run3-OffPeak-R14 --remote='*'
> BbkFiles --dbsite=man --dataset=Tau11-Run3-OffPeak-R14-BlueSquare --remote='*'
> BbkFiles --dbsite=man --dataset=Tau11-Run3-OffPeak-R14-GreenCircle --remote='*'
> BbkFiles --dbsite=man --dataset=Tau11-Run3-OnPeak-R14 --remote='*'
> BbkFiles --dbsite=man --dataset=Tau11-Run3-OnPeak-R14-BlueSquare --remote='*'
> BbkFiles --dbsite=man --dataset=Tau11-Run3-OnPeak-R14-GreenCircle --remote='*'
> BbkFiles --dbsite=man --dataset=Tau1N-Run3-OffPeak-R14 --remote='*'
> BbkFiles --dbsite=man --dataset=Tau1N-Run3-OffPeak-R14-BlueSquare --remote='*'
> BbkFiles --dbsite=man --dataset=Tau1N-Run3-OffPeak-R14-GreenCircle --remote='*'
> BbkFiles --dbsite=man --dataset=Tau1N-Run3-OnPeak-R14 --remote='*'
> BbkFiles --dbsite=man --dataset=Tau1N-Run3-OnPeak-R14-BlueSquare --remote='*'
> BbkFiles --dbsite=man --dataset=Tau1N-Run3-OnPeak-R14-GreenCircle --remote='*'
> BbkFiles --dbsite=man --dataset=Tau33-Run3-OffPeak-R14 --remote='*'
> BbkFiles --dbsite=man --dataset=Tau33-Run3-OffPeak-R14-BlueSquare --remote='*'
> BbkFiles --dbsite=man --dataset=Tau33-Run3-OffPeak-R14-GreenCircle --remote='*'
> BbkFiles --dbsite=man --dataset=Tau33-Run3-OnPeak-R14 --remote='*'
> BbkFiles --dbsite=man --dataset=Tau33-Run3-OnPeak-R14-BlueSquare --remote='*'
> BbkFiles --dbsite=man --dataset=Tau33-Run3-OnPeak-R14-GreenCircle --remote='*'

Verify sets of datasets

> BbkFiles --dbsite=man --dataset=Tau11-Run3-* --remote='*'
                                     New file
                                    (status=2)
Skim Release Stream Components Files    Events GBytes
============ ====== ========== ===== ========= ======
14.3.2h      Tau11  HBCA         103 346661982  149.6
============ ====== ========== ===== ========= ======
Totals                           103 346661982  149.6
database: 103 (160680928250 bytes, 149.6 GB)
> BbkFiles --dbsite=man --dataset=Tau1N-Run3-* --remote='*'
                                     New file
                                    (status=2)
Skim Release Stream Components Files   Events GBytes
============ ====== ========== ===== ======== ======
14.3.2h      Tau1N  HBCA          51 38444016   60.0
============ ====== ========== ===== ======== ======
Totals                            51 38444016   60.0
database: 51 (64380858851 bytes, 60.0 GB)
> BbkFiles --dbsite=man --dataset=Tau33-Run3-* --remote='*'
                                     New file
                                    (status=2)
Skim Release Stream Components Files   Events GBytes
============ ====== ========== ===== ======== ======
14.3.2h      Tau33  HBCA          56 42577579   66.6
============ ====== ========== ===== ======== ======
Totals                            56 42577579   66.6
database: 56 (71523569016 bytes, 66.6 GB)

Marking the files to be imported and importing data

Important:
> Tim will dig out for James the special parameters that are
> needed to speed up data import (bbcp etc...).

You can use the commands like in the documentation

http://hepunx.rl.ac.uk/BFROOT/www/Computing/Offline/DataDist/bbk-localdb.html

but you'll probably have more luck with --ftp=bbcp (instead of bbftp,
which has more firewall problems), eg.

  BbkImport --dbsite=local --dbuser=bbrora --ftp=bbcp \
              bbrdist@bbr-xfer01.slac.stanford.edu

There are many parameters (see the bbcp section of BbkImport --help),
but you should get a good enough improvement with the defaults.

I suggest you stick to importing from SLAC. We haven't implemented any
way to export data out of xrootd at RAL.

If you have any problems, please post your question to the Data
Distribution HyperNews. There are many other experts.

The time expended transfering from SLAC to Manchester per 1 GB is 1:10. Password is required 2 times for each file. Transfer Tau will take 240 hours. After lots of problems because LocateForImport doesn't exist at RAL. It probably wouldn't be very useful to do that now because RAL are still setting up new systems (load balancer, cache filesystem, and automatic staging), so anything they made now would have to be rewritten later. However, Tim gave me the physical address were the tau data is. I used the command

BbkImport --dbsite=man --dbuser=bfactory csfmove01.rl.ac.uk:/stage/bdata-data48 /nfs/babar03/TauData

Specifying the disk (/stage/bdata-data48) on the command line bypasses the use of LocateForImport. You can specify the target disk as the second parameter (as I show here) or with the --diskroot option as you do. It's faster to use bbftp or bbcp, even for importing from RAL. However, this packages are not available at Manchester.

====> Disco babar01
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=Tau33-Run3-OffPeak-R14
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=Tau33-Run3-OnPeak-R14	
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=SP-1005-Tau11-R14	
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=SP-1005-Tau1N-R14	
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=SP-1005-Tau33-R14	
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=SP-1235-Tau11-R14	
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=SP-1235-Tau11-Run3-R14	
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=SP-1235-Tau33-Run3-R14	
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=SP-1237-Tau1N-Run3-R14	

BbkImport --dbsite=man --dbuser=bfactory csfmove01.rl.ac.uk:/stage/bdata-data48 /nfs/babar01/TauData
=====> Disco babar03
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=SP-1237-Tau33-R14	
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=Tau1N-Run3-OnPeak-R14	
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=SP-1237-Tau1N-R14	
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=SP-1237-Tau33-Run3-R14	
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=SP-998-Tau11-R14	

BbkImport --dbsite=man --dbuser=bfactory csfmove01.rl.ac.uk:/stage/bdata-data48 /nfs/babar03/TauData
=====>  Disco babar04
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=SP-1235-Tau1N-R14	
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=SP-1235-Tau1N-Run3-R14	
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=SP-1237-Tau11-R14	
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=SP-1237-Tau11-Run3-R14	
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=SP-998-Tau1N-R14	
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=SP-998-Tau33-R14	
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=Tau1N-Run3-OffPeak-R14	
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=SP-1235-Tau33-R14	     

BbkImport --dbsite=man --dbuser=bfactory csfmove01.rl.ac.uk:/stage/bdata-data48 /nfs/babar04/TauData
=====>  Disco babar05
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=Tau11-Run3-OffPeak-R14	
BbkFiles --dbsite=man --dbuser=bfactory --remote=2 --setremote=1C --dataset=Tau11-Run3-OnPeak-R14	

BbkImport --dbsite=man --dbuser=bfactory csfmove01.rl.ac.uk:/stage/bdata-data48 /nfs/babar05/TauData
Files missing from RAL were imported from SLAC
BbkImport --dbsite=man --dbuser=bfactory --remote-user=jamwer bbr-xfer01.slac.stanford.edu /nfs/babar04/TauData

Seting the pointers to the datasets

References:

http://www.slac.stanford.edu/BFROOT/dist/releases/newest/HOWTO/HOWTO-Setup-a-CM2-Kanga-Eventstore

The link between the physical data and the BookKeeper software is in your KanAccess.cfg file which tells the programs where to
find CM2 data.
vi /afs/hep.man.ac.uk/g/bfactory/kanga/config/KanAccess.cfg
# Comment out the write of SP just incase that causes problems
read /store/SP/BkgTriggers/* file /nfs/babar01/snapshots
read /store/SP/* xrootd kanolb-a:1094/
# Tau Data
read /store/PRskims/R12/14.3.2h/Tau33/* file /nfs/babar01/TauData
read /store/PRskims/R12/14.3.2h/Tau1N/* file /nfs/babar03/TauData
read /store/PRskims/R12/14.3.2h/Tau1N/* file /nfs/babar04/TauData
read /store/PRskims/R12/14.3.2h/Tau11/* file /nfs/babar05/TauData
read /store/PRskims/R12/14.3.2h/Tau33/* file /nfs/babar06/TauData
# MC used in the tutorial example
read /store/SPskims/R12/14.4.2b/Tau11/* file /nfs/babar04/TauData
# MC data spread around several disks
# /nfs/babar01
read /store/SPskims/R12/14.4.0d/Tau11/* file /nfs/babar01/TauData
read /store/SPskims/R12/14.4.2b/Tau11/* file /nfs/babar01/TauData
read /store/SPskims/R12/14.4.2b/Tau1N/* file /nfs/babar01/TauData
read /store/SPskims/R12/14.4.2b/Tau33/* file /nfs/babar01/TauData
read /store/SPskims/R14/14.4.0d/Tau11/* file /nfs/babar01/TauData
read /store/SPskims/R14/14.4.0d/Tau1N/* file /nfs/babar01/TauData
read /store/SPskims/R14/14.4.0d/Tau33/* file /nfs/babar01/TauData
read /store/SPskims/R14/14.4.0e/Tau11/* file /nfs/babar01/TauData
read /store/SPskims/R14/14.4.2b/Tau11/* file /nfs/babar01/TauData
read /store/SPskims/R14/14.4.2b/Tau1N/* file /nfs/babar01/TauData
read /store/SPskims/R14/14.4.2b/Tau33/* file /nfs/babar01/TauData
# /nfs/babar03
read /store/SPskims/R12/14.4.0d/Tau11/* file /nfs/babar03/TauData
read /store/SPskims/R12/14.4.0d/Tau1N/* file /nfs/babar03/TauData
read /store/SPskims/R12/14.4.0d/Tau33/* file /nfs/babar03/TauData
read /store/SPskims/R12/14.4.0e/Tau11/* file /nfs/babar03/TauData
read /store/SPskims/R12/14.4.0e/Tau1N/* file /nfs/babar03/TauData
read /store/SPskims/R12/14.4.0e/Tau33/* file /nfs/babar03/TauData
read /store/SPskims/R12/14.4.2b/Tau11/* file /nfs/babar03/TauData
read /store/SPskims/R12/14.4.2b/Tau1N/* file /nfs/babar03/TauData
read /store/SPskims/R12/14.4.2b/Tau33/* file /nfs/babar03/TauData
read /store/SPskims/R14/14.4.0d/Tau11/* file /nfs/babar03/TauData
read /store/SPskims/R14/14.4.0d/Tau1N/* file /nfs/babar03/TauData
read /store/SPskims/R14/14.4.0d/Tau33/* file /nfs/babar03/TauData
read /store/SPskims/R14/14.4.0e/Tau11/* file /nfs/babar03/TauData
read /store/SPskims/R14/14.4.0e/Tau1N/* file /nfs/babar03/TauData
read /store/SPskims/R14/14.4.0e/Tau33/* file /nfs/babar03/TauData
read /store/SPskims/R14/14.4.2b/Tau11/* file /nfs/babar03/TauData
read /store/SPskims/R14/14.4.2b/Tau1N/* file /nfs/babar03/TauData
read /store/SPskims/R14/14.4.2b/Tau33/* file /nfs/babar03/TauData
# /nfs/babar04
read /store/SPskims/R12/14.4.0d/Tau11/* file /nfs/babar04/TauData
read /store/SPskims/R12/14.4.0d/Tau1N/* file /nfs/babar04/TauData
read /store/SPskims/R12/14.4.0d/Tau33/* file /nfs/babar04/TauData
read /store/SPskims/R12/14.4.0e/Tau11/* file /nfs/babar04/TauData
read /store/SPskims/R12/14.4.0e/Tau1N/* file /nfs/babar04/TauData
read /store/SPskims/R12/14.4.0e/Tau33/* file /nfs/babar04/TauData
read /store/SPskims/R12/14.4.2b/Tau11/* file /nfs/babar04/TauData
read /store/SPskims/R12/14.4.2b/Tau1N/* file /nfs/babar04/TauData
read /store/SPskims/R12/14.4.2b/Tau33/* file /nfs/babar04/TauData
read /store/SPskims/R14/14.4.0d/Tau1N/* file /nfs/babar04/TauData
read /store/SPskims/R14/14.4.0d/Tau33/* file /nfs/babar04/TauData
read /store/SPskims/R14/14.4.0e/Tau1N/* file /nfs/babar04/TauData
read /store/SPskims/R14/14.4.0e/Tau33/* file /nfs/babar04/TauData
read /store/SPskims/R14/14.4.2b/Tau11/* file /nfs/babar04/TauData
read /store/SPskims/R14/14.4.2b/Tau1N/* file /nfs/babar04/TauData
read /store/SPskims/R14/14.4.2b/Tau33/* file /nfs/babar04/TauData
# /nfs/babar05
read /store/SPskims/R12/14.4.0d/Tau11/* file /nfs/babar05/TauData
read /store/SPskims/R12/14.4.0d/Tau1N/* file /nfs/babar05/TauData
read /store/SPskims/R12/14.4.0d/Tau33/* file /nfs/babar05/TauData
read /store/SPskims/R12/14.4.0e/Tau11/* file /nfs/babar05/TauData
read /store/SPskims/R12/14.4.0e/Tau1N/* file /nfs/babar05/TauData
read /store/SPskims/R12/14.4.0e/Tau33/* file /nfs/babar05/TauData
read /store/SPskims/R12/14.4.2b/Tau11/* file /nfs/babar05/TauData
read /store/SPskims/R12/14.4.2b/Tau1N/* file /nfs/babar05/TauData
read /store/SPskims/R12/14.4.2b/Tau33/* file /nfs/babar05/TauData
read /store/SPskims/R14/14.4.2b/Tau11/* file /nfs/babar05/TauData
read /store/SPskims/R14/14.4.2b/Tau1N/* file /nfs/babar05/TauData
read /store/SPskims/R14/14.4.2b/Tau33/* file /nfs/babar05/TauData

Fixing the Book Keeper errors.

The engine do not search for multi volumes datasets. The solution was 
copy the files to the new server:
cp -r /exp_software/babar01/TauData/* .
cp -r /exp_software/babar02/TauData/* .
cp -r /exp_software/babar03/TauData/* .
cp -r /exp_software/babar04/TauData/* .
cp -r /exp_software/babar05/TauData/* .
cp -r /exp_software/babar06/TauData/* .
and fix the KanAccess.cfg file:
# Comment out the write of SP just incase that causes problems
read /store/SP/BkgTriggers/* file /nfs/babar01/snapshots
read /store/SP/* xrootd kanolb-a:1094/
# Tau Data
read /store/PRskims/* file /nfs/work
read /store/SPskims/* file /nfs/work
read /work/* file /nfs
read * error
write /work/* file /nfs/work/newstore
write * error

Book keeper does not deal with multi-volumes!

Top

Last modified:
Copyright 2004 Manchester University
Feedback to: jamwer@hep.man.ac.uk