Hello, Since we have new students that take a stab at some calibration for the large bunch of 200 GeV AuAu data, I quickly worte two scripts that aim at checking the result of the gtr stage by exploring the histogram files. There are two scripts : 1- brahms_app/do_app/util/histmerge.sh 2- brahms_app/do_app/util/checkdata.C The 1st one is used for merging histogram sequences into histogram runs. It usage is as follows : ./histmerge.sh -h Usage: [option] --help -h Gives this help --begin -b First run to look at, default is [0] --end -e Last run to look at, default is [0] --disk -d brahms data disk id, default is [16] --snn -s Snn of the reaction, default is [200] --collision -c Collision system, default is [auau] --disk -d brahms data disk id, default is [16] --production -p Production version, default is [1] It only works if you scan official directories /brahms/dataxxx ... It will merge sequences of the _LATEST_ version of a given production for the runs within the input range (-b <run> -e <run>). If you ignore the -e option, then it will only scan the -b option. Once you have histogram files that are run based, you can use the checkdata.C root script. Open root, load the macro, e.g. : root [0] .L checkdata.C root [1] checkdata("<path to your merged histogram files>", <sequenceMode = kFALSE>, <version filter = -1>, <production = 1>) The meaning of the arguments is : 1- path to your histogram files 2- if you want to scan data at the sequence level (in which case it's only one run at a time). kFALSE means at a run level. 3- if you are interested in a particular version#. A value of -1 means latest version available. 4- production # (1 by default) Examples : checkdata("/nfs/hehi/hehi30/hehi/ristea/DATA", kFALSE) gives me : ==== Welcome to the gtr data checker! ==== Warning]: no version number specified, I will scan the latest version only Looking up hist files in /nfs/hehi/hehi30/hehi/ristea/DATA found [470] files Select an option : - Global track matching [0] - FS Momentum Consistency [1] - BB Vertex offset [2] - TOF-Track Matching [3] - RICH PID [4] - Quit [5] Option : Then you have to choose an option. You can repeat checkdata(...) for another check. If you don't change the arguments, it will not rescan the directory (useful when many files). The sequence mode works if you scan a directory containing sequence histogram files like /brahms/data/..../rXXXX/gtr/ In this case, you will be prompted for a run number. The options are right now : gtr matching parameters FS momentum consistency (i.e. pD2,3,4 - pRefit) RICH Pion mass TOF-Track matching (match / pointed Slats) BB Vertex - TPM1 vertex Feel free to add some more stuff. Note that since I do some fits internally, it might take some time for root to process a large number of fits when there is not enough statistics. I wrote this macro quickly so someone can certainly add some gards for this kind of things but usually it works nicely. Hope this helps. Djam PS: don't try it on not official files (i.e. with weird filenames, it's not gonna work properly). -- Djamel Ouerdane ------------------------------------------o | Niels Bohr Institute | Home: | | Blegdamsvej 17, DK-2100 Ø | Jagtvej 141 2D, | | Fax: +45 35 32 50 16 | DK-2200 Copenhagen N | | Tel: +45 35 32 52 69 | +45 35 86 19 74 | | http://www.nbi.dk/~ouerdane | | ouerdane@nbi.dk | o---------------------------------------------------------o _______________________________________________ Brahms-soft-l mailing list Brahms-soft-l@lists.bnl.gov http://lists.bnl.gov/mailman/listinfo/brahms-soft-lReceived on Tue Nov 16 10:49:54 2004
This archive was generated by hypermail 2.1.8 : Tue Nov 16 2004 - 10:49:59 EST