Privacy and Security Notice

Archived Messages for CLAS_OFFLINE_1997@cebaf.gov: Re: Gsim: bgrid.fpk

Re: Gsim: bgrid.fpk

Maurik Holtrop (maurik@einstein.sr.unh.edu)
Wed, 09 Jul 1997 18:20:48 -0400 (EDT)

I agree with Joe that the geometry and the field strength could come from
the Mapmanager. This would mean that we feed gsim a specific run number to
model. (Hopefully this runnumber would be a representative of a group of
runs, and we're not going to need to simultate every run.)

However, the field maps depend on the version of the subroutine that reads
it. Similarly, the background simulation files won't change unless
somebody decides to make an improvement. There may be other files that are
fairly static. Should we put these under CVS ?
Or are they going to change so rarely that it's not worth the effort ?

Maurik Holtrop

> On Wed, 9 Jul 1997, Joseph Manak wrote:
>
>
> bgrid_XXX.fpk - are the field maps for the various CLAS magnets.
> Currently none of them are stored in the map database, of course,
> they can be placed in the database, but the mapmanager database is
> most useful if the item of interest varies with run number.
> As I understand it, the field maps are static and are not expected to
> vary with run number unless the geometry of the magnets is distorted - it
> is unclear to me how the map would have solved Maurik's specific problem.
> However, there are many aspects of the experimental geometry
> which can vary with run number - like the position of the forward
> carrage, LAC or the target, if the location of these
> detectors was read from the map database in GSIM we could easily model
> the configuration of the CLAS for any specific run number - this might
> be useful.
>
> Finally, somewhat on a tangent, some variables currently under
> TCL control might be more appropriate in the mapmanager database,
> like the toroid and mini-toroid current and the name of the
> appropriate road file for a given run - i.e. we can make it by default to
> use the map but can be overidden if the variable is explicitly
> defined.
>
> -Joe
>