We will have the DUNE General computing meeting:
Heidi Schellman is inviting you to a scheduled Zoom meeting.
Topic: General DUNE Computing meeting
Time: This is a recurring meeting Meet anytime
Join Zoom Meeting
https://oregonstate.zoom.us/s/162652254
One tap mobile
+16699006833,,162652254# US (San Jose)
+16465588656,,162652254# US (New York)
Dial by your location
+1 669 900 6833 US (San Jose)
+1 646 558 8656 US (New York)
Meeting ID: 162 652 254
Find your local number: https://zoom.us/u/acoyhG3WuF
DUNE Computing had a second workshop at Fermilab jointly with the WLCG Grid deployment board Sept 9-11, 2019. A plan for adopting CILogin certificates to improve interoperability between FNAL and European sites was made and put into action.
The University of York in Canada and Unicamp and CBFP in Brazil have joined the consortium.
Raja Nandakumar at RAL successfully integrated sam data delivery into the DIRAC framework.
Work on the Rucio data management system continues.
A major reprocessing and simulation of the protoDUNE single phase beam data was done with improved algorithms, notably the 2D deconvolution algoriths.
6.7 M beam events were reconstructed and 1.3M protoDUNE events were fully simulated and reconstructed.
In addition, data taking for the dual phase detector started in late August, 84 TB of raw data were written. Reconstruction infrastructure is in the final phases of testing before production.
We met the week before last to discuss splitting dunetpc into smaller pieces. The easiest way forwards is to split off those pieces of software that are under active development by the ProtoDUNE analysis team -- they have been the most vocal about the slow dunetpc builds. 35-ton code can be deleted, but it has many tests tied to it. Tom created a new Redmine project called protoduneana (Tingjun proposed the name) and has tested a build that has split it up. We have notified the analysis and reco groups to merge their feature branches before we do the split for real.
We iterated with the artdaq people on another memory corruption issue (valgrind found an invalid write, and there was a bad free in processing ProtoDUNE CTB fragments). The previous round of bugs has been addressed, including the memory leak which was a problem in ROOT.
One of our collaborating institutions has a too-strict firewall -- it does not permit ssh connections in either direction, to or from Fermilab. Can we lean on their computing services somehow? Or are we (well, really they) at the mercy of their policy?
python report.py 2019-08-01 2019-10-30
protodune-sp full-reconstructed physics v08_27% 7647345 188.895 TB
protodune-sp raw cosmics raw 3770495 227.07 TB
protodune-sp full-reconstructed cosmics v07_08% 1303795 8.221 TB
protodune-sp full-reconstructed cosmics v08_27% 3241140 65.056 TB
protodune-sp raw test raw 1460856 38.124 TB
protodune-dp raw cosmics raw 249252 119.624 TB
protodune-dp raw test raw 56092 35.679 TB
MCC11 full-reconstructed 60 0.0 TB
PDSPProd2 full-reconstructed 1340170 283.227 TB