>ln -s other/directory/name yourfilename E.g., >ln -s /afs/cern.ch/user/w/wmurray/public/tb95/paw/lh2035.1.dst lh2035dst
In order to get the ntuple structure, you have to get in the paw and set the directory to the ntuple... Here is how.
>paw >hist/file 1 filename <- filename is the ntuple file >cdir //lun1/aaaa <- aaaa is the ntuple name >nt/uwfunc 10 funcname "" <- don't miss "", which generate a fuction with the name 'funcname' 10 is the ntuple id # >exit
Then, the file named 'funcname' is generated in your directory. Edit the 'funcname' to implement the code whatever you want.
>paw >exec generic >ls -> you will see 'generic.f' in your directory.
>paw >hist/file 1 filename >cdir //lun1/aaaa >nt/loop 10 funcname nnnn <- nnnn is the number of events to be processed.
There is also a kumac file to run the tele.f program. You will learn how to run the program out of this kumac content. See
* telescope plane correlation h/file 1 lh2035dst cd //lun1/strp nt/loop 10 tele.f 1000 cd //pawc exec meta#open <- meta.kumac to open paw.ps zone 2 2 h/plot 102 h/plot 103 h/plot 107 h/plot 108 exec meta#close <- meta.kumac to close paw.ps
To execute, you can do
>paw >exec example >exit
Then, a ps file, paw.ps, is generated for the print-out. The meta.kumac file opens and closes the postscript file, paw.ps.
Other infos such as the DST logs, etc., can be found on WWW. A list of pointers are listed in the beamtest page (of KEK). The page is
You can reach the info via the pointers directly from the ATLAS page of www.cern.ch -> subdetectors and working group -> inner detector -> Barrel sector prototype -> offline analysis -> offline description -> DST's...