Privacy and Security Notice
Archived Messages for CLAS_OFFLINE_1997@cebaf.gov: (no subject)
(no subject)
T.-Y. Tung (tung@CEBAF.GOV)
Thu, 08 May 1997 16:50:07 -0400
Joseph Manak wrote:
>
> Dear Off-line,
> During next week or two the recsis and its libraries
> will undergo a major change for the better. During this period
> the mapmanager calibration database will be phased in, one
> subsystem at a time. Due to the size and comprehensive nature
> of this upgrade (swapping in/out 1000?! lines of code) some problems
> with recsis may occur, this message is to give you an outline
> of the course of action I intend to take and what is required
> for off-site users to make recsis work. My intent is to minimize
> disruption of the normal development process.
>
> 1) A new TCL variable will be introduced called:
> mapmanager
> i.e. - set mapmanager 1;
>
> if mapmanager is set to zero the old fpack style
> flat files will be used just like now, if
> mapmanager is set to 1 the mapmanager calibration
> database will be used. The default will be the flat
> files until all of the bugs are worked out and
> calibrations for all subsystems are set.
>
> 2) Recsis will have to link to the mapmanager library,
> cms/link.mk will be modified to include the mapmanager,
> hence if people wish to compile off site they will
> have to have a local copy of the mapmanager library.
> (mapmanager compiles on Sun, AIX, and HP)
>
> 3) New files will be introduced into each library called
> xx_maputil.c (i.e. dc_maputil.c) which contain a variety
> of calls to the mapmanager. Before adding these files
> each library will be tagged by the name - premap - so that
> people can check out a copy of recsis without map calls
> in it. In addition map development can take place along
> a separate cvs branch for each subsystem, and then merge
> them together when we are happy with its performance.
> For people interested in manipulating the maps you
> should just link to the library for that subsystem.
>
> 4) A copy of the files in $CLAS_PARMS/Maps should be at your
> local institution, these are binary files and should be
> FTP-ed accordingly.
>
> 5) The new routines will (gradually) be hooked into the
> existing code, and the various calibration items will
> then be under map control.
>
> The biggest problem I can see is getting recsis to link to the
> mapmanager at all sites, if you do not have a copy of the mapmanager
> library you should update packages/Map type: make lib and
> try again - if you still do not have a copy of libmapmanager.a
> in your local area you should write or e-mail me and I will try to
> fix it. I will give people a few days to think about this before
> I force any of these changes on anyone. While I will do everything
> possible to prevent code from breaking I cannot guarantee anything,
> as always, people should link to the production libraries if they
> want to be guaranteed a working system (type: use_prod at the
> command line).
>
> -Joe
Correct me if I misunderstood something, I thought that the moral of
code management or having a release schedule and librarian
etc. is to allow a working version availible all the time and mimize the
chaos when new code is checked in . I sujust that we stick with the
plan of monthly and weekly release.
In addition, does anybody going to set up a watcher, so at least the
member of this mailing list will be notified when any routine changed.
It's in CVS manual p.34.
--
T.-Y Tung