Re: [Brahms-dev-l] filecatalogue problem

From: Hironori Ito <hito@rcf.rhic.bnl.gov>
Date: Wed Nov 30 2005 - 09:00:45 EST
Done.  Try your program.  Make sure it is picking up right(desired) file.

Hiro


Hironori Ito wrote:

> Hello.  I think HY and FV misunderstood my fix.  What I can easily do 
> is to change the production version No with ProductionVerId=31 to  be 
> 3 from 2.  (I am assuming that that is what a person wanted to 
> recently anyway.)  This does not change the production version No (2) 
> with ProductionVerId=23.  Now, the possible problem will occure if 
> there are already data with ProductionVerId=31. However, looking at 
> the database, I don't see any entries with ProductionVerId=31.  
> Therefore,  this will fix your problem.
> Hiro
>
> Hongyan Yang wrote:
>
>> Hei Hiro,
>>
>>    thanks for your response!
>>    In fact, what I want to do is to use the gtr file which is on disk 
>> now (the gtrs with ProdVer=1 is on HPSS only right now) to figure out 
>> the right time offsets for TOFW in dau runs - since these gtrs were 
>> generated in this year, I am not going to do this part but the dst 
>> production. But if you think it is ok or it won't hurt much to change 
>> the production version from 2 to 3, then I may do it. But could you 
>> please tell me how I can manage the change in the database or where I 
>> can find information related to it? Thanks a lot.
>>
>> Best regards,
>>  Hongyan
>>
>> Hironori Ito wrote:
>>
>>> Hello.  The problem is not your script.  It is in the database.  
>>> Someone recently has added new gtr production version (#2) for run 
>>> period 3 despite the fact that there exits already the gtr 
>>> production version 2 for the same data set.  (I know it is the most 
>>> recent production entry since it has the higherst  version id.) 
>>> Therefore, query to our database will fail.  (I guess that user was 
>>> not carefull and the web interface did not have check for dumb 
>>> mistake.)  Anyway, the easiest way is to change this production 
>>> version to be 3 (not 2).  Then, your problem will disappear.  Is 
>>> this what you (whoever added new version) want?
>>>
>>> Hiro
>>> _______________________________________________
>>> Brahms-dev-l mailing list
>>> Brahms-dev-l@lists.bnl.gov
>>> http://lists.bnl.gov/mailman/listinfo/brahms-dev-l
>>
>>
>>
>
> _______________________________________________
> Brahms-dev-l mailing list
> Brahms-dev-l@lists.bnl.gov
> http://lists.bnl.gov/mailman/listinfo/brahms-dev-l


_______________________________________________
Brahms-dev-l mailing list
Brahms-dev-l@lists.bnl.gov
http://lists.bnl.gov/mailman/listinfo/brahms-dev-l
Received on Wed Nov 30 09:02:10 2005

This archive was generated by hypermail 2.1.8 : Wed Nov 30 2005 - 09:02:17 EST