[Frost] initeloss

Sun Oct 17 20:16:16 EDT 2010

I have no problems with being detached from the clas software. But 
people should understand what they are doing if they choose to do so. As 
we see we ended up not only being detached from the clas packages but 
also detached from the reality. At this point I am wondering if anyone 
used ST offset of -4.0 with g9 data.

-Eugene

Franz Klein wrote, On 10/17/10 20:03:
>
> my two cents:
> rootbeer was supposed to be independent from clas hackages (sorry
> packages), the only dependence: clasbanks.ddl, eloss (there is a dummy
> recmes.F in extra_packages/eloss_rb). In principle, we could add the
> opportunity to include caldb/map routines (since they are independent from
> the rest of the clas software) - and I think it might be a good idea to
> get not only target position, ST offset, etc, but also momentum
> corrections (though these are done quite unorganized by each run group or
> institution).
> However, as Ken pointed out, it should not be a requirement to get the
> stuff from caldb (because then we offsiders might get into the same
> troubles we have with accessing caldb in gsim, user_ana, calibration
> codes...).
> Besides, I changed the Makefile in clasg9 to allow several obj files of
> eloss routines (for different compiler versions).
> And a 2nd note: rootbeer was the software that did not cause complaints
> when compiling under 64bits!
>
> Have a nice evening
> Franz
> On Sun, 17 Oct 2010, Michael Dugger wrote:
>
>>
>> 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
>>>
>> _______________________________________________
>> Frost mailing list
>> Frost at jlab.org
>> https://mailman.jlab.org/mailman/listinfo/frost
>>
>
> ===============================================================
>                     Franz J. Klein, Associate Professor
>                     CUA, Department of Physics
>                     Washington, DC 20064
>     office: Hannan Hall 206          phone: 202-319-6190
>     or: Jefferson Lab,CC F-243       phone: 757-269-6672
> ---------------------------------------------------------------
> _______________________________________________
> Frost mailing list
> Frost at jlab.org
> https://mailman.jlab.org/mailman/listinfo/frost