[Frost] initeloss

[Michael Dugger]

Ken,

Thanks for clearing that up.

I think it makes sense to have eloss disengage from the database look-up.

-Michael

On Sun, 17 Oct 2010, Ken Livingston wrote:

> Hi Mike, Eugene and all,
>
> The answer to Mike's question is "yes it should be -4.0".
>
> To elaborate a little -
> The set up and use of the eloss rootbeer wrapper are described at.
> http://clasweb.jlab.org/rungroups/g9/wiki/index.php/Rootbeer%
> 2C_including_eloss_and_ExpTable
>
> There is actually a comment in sample_code/elossTest.C
>
> ...
> //targ_X, targ_y, targ_z, st_offset
> initELoss(0.0,0.0,0.0,2.0);
> ...
>
> As you can see, it needs the x,y,z target coords and start counter
> offset. This is instead of it having too look these numbers up in caldb.
>
> The reason it "crept in" is that the eloss package in not independent of
> the clas software packages and was never meant to be. Conversely, the
> rootbeer scheme is as independent as possible of the clas packages and
> all other stuff (except, obviously, ROOT). The only thing rootbeer needs
> to build and run is the clasbanks.ddl file which describes the BANKS for
> the data being analysed. On this rare occasion that means a number has
> to be gotten manually from the database and hard-wired in to your
> analysis code.
>
> (and Eugene, it didn't "creep in" to eloss, which I have never tampered
> with. It "crept in" to the C/C++ wrapper for eloss - a rootbeer extra
> which uses the standard checked out version of the eloss fortran code.)
>
> Sorry if that has caused confusion.
>
>
> Cheers
> Ken
>
>
> On Sat, 2010-10-16 at 08:51 -0400, Eugene Pasyuk wrote:
>> I have no idea what this 'initEloss" is doing and how it crept in!
>> It is not the original "InitEloss" that I wrote. This is different
>> function, note spelling difference. Maybe rootbeer experts should
>> explain us what is it. InitEloss form the original eloss package has
>> only one parameter: run_number.
>>
>> -Eugene
>>
>>
>> Michael Dugger wrote, On 10/16/10 00:36:
>>>
>>> Eugene,
>>>
>>> Thanks for the info.
>>>
>>> My COBRA stuff is getting the wrong info for eloss :(
>>>
>>> I'm so used to seeing the g8b numbers nothing looked wrong to me.
>>>
>>> In my rootbeer code I have
>>> initELoss(0.0,0.0,0.0,2.0)
>>>
>>> Should this be
>>> initELoss(0.0,0.0,0.0,-4.0) ?
>>>
>>> -Michael
>>>
>>> On Fri, 15 Oct 2010, Eugene Pasyuk wrote:
>>>
>>>> No, these numbers are incorrect. Those are g8b numbers.
>>>> For g9a/b ST-offset should be -4 and target position at 0.
>>>> This is what in caldb, run index: calib_user.RunIndexg9b.
>>>>
>>>> -Eugene
>>>>
>>>>
>>>> Michael Dugger wrote, On 10/15/10 18:24:
>>>>>
>>>>> Eugene,
>>>>>
>>>>> My call to initeloss gives this:
>>>>> InitEloss-I-: ST-offset is set to -24.059999
>>>>> InitEloss-I-: Target position is set to 0.000000, 0.000000, -20.000000
>>>>>
>>>>> Is this correct?
>>>>>
>>>>> -Michael
>>>>
>>> _______________________________________________
>>> Frost mailing list
>>> Frost at jlab.org
>>> https://mailman.jlab.org/mailman/listinfo/frost
>> _______________________________________________
>> Frost mailing list
>> Frost at jlab.org
>> https://mailman.jlab.org/mailman/listinfo/frost
>
>
> _______________________________________________
> Frost mailing list
> Frost at jlab.org
> https://mailman.jlab.org/mailman/listinfo/frost
>