[Clas12_first_exp] CLAS12 First experiment meeting 12/19 @ 8:30 in F224/25

[Raffaella De Vita]

Dear FX,
as discussed today, the software group has been working on several fronts to prepare the transition to hipo4 and support the RG-A decoding of the Spring data. 

Tests of evio-to-hipo4 decoding are nearly completed and the next days will be dedicated to propagate the use of hipo4 to reconstruction. Tests of reconstruction will continue during the break. In my opinion, these are necessary to ensure there are no functionality gaps that may require changes to the data format and cannot be skipped. In addition, a strategy to handle efficiently scaler information and eventually cope with delayed helicity reporting (which doesn’t affect the Spring but the later data) has been discussed and will be implemented after the break.

In parallel tests of a SWIF-based workflow to efficiently decode the Spring data on the batch farm are in progress: as you know, these data are spread over a large number of tapes, which has made the decoding process slow and problematic so far.

All this work is expected to be completed in time to start massive decoding in early-to-mid January. This is inline with what mentioned in previous occasions. This work will also allows us to estimate how long the decoding will take, which I don’t think we know at the moment.

Best regards,
	Raffaella


> On 19 Dec 2018, at 16:25, Francois-Xavier Girod <fxgirod at jlab.org> wrote:
> 
> Dear all
> 
> During today's meeting we discussed delaying the start of decoding with hipo 4 to mid January or later
> At the end of January, we will be sharing resources allocation with RG-B, and we will be competing for disk access in particular with the data taking from all 4 halls
> This is a very significant difference with resources available during a couple weeks over the holiday break. Completing the decoding will easily take over a month, and will not be complete before the anticipated start of the cooking in early March
> 
> I personally do not think it is necessary to perform full chain reconstruction of the data to validate hipo 4 decoding. If it can be shown that event by event banks have the same information, and if it can be shown as was shown during the meeting that adc and tdc distribution are entirely identical, there is no reason for reconstruction to fail with identical information. 
> 
> Independently of what decision is made on the start of decoding, some specific questions were not answered during today's meeting. We should know what the progress and timeline are on the development of other necessary tools, including the handling of delayed helicity, as well as the new decoding framework using swif to write files in order on tape. 
> 
> Best regards
> FX
> 
> On Tue, Dec 18, 2018 at 11:40 AM Latifa Elouadrhiri <latifa at jlab.org <mailto:latifa at jlab.org>> wrote:
> Dear all,
> 
> We will have meeting tomorrow at 8:30 in F224/25
> 
> The focus is on:
> 
> The calibration & data processing we will review each system status and plan: DC, FTOF, CTOF, HTCC, LTCC, EC including timing, RF,CND and FT.
> DC alignment alignment status
> Data monitoring
> Documentation ans next steps
> Others
> Please let me know if you have any questions
> Best regards,
> 
> Latifa
> 
> 
> 
> _______________________________________________
> Clas12_first_exp mailing list
> Clas12_first_exp at jlab.org <mailto:Clas12_first_exp at jlab.org>
> https://mailman.jlab.org/mailman/listinfo/clas12_first_exp <https://mailman.jlab.org/mailman/listinfo/clas12_first_exp>
> _______________________________________________
> Clas12_first_exp mailing list
> Clas12_first_exp at jlab.org
> https://mailman.jlab.org/mailman/listinfo/clas12_first_exp

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/clas12_first_exp/attachments/20181219/df1b6eb8/attachment.html>