Performance of the RAM_Master script

A word of warning before you get started:
The files used in the process of creating the RAM-file are rather big! You should make sure that you have at least 2.5GB of diskspace available, otherwise you will run into serious space-problems and probably will have to do the whole process all over again! Currently it takes about 7 hours to create a RAM-file, which can be a VERY long time if the whole experiment is waiting for you!

The RAM_Master-script will write all the files created in the process to the directory you run it in. For this example I will be working in the /s/s8/e852/kuhnj/Ram/workspace/tmp directory.



/s/s8/e852/kuhnj/Ram/workspace/tmp (1) ~/bin/RAM_Master.perl
from RAM_Master-script: Starting kaon_4vecs! 
from RAM_Master-script: kaon_4vecs done! 


from RAM_Master-script: Starting mkitp_kaon! 
from RAM_Master-script: mkitp_kaon done (Kplus)! 
from RAM_Master-script: mkitp_kaon done(Kminus)! 


from RAM_Master-script: Starting the Dispatchers! 

from RAM_Master-script: Checking Dispatcher-status (kplus)..... 
disIO.connect: Connecting to the Dispatcher on loki (130.199.24.6), TCP port 10099...connected.
Notice: Disconnected from the Dispatcher, exiting...

from RAM_Master-script: Dispatcher (Kplus) is running! 

from RAM_Master-script: Checking Dispatcher-status (kminus)..... 
disIO.connect: Connecting to the Dispatcher on loki (130.199.24.6), TCP port 10095...connected.
Notice: Disconnected from the Dispatcher, exiting...

from RAM_Master-script: Dispatcher (Kminus) is running! 

from RAM_Master-script: Starting feedFromFile 
from RAM_Master-script: feedFromFile running....

from RAM_Master-script: Starting the SaGen/ramView jobs (Kplus)! 
        starting jobs on loki.... 
        starting jobs on physgi03.... 
from RAM_Master-script: Starting the SaGen/ramView jobs (Kminus)! 
        starting jobs on loki.... 
        starting jobs on physgi03.... 

from RAM_Master-script: Checking for end of file (Kplus) ..... 
disIO.connect: Connecting to the Dispatcher on loki (130.199.24.6), TCP port 10099...connected.
Notice: Disconnected from the Dispatcher, exiting...
from RAM_Master-script: Checking for end of file (Kminus) ..... 
disIO.connect: Connecting to the Dispatcher on loki (130.199.24.6), TCP port 10095...connected.
Notice: Disconnected from the Dispatcher, exiting...


from RAM_Master-script: Found end of file (Kplus) ...
from RAM_Master-script: Found end of file (Kminus) ...

from RAM_Master-script: Shutting down the Dispatcher! 


from RAM_Master-script: Found 1 Kplus-RAMchannel-files.
from RAM_Master-script: Found 1 Kminus-RAMchannel-files.

from RAM_Master-script: Starting add_RAM (Kplus)! 
from RAM_Master-script: add_RAM done (Kplus)! 

from RAM_Master-script: Starting add_RAM (Kminus)! 
from RAM_Master-script: add_RAM done (Kminus)! 


from RAM_Master-script: Starting hole-filling! 

        Starting to fill Kplus/H9 - file.... 
                pass 1 of hole-filling finished....
                pass 2 of hole-filling finished....
                pass 3 of hole-filling finished....
                pass 4 of hole-filling finished....
                pass 5 of hole-filling finished....
                pass 6 of hole-filling finished....
                Done filling Kplus/H9 - file. 
        Starting to fill Kplus/TPX1 - file.... 
                pass 1 of hole-filling finished....
                pass 2 of hole-filling finished....
                pass 3 of hole-filling finished....
                pass 4 of hole-filling finished....
                pass 5 of hole-filling finished....
                pass 6 of hole-filling finished....
                pass 7 of hole-filling finished....
                Done filling Kplus/TPX1 - file. 
        Starting to fill Kminus/H9 - file.... 
                pass 1 of hole-filling finished....
                pass 2 of hole-filling finished....
                pass 3 of hole-filling finished....
                pass 4 of hole-filling finished....
                Done filling Kminus/H9 - file. 
        Starting to fill Kminus/TPX1 - file.... 
                pass 1 of hole-filling finished....
                pass 2 of hole-filling finished....
                pass 3 of hole-filling finished....
                pass 4 of hole-filling finished....
                pass 5 of hole-filling finished....
                pass 6 of hole-filling finished....
                pass 7 of hole-filling finished....
                pass 8 of hole-filling finished....
                Done filling Kminus/TPX1 - file. 


from RAM_Master-script: Adding Kplus and Kminus for H9-RAM.... 
         ...done! 

from RAM_Master-script: Adding Kplus and Kminus for TPX1-RAM.... 
         ...done! 


from RAM_Master-script: Converting the H9-RAM....
         ...done! 

from RAM_Master-script: Converting the TPX1-RAM....
         ...done! 


from RAM_Master-script: script done!

Some explanations and remarks to the different output-lines of the script:

