[G12] G12 Yield

[Eugene Pasyuk]

Yes, it will work for short runs and single files as before, no 
difference. Th timeline is just a length of a buffer if you will. It 
must be no shorter than the longest chunk of data.

-Eugene

Paul Eugenio wrote, On 04/21/11 08:20:
> Hi Eugene,
>
> Would gflux work fine for small runs (and single files) if timeline was changed permanently to 1000?
>
>
> Paul
>
>
> --
> Prof. Paul Eugenio
> Florida State University
> Department of Physics
> Tallahassee, Florida,  USA 32306
>
> (850) 644-2585
> eugenio at fsu.edu
>
>
>
> On Apr 20, 2011, at 11:22 PM, Eugene Pasyuk wrote:
>
>> I looked into the gflux code and discovered that there is a problem if
>> we run it on entire run at once. The way it is now it has a storage
>> reserved for only 50 intervals. This is fine for single file. However,
>> The whole run in g12 may have over 700 intervals. In that case it will
>> produce the flux for the first 50 intervals.
>>
>> The fix is simple, as follows.
>> At the beginning of the gflux.c file in the section where some global
>> variables are declared and initialized there is a line:
>>
>> int timeline = 50;
>>
>> This number should be change to something which is larger than the
>> longest run duration in units of 10 sec. 1000 probably should be enough.
>>
>> -Eugene
>>
>> mkunkel at jlab.org wrote, On 04/20/11 21:38:
>>> Greetings G12,
>>>
>>> I had promised the new Yield Plots, however I have found a new bug in the
>>> GFlux calculator script.
>>> When I run the script, I returns me a higher gflux then what was initially
>>> there.
>>> I have attached a plot depicting this discrepancy and was wondering if
>>> this can get looked into.
>>>
>>> Thanks
>>> MK
>>>
>>>
>>>
>>> _______________________________________________
>>> G12 mailing list
>>> G12 at jlab.org
>>> https://mailman.jlab.org/mailman/listinfo/g12
>> _______________________________________________
>> G12 mailing list
>> G12 at jlab.org
>> https://mailman.jlab.org/mailman/listinfo/g12
>