Hello, I don't know the exact detail of your problem, but you using a private DetectorParameters.txt is exactly what we are trying to avoid. If you want to do the dAu analysis, we have a file called asciidata/DetectorParametersRun03dau200.txt which should be what you want to use. I would suggest that you verify that this file is "correct" (ie matches the parameters in your private file) and if it is not correct, then make it correct. This file should be automatically selected if you choose a run in the run period of d-Au. The instructions are on the e-mail Flemming sent out detailing these changes. Kris Stephen J. Sanders wrote: > Hi, This is probably a question for Kris or Flemming. > When the changes were made to the DetectorParameters files I > was in the middle of the 04 run analysis. None of the changes seemed to > affect what I was doing whether I was replaying data files or geant > cdat files. > > Now I need to go back to the dAu analysis. However, I'm blocked from > replaying the cdat files with: > > Detector Parameter file not found. Contact BRAT administrator!!! > > Guess I need a BRAT administrator! My script explicitly sets the > DetectorParameter file: > > BrParameterDbManager *parMan = BrParameterDbManager::Instance(); > parMan->SetDbParameterFileName("DetectorParameters.txt"); > > but this seems to be ignored. > > Any suggestion? > > ...steve > > > _______________________________________________ > 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 Tue Mar 16 10:15:58 2004
This archive was generated by hypermail 2.1.8 : Tue Mar 16 2004 - 10:16:19 EST