Re: [Brahms-dev-l] Re: new 63 GeV files

Hi Hiro, Djam, et al,

On Wed, 2004-06-02 at 13:57, Djamel Ouerdane wrote:
> Ciao Hiro,

First off, great idea of having a proper file catalog for shared files. 

I think you should do the 

   BrEventIO::AddFileSet(Int_t runno, Int_t prodno, Int_t ver=-1);

I saves a bit of work on the users part (always a good motivation for
people to do more work :-)

> Thanks for the clarification. Nobody doubts that it will be a great 
> improvement. Still, I don't see how the <production> number can be known. 
> You say it's up to the user to decide which production to choose. But how 
> is this information available to the user ?

I guess it's like all the rest of the version numbers we deal with:  You
increment it, and send a mail to the proper mailing list saying you have
done so.

I could imagine something like this:

     - Create Quick'n'Dirty (Quirky and Defunct) calibrations for global  
       detectors
     - Increment to production version 0.1 
     - Create LTR's, GTR's, and what not
     - Create Quick'n'Dirty TOF, and other calibrations 
     - Improve calibrations for global detectors. 
     - Increment to production version 0.2 
     - Create LTR's, GTR's, and what not
     - Improve calibrations 
     - Improve cuts 
     - Increment to production version 0.3
     - Create LTR's, GTR's, and what not
     ...
 
> let's say you have two different data productions of the same run period.  
> Does it mean in fact two different data directory trees (data07 and data08
> for ex.) ? Not that we need to know about the guts of the file cataloging
> (dictatoring ?:) but this part is not clear to me...

I think Hiro said, that the production number isn't evident from the
file name, but only present as a one-to-many relation between file names
and production version in the database.  

I think it's analog to how CVS revision numbers and our tag versions
work, ins't it?   That is, the version number keeps incrementing, even
in the face of a production version, but the mapping from version number
to production version number is known to the database. (In a sense, you
could use CVS for all this :-)

Some question:  

Will the production version number be present in the file, as part of
the BrFileTag object written to file?  I think it should be. 

Will individual (or a group of) users be able to set up their own
catalog? 

Yours,

-- 
 ___  |  Christian Holm Christensen 
  |_| |	 -------------------------------------------------------------
    | |	 Address: Sankt Hansgade 23, 1. th.  Phone:  (+45) 35 35 96 91
     _|	          DK-2200 Copenhagen N       Cell:   (+45) 24 61 85 91
    _|	          Denmark                    Office: (+45) 353  25 404
 ____|	 Email:   cholm@nbi.dk               Web:    www.nbi.dk/~cholm
 | |



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