The program checks automatically for the end of the itp-files every couple of minutes. Therfore you will get a lot of the lines saying:
```
       from RAM_Master-script: Checking for end of file ....
```
There is absolutely no need to get worried about this!
It is possible (and very likely, if you have a lot of itape-events) that one of the two Dispatchers (one processing the Kminus- and the other the Kplus-events) finishes earlier than the other! In that case the finished Dispatcher will wait for the other to finish and then BOTH of them shut down at the same time!
The script counts the number of output-RAMchannel files. This is the same as the number of jobs running on the Dispatchers, i.e. if you run 4 SaGen-jobs on the Kplus-Dispatcher, the you should have 4 RAMchannel output files for the Kplus!
It is possible that the hole-filling program has to run several times before all the holes are filled. This because there are cases, where the program is not finding all the holes in one or two passes, due to some special topology of the holes in the RAM (see JK for an explanation, if you're interested). This is done automatically by the script. The script runs the hole-filling program as often as it is necassary and then stops. So don't be worried if you get different numbers for the passes!
The RAM-files are written to the files
```
       zzzz.RAM.h9 
       zzzz.RAM.tpx1 
```
These files will be loaded into the RAM and should be copied to the right directory, so that the RAM-files used in the run are all in one place. Right now the files are stored in
```
       /home/lemond/e852/config/par/ramH9.par
       /home/lemond/e852/config/par/ramTPX1.par
```

How the output of the files should look like:

kaon_4vecs-output (filename: zzzz.test):

     2.859334 -2.998207 194.939251 -0.642327 -0.476799 6.325029 6.394500
     4.790478 0.539977 205.702103 -0.441231 0.386656 3.293704 3.381774
     3.763858 -2.397939 174.903599 -0.415039 -0.335440 7.202602 7.239197
     3.428009 -2.806055 187.852746 0.991405 0.514454 2.517669 2.798200
     4.216081 1.435562 181.065084 -0.885677 0.454704 5.552074 5.662192
     0.474324 -0.077439 205.851162 -0.816535 0.196816 2.891067 3.050812
     3.402828 2.624364 196.213696 0.485509 0.018225 6.590352 6.626652

The first 3 numbers are the x- , y- and z-coordinate of the vertex and the last 4 numbers are the x- , y- and z-component of the momentum and the Energy.

SaGen/ramView output (filename, e.g: zzzz.ramch_kp_01):

     RAMx 47 RAMy 51 RAMz1 34 RAMz2 7
     RAMx 42 RAMy 51 RAMz1 30 RAMz2 7
     RAMx 44 RAMy 55 RAMz1 35 RAMz2 8
     RAMx 50 RAMy 61 RAMz1 33 RAMz2 9
     RAMx 31 RAMy 40 RAMz1 26 RAMz2 6
     RAMx 13 RAMy 22 RAMz1 22 RAMz2 5
     RAMx 74 RAMy 89 RAMz1 41 RAMz2 12

These are the RAMchannels that were set. RAMz1 is the TPX1-RAM channel and RAMz2 is the H9-RAM channel.

add_RAM output for the H9-RAM (filename, e.g : zzzz.ramch_kp_01.h9)

     RAMx 95 RAMy 121 RAMz1 0 RAMz2 16
     RAMx 95 RAMy 124 RAMz1 0 RAMz2 16
     RAMx 96 RAMy 113 RAMz1 0 RAMz2 14
     RAMx 96 RAMy 114 RAMz1 0 RAMz2 14
     RAMx 96 RAMy 115 RAMz1 0 RAMz2 14
     RAMx 96 RAMy 115 RAMz1 0 RAMz2 15
     RAMx 96 RAMy 117 RAMz1 0 RAMz2 15

add_RAM output for the TPX1-RAM (filename, e.g : zzzz.ramch_kp_01.tpx1)

     RAMx 95 RAMy 121 RAMz1 49 RAMz2 0
     RAMx 95 RAMy 124 RAMz1 47 RAMz2 0
     RAMx 96 RAMy 113 RAMz1 51 RAMz2 0
     RAMx 96 RAMy 114 RAMz1 52 RAMz2 0
     RAMx 96 RAMy 115 RAMz1 50 RAMz2 0
     RAMx 96 RAMy 115 RAMz1 51 RAMz2 0
     RAMx 96 RAMy 117 RAMz1 48 RAMz2 0

The output of dentist_RAM and the filled files looks just the same as the ones for add_RAM. The filenames are

     zzzz.holes_kp_01.h9            ,for Kplus/H9 holes
     zzzz.holes_kp_01.tpx1          ,for Kplus/TPX1 holes
     zzzz.ramch_kp_01.h9_filled     ,for Kplus/H9 filled file
     zzzz.ramch_kp_01.tpx1_filled   ,for Kplus/TPX1 filled file

convert_RAM (filename: zzzz.RAM.h9 and zzzz.RAM.tpx1):
```
     Data-file to load the RAM
     Created by J. Kuhn with the program 
     Date and time of creation: Fri Apr  4 10:54:06 1997
     For explanation of the format: see B. Hackenburg or J.Kuhn
     8 a 0 4
     7 e 0 8
     b 11 0 8
     a 12 0 8
     b 12 0 8
     b 13 0 8
     5 15 0 8
```
The first 4 lines are commenting lines and will be ignored when the RAM-file is read into the RAM. The data that actually loads the RAM isfollowing. The foramt is rather complicated, but there is a description for it on the RAM-webpage (http://lemond.phy.bnl.gov/~e852/documentation/trigger/RAM.html).

kuhnj@rpi.edu