| 1 |
orsi |
1.1 |
- HOW-TO-DIGIT, or "how to learn the PAMELA Digitizer in 5 minutes" |
| 2 |
|
|
- Creation: October 2007 |
| 3 |
|
|
- main contribution: S. Bottai |
| 4 |
|
|
- author: S. Orsi |
| 5 |
|
|
|
| 6 |
|
|
1) Install a database dedicated to simulation (if not already installed) : |
| 7 |
|
|
Set the PAMELA enviroment variable. Then set variable for the dedicated |
| 8 |
|
|
database : |
| 9 |
|
|
unset PAM_DBHOST |
| 10 |
|
|
unset PAM_DBUSER |
| 11 |
|
|
unset PAM_DBPSW |
| 12 |
|
|
|
| 13 |
|
|
export PAM_DBHOST=mysql://nameofmachine/namedatabase |
| 14 |
|
|
(example : PAM_DBHOST=mysql://srv-g2-01.ts.infn.it/pameladigit) |
| 15 |
|
|
export PAM_DBUSER=root |
| 16 |
|
|
export PAM_DBPSW=pameladb |
| 17 |
|
|
|
| 18 |
pamelats |
1.3 |
2) Create the database for simulation with the script install_GPAMELADB.sh, which is in Profiler |
| 19 |
|
|
directory under docs (you must run it in the dierectory itself or copy in the directory where the sql |
| 20 |
|
|
files are present ). The script will create the database and fill it with the approprate reference to |
| 21 |
|
|
the calibrations files for the simulation. |
| 22 |
|
|
(This is possible only for CVS version after 9/10/2007 , when the calibration files and their link have |
| 23 |
|
|
been put on the repository.) |
| 24 |
orsi |
1.1 |
|
| 25 |
pamelats |
1.3 |
3) Fill the GL_TLE table with "YodaProfiler -tle tle.txt" where the tle.txt file can be found in the |
| 26 |
|
|
Profiler directory under docs |
| 27 |
orsi |
1.1 |
|
| 28 |
|
|
4) Run the digitizer : |
| 29 |
|
|
|
| 30 |
|
|
./Pamelagp2Digits namegpamelafile.his |
| 31 |
|
|
|
| 32 |
|
|
It creates the files : |
| 33 |
|
|
namegpamelafile.pam (input for Yoda) |
| 34 |
|
|
namegpamelafile.gp.root (root conversion of namegpamelafile.his) |
| 35 |
|
|
|
| 36 |
|
|
5) Run yoda : |
| 37 |
|
|
yoda namegpamelafile.pam |
| 38 |
|
|
|
| 39 |
|
|
this will produce the file namegpamelafile.root |
| 40 |
|
|
|
| 41 |
|
|
6) Run the Profiler with the option -gpamela |
| 42 |
|
|
YodaProfiler -gpamela -yodaFile namegpamelafile.root |
| 43 |
|
|
It determines automatically the timesync and boot number and fills the database |
| 44 |
|
|
|
| 45 |
|
|
7) You can check the entry in the database with the |
| 46 |
|
|
R2-D2 -filename nomegpamelafile.root |
| 47 |
|
|
which tells you the idRun automatically associated |
| 48 |
|
|
|
| 49 |
|
|
8) Run DarthVader. |
| 50 |
|
|
Some examples of usage: |
| 51 |
|
|
|
| 52 |
|
|
DarthVader -zerofill -idRun 1 -ALL +RUN +CAL [ --no-crosstalk ] +TRK +TOF +AC +TRG +ND |
| 53 |
|
|
DarthVader -zerofill -idRun 1 +CAL [ --no-crosstalk ] -S4 |
| 54 |
|
|
|
| 55 |
pamelats |
1.3 |
The previous 2 commands have the same output, i.e. all detectors are included except S4 (the default |
| 56 |
|
|
behaviour includes the option "+ALL"). |
| 57 |
orsi |
1.1 |
If the TRK is not present the option --no-tracker must be specified: |
| 58 |
|
|
c) DarthVader -zerofill -idRun 1 -ALL +RUN +CAL [ --no-crosstalk --no-tracker] +AC |
| 59 |
|
|
|
| 60 |
pamelats |
1.3 |
It is recommended to run DarthVader specifying as output the file namegpamelafile.gp.root (file created |
| 61 |
|
|
by the digitizer, containing the gpamela data in root [see above]). |
| 62 |
orsi |
1.1 |
The option "--no-crosstalk" (and "--no-tracker") can be omitted in this case |
| 63 |
|
|
|
| 64 |
|
|
DarthVader -zerofill -idRun 1 -ALL +RUN +CAL +TRK ... -processFile namegpamelafile.gp.root |
| 65 |
|
|
|
| 66 |
|
|
In this way all gpamela info and Level2 info are contained in the same file (namegpamelafile.gp.root). |
| 67 |
|
|
|
| 68 |
pamelats |
1.3 |
With the latest DarthVader you can also include S4 and ORB without errors (but S4 data will be empty |
| 69 |
|
|
until fully implemented in the Digitizer code). |
| 70 |
orsi |
1.1 |
|
| 71 |
|
|
9) Default parameters for simulation are included in DarthVader since 9/10/2007. |
| 72 |
pamelats |
1.3 |
In case is not possible to use the CVS version after 9/10/2007 you must force DarthVader to use |
| 73 |
|
|
alignment and eta parameters needed by the tracker. |
| 74 |
orsi |
1.1 |
This is also possible if for some reason you want to test other sets of parameters. |
| 75 |
|
|
To do this simply write : |
| 76 |
|
|
|
| 77 |
pamelats |
1.3 |
DarthVader -zerofill -idRun 1 -ALL +RUN +TRK [ -4 /path-to-eta-parameter-for-simulation/ -5 /path-to-] |
| 78 |
|
|
... |
| 79 |
orsi |
1.1 |
|
| 80 |
pamelats |
1.3 |
To load different parameter types you have to use different numbers, according to the same notation of |
| 81 |
|
|
the DB: |
| 82 |
orsi |
1.1 |
|
| 83 |
orsi |
1.2 |
1 field map |
| 84 |
|
|
2 adc-to-mip |
| 85 |
|
|
3 charge correlation |
| 86 |
|
|
4 position-finding |
| 87 |
|
|
5 alignment |
| 88 |
|
|
6 VA1 mask |
| 89 |
|
|
|
| 90 |
|
|
The default parameters for the simulation are now in the CVS repository under the directory: |
| 91 |
|
|
|
| 92 |
|
|
DarthVader/param/trk-param/align_param_GP-0/ |
| 93 |
|
|
DarthVader/param/trk-param/eta_param_GP-0/ |
| 94 |
|
|
|
| 95 |
|
|
|
| 96 |
|
|
********* NB: ********** |
| 97 |
pamelats |
1.3 |
On the machines pamelatov in Roma2 the flags "-lmathlib -lpacklib -lkernlib" must be present in the |
| 98 |
|
|
Make file: |
| 99 |
orsi |
1.1 |
LDFLAGS = -g -lmathlib -lpacklib -lkernlib -llapack -lg2c -lm -lnsl -lcrypt -L/cern/2005/lib |
| 100 |
pamelats |
1.3 |
On other machines (for example pamelaws02 in Naples) the digitizer does not compile if the same flags |
| 101 |
|
|
are speficied, so they should be removed. |
Parent Directory
| 
Revision Log