From: Flemming Videbaek (videbaek@sgs1.hirg.bnl.gov)
Date: Mon Dec 09 2002 - 16:32:21 EST
Coming back to the issue of embedding the gbr2c routine into brag proper, I do agree it is a good suggestions,
and it is done., with the following caveat's that arose from discussion with Hiro. Sometimes we also use the
comis routine to debug, and or play around with stuff so I decide (executive decision) to change the names of
the rouitnes compiled into brag.
So
a) the names are changed from gbrxx -> gbxxx
b) the init_detector is renamed gbinit and is called from gb2c itself. So a typical sequence will
be in your kumac file
>call gb2c
>call gbfile('test.cdat')
>analyze gbana 1000 10
>gbend
All exsiting code and macro's that has call gbr2c.f will still work (backward compability), but you can
use the newer method's as described.
This involved adding gbr2c.F in src/user + creating some common blocks (.inc) files. Not too bad less than 1 hour
and it seems to work. The setup.kumac files are changed to work with the compiled gbana...
Brags version is now 1.1.26
Not done at this point :
you cannot set debug flag as before e.g. vector/input debug 1 1 0 0 0
as an example.
The makefiles (Makefile.am) should be modified such that a valid gbr2c.f cal be generated from the gbr2c.F file
basically by preprocessing the .F file with a preprocessor flag BRCOMIS set and then put it to some nice share/brag .. location.
This will keep updates to exist only one place.
------------------------------------------------------
Flemming Videbaek
Physics Department
Brookhaven National Laboratory
tlf: 631-344-4106
fax 631-344-1334
e-mail: videbaek@bnl.gov
This archive was generated by hypermail 2.1.5 : Mon Dec 09 2002 - 17:03:39 EST