The reason that I ask Will for meeting is to get read of
duality of EC analyses. My proposal is:
- only one analyses flow of EC data should exist,
- only one output BOS bank should be filled,
- modules in EC repository that are no longer in use should be removed.
As an analyses flow (solely) I am proposing to have so called
anal_opt=2 and as a resulting BOS bank modified ECHB. The current
EC manual in the CLAS_OFFLINE represent's my proposal.
If we agreed with this then am proposing to remove unused files
from ec repository, in order to prevent including them in libec.a.
I am ready to do all necessary changes and cleaning. To be more
constructive - IF I WILL NOT GET ANY COMPLAINS ABOUT PROPOSED
CHANGES BEFORE MONDAY I WILL DO IT.
Mean while I checked in some modified routines in EC. The main reason
is to have option weighting a strips in the peaks not only linearly
with energy but also as a logarithm of energy. I created new tcl
logical variable ec_ln_weights, that default is .FALS. (old linear
weighting). In order to have logarithmic weights one should redefine
it in the init.tcl (or newinit.tcl) as: set ec_ln_weights -1;
It seems that peak position on the edge is defined more accurate in
this case.
One more thing, I did some speed studies of RECSIS. Looks like EC
analyses for February data takes less then 1ms (~0.9ms) per event.
There is a some room for improvements and if link EC with BOS IO
(not with recsis, stand alone) then we can run it as fast as data
will come. Sergai's original idea was to rewrite a package on a C
and load into a crates in order to have pre-analysed data, that one
can make use of it. I think if we want that we can do it now with
existing code running it on DD ring as a stand alone.
Dos it have sense?
Regards Stepan.