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