[Frost] initeloss
Eugene Pasyuk
pasyuk at jlab.org
Fri Oct 15 23:21:49 EDT 2010
Brian,
I figure you probably use map files and you got your parms from
/grop/clas then this perhaps a rason. Those map files are regenerated
from the Main run index RunIndex of caldb. All the constants for g9 are
still kept in our private run index calib_user.RunIndexg9.
You can generate new set of maps for yourself from our run index.
A wrong positioning of the start counter in eloss definitely would
explain at least part of our inconsistencies.
We see that Mike and you got different numbers and they are incorrect.
Brian M. also has some troubles with his version of InitEloss.
I suggest everybody else to look carefully the messages coming form
InitEloss in your code.
What you should see is ST offset of -4.0 and target offset of 0.0.
-Eugene
Brian Vernarsky wrote, On 10/15/10 22:03:
> Eugene,
>
> When I run Eloss I always get ST-offset 2 and target position 0 for
> g9a. I have the most up to date clas parms. I'm not sure how big of
> a difference this could make, but this could definitely be some of the
> reason for our problems.
>
> Brian
> _______________________________________________
> Frost mailing list
> Frost at jlab.org
> https://mailman.jlab.org/mailman/listinfo/frost
More information about the Frost
mailing list