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-lReceived on Wed Nov 30 08:14:39 2005
This archive was generated by hypermail 2.1.8 : Wed Nov 30 2005 - 08:14:46 EST