Re: [Brahms-dev-l] question about cvs

From: Hironori Ito <hito@rcf.rhic.bnl.gov>
Date: Fri Apr 14 2006 - 21:42:58 EDT
Hello,  I agree with you that these things should not be stored in cvs.  
My suggestion would be the following.

1st method:   Do similar to the file catalog.  Store the information to 
locate the required file (or files) from the database.  If the files are 
important (and can not be remade easily), then copy also those files to 
HPSS for archives.

2nd method:  Or, you can store histogram (or histograms) itself in 
database.  To do that just serialize it (or them) and store in MySQL as 
blob.  You can do very easily in RUBY with Marshal class.  (or you can 
do also easily in Java, but I guess that is what our BRAT database codes 
also do for arrays of data.)  But, I am not sure how fast this process 
is.  And, the response of the database might be too slow with larger 
histograms for someone's taste???

Hiro

Christian Holm Christensen wrote:

>Hi Erik,
>
>On Fri, 2006-04-14 at 14:51 -0500, Johnson, Erik B wrote:
>  
>
>>Brahms,
>>  I have generate a number of post-dst production corrections on a run
>>by run basis which are stored in TH2D histograms.  The corrections are
>>called by my banapp class to generate the best reaction plane from the
>>dsts.  I figured that I should save these parameters in cvs.  
>>    
>>
>
>Probably a data base (say a rootd server) would be a better choice. 
>
>  
>
>>So I put them in brahms_app.  I have gone through a number
>>interations, some have been saved to cvs and then removed.  Now there
>>is an Attic folder in one of my directories that has 44M of
>>histograms.  As a consequence of this, I cannot commit the paramters
>>to cvs.  Here is the error I get.
>>
>>cvs commit: Examining .
>>Checking in FlatHistos_Avg.root;
>>/afs/rhic/brahms/BRAHMS_CVS/brahms_app/ebj_app/Flow/ResCor/params/run04/auau/200/FlatHistos_Avg.root,v  <--  FlatHistos_Avg.root
>>new revision: 1.2; previous revision: 1.1
>>cvs [commit aborted]: error closing lock file /afs/rhic/brahms/BRAHMS_CVS/brahms_app/ebj_app/Flow/ResCor/params/run04/auau/200/,FlatHistos_Avg.root,: Disk quota exceeded
>>cvs commit: error closing lock file /afs/rhic/brahms/BRAHMS_CVS/brahms_app/ebj_app/Flow/ResCor/params/run04/auau/200/,FlatHistos_Avg.root,: Bad file descriptor
>>
>>
>>When I try to remove an obsolete file I get this error
>>
>>Removing FlatList.root;
>>cvs [commit aborted]: error closing lock file /afs/rhic/brahms/BRAHMS_CVS/brahms_app/ebj_app/Flow/ResCor/params/run04/auau/200/,FlatList.root,: Disk quota exceeded
>>cvs commit: error closing lock file /afs/rhic/brahms/BRAHMS_CVS/brahms_app/ebj_app/Flow/ResCor/params/run04/auau/200/,FlatList.root,: Bad file descriptor
>>
>>
>>I woudl like to think if I remove the garbage in the Attic folder I
>>can commit without problems.  Does anyone have any sugesstions as to
>>what I should do?  
>>    
>>
>
>Log on to an RCF machine, cd to 
>
>  /afs/rhic.bnl.gov/brahms/BRAHMS_CVS/brahms_app/ebj_app/Flow/ResCor/params/run04/auau/200/
>
>and remove the Attic 
>
>  rm -rf Attic'
>
>  
>
>>I'll work on reducing the size of these histogram files for starters.
>>    
>>
>
>Perhaps you'd rather store scripts, and then simple update the script,
>rather than delete old and add new files.  
>
>CVS is not really meant to handle binary data. 
>
>Yours,
>
>  
>

_______________________________________________
Brahms-dev-l mailing list
Brahms-dev-l@lists.bnl.gov
http://lists.bnl.gov/mailman/listinfo/brahms-dev-l
Received on Fri Apr 14 21:43:30 2006

This archive was generated by hypermail 2.1.8 : Fri Apr 14 2006 - 21:43:37 EDT