Hi all, I've updated CRASH: CVS tag: CRASH-1-4-0 Version: 1.4.0 and installed it on i386_linux24 `new'. Major changes: * It works! * You can specify more than one run to make JSFs for. * USe option -U to turn on use of ASCII geometry and magnet field files. Default is off, and hence assumes that your script uses the DBs. * Old JSF file format and new incompatible !!!!!!!!!!!!!!!!!!!!!!! Sorry - no way around the later. For that reason I removed all JSFs of the bramreco account. I suggest you do the same for your `private' JSFs (which is depreciated might I add for exactly these reasons). More comments in the changelog below. Changelog: ---------- 2002-04-29 Christian Holm Christensen <cholm@rcas0014.rcf.bnl.gov> * CrJsfBmWriter.cxx, CrJsfBmWriter.h, CrJsfWriter.h, jsfbmwrite.cxx: Fixes for mulitple run JSF writes * mergebmfiles.cxx: minor fixes * jsfbmwrite.cxx: Options are now normal objects (as opposed to pointers). Took out a bad line. Added option -U for using Geo and mag files. * CrJsfBmWriter.h: Added fIgnoreGeoMNagFiles * CrJsfFile.cxx: See the comment in the header file of the same date. * CrJsfFile.h: MAke ChekcInput and CheckOutput methods static, as they are really utility finction that other classes may want to use. Added the method AddExecutableArg(const char* o, const char* d, const* char* f, bool r), to add a long option with a file argument to the list of user options. It doesn't really work, as the CRS software either easts the embeded `=', or makes the program loop infinitly - I can't seem to track down where it happens, as it happens on the client and access to there is sparse. But it's defently something that happens when tranlating the JSF into a real job i.e., somewhere in the CRS software :-( * testjsfbm.sh: small fixes * CrJsfBmWriter.cxx: A couple of fixes. There was a segfault thing in ReadFile - fixed. Now supports writting JSFs without the geometry and magnet ASCII files, since the Geometry DB seems to be up and running properly. This mode is turned on per default. If the user sets the data directory to the empty string, via the `-d' option to jsfbmwrite, it will be set `<brat_prefix>/share/brat/params' so that the BRAT DetectorParameters.txt will be used. Is this file really needed any more? Shouldn't all the information be in the Geometry or Calibration databases? Yours, Christian Holm Christensen ------------------------------------------- Address: Sankt Hansgade 23, 1. th. Phone: (+45) 35 35 96 91 DK-2200 Copenhagen N Cell: (+45) 28 82 16 23 Denmark Office: (+45) 353 25 305 Email: cholm@nbi.dk Web: www.nbi.dk/~cholm
This archive was generated by hypermail 2b30 : Mon Apr 29 2002 - 17:48:13 EDT