[Clas12_software] ready for new release

[Raffaella De Vita]

Dear Latifa,
the cooking of run 4013 and 4150 was mostly meant to further validate 
the new tag and check the effect of the changes (code/geometry) on 
detector calibrations. However, low energy data would certainly give 
better sensitivity to the geometry changes as you mentioned. New T0 
calibrations for those runs runs will be needed, though, because using 
the event stat time in TBT impacts the T0 in dc calibrations. These were 
derived from run 4130 by Latif but would not necessarily apply to the 
2.2 GeV data that were recorded long before, because of changes in the 
TDC readout windows that were done in between.
What I would suggest is to compile a list of all the runs that you would 
like to have cooked both for specific studies and for data analysis and 
start the pass0 as soon as possible to check which runs will need to be 
re-calibrated.
Best regards,
     Raffaella


Latifa Elouadrhiri wrote:
> Dear Raffaella,
>
> It would be good to add to the list of data processing few files from 
> of the 2.2 GeV run also,  since we can judge immediately with the 
> position and resolution of the elastic peak. This should get better 
> with all the changes in particular the geometry.
>
> Best regards,
>
> Latifa
>
>
> On 7/1/18 3:35 PM, Raffaella Devita wrote:
>> Dear FX and Will,
>> all the changes we wanted to have in the new release have been merged 
>> to the development branch. Can you create a new tag?
>> Since there are major changes, the tag id should be 5b.5.0. It would 
>> be good to have a full list of the commits in the release note; also
>> this will be compatible with gemc 4a.2.4.
>> There will be probably a few more updates, beyond what was planned, 
>> in the next days from EB development and the swimming API but the tag 
>> can be already used for cooking since some validation on MC and real 
>> data has already been performed.
>> In particular it would be good to recook run 4013 and 4150. In this 
>> cooking, it would be useful to test the new region2 corrected 
>> geometry: to do that, the yaml file should be modified to use the 
>> service options indicated below.
>> Best regards,
>>      Raffaella
>>
>>
>> ...
>>    services:
>>      DCHB:
>>        torusMap: Symm_torus_r2501_phi16_z251_24Apr2018.dat
>>        solenoidMap: Symm_solenoid_r601_phi1_z1201_2008.dat
>>        useStartTime: "true"
>>        geomDBVariation: may_2018_engineers
>>        constantsDBVariation: calib
>>      DCTB:
>>        geomDBVariation: may_2018_engineers
>>        constantsDBVariation: calib
>