[Brahms-dev-l] data quality and program/scripts to deal with values in db.

Hello.  From the previous mail from FV (shown below), a few people are 
assigned to be a gatekeeper for data quality. 

////
It was decided to create list of bad runs with justifications. This is 
rather broad area, so responsibility will be distributed by run-period. 
People who have identified bad runs should communicate this to the 
following people
# Cu-Cu 200 Gev : Selemon
# Cu-Cu 62 Gev : Truls
# Au-Au 200 and 62 GeV: Catalin
# Run 5 pp:  Ramiro
# Run 3 dAu Ramiro
////

To facilitate their work, I have made change to DB and made 
program/scripts to deal with them.

1.  RUNDB  are copied to brahms-db0 from brahms-rundb0.
2.  ChangeDataQuality.rb (in ~bramreco/DataProduction/scripts/util/) has 
be created to change run quality entry in Runs table.  (To use this 
program, look at the top of this code.)
3.  GetDstFileNames.C (in ~hito/analysis/) has been created to find and 
list only good dst runs for specific angle settings.  (to use this root 
script, look at the top of this code.  You should be able to copy/past 
to your proof macro code very easily.)  (If someone wants to make this 
script to more official brat class, be my guest.  :) )

A gatekeeper should  use ChangeDataQuality.rb to change the quality 
setting in the database.  And, all user should use this script to find 
your data files.  In this way, there is no need to keep individual list 
of bad/good runs in your script/or spread sheet.  And, we don't have to 
argue/worry whether one particular file should be used or not.   (If you 
use micro-dst/or some other strange format file, which are not in our 
database, I can not help you.)

If the program does not work. please let me know. 

Hiro


_______________________________________________
Brahms-dev-l mailing list
Brahms-dev-l@lists.bnl.gov
http://lists.bnl.gov/mailman/listinfo/brahms-dev-l