Almost ready for final stage of commissioning - having all datasets in and managed by Rucio
A lot of effort has been done recently to get to this point - working on final small details
How to map DQ2 subscriptions to Rucio rules/locks
Mapping of DQ2 replica classes primary, secondary etc
Mapping of DQ2 dataset owner to Rucio account
Protection for custodial data
Migrating 6M datasets will take a long time
Done by DB procedure run by Rucio dev, but most (unused by running jobs) can be done in background
Reminder: New DQ2 client can use datasets in DQ2 and Rucio
~50k datasets are "active" in panda/DDM subscriptions at any one point
To move those have to pause panda and stop DQ2 site services
Any open subscriptions will be picked up by Rucio
A date has not yet been set but likely mid-November
First the procedure needs to be thoroughly tested
Still a few small Rucio bugs to fix
Derivation Production
Full production on DC14 8TeV MC and period B samples was launched with AtlasDerivation-19.1.4.1 on October 20th
Data processing essentially done
Input data sets 60-80TB, output datasets about 70,77% for Muon and Egamma and 24% for JetTauEtmiss
MC with skimming done, with no skimming about half done
Output size about 32% for skimming
Validation tasks on DC14 13TeV MC submitted on Monday with AtlasDerivation-19.1.4.2
Good progress so far except the merging ratio. Requested files to be merged to 1GB instead of the default 4GB, however files are around ~100MB and less, being investigated
Full production to be launched earliest possible (today?)
Total input volume 222TB - can make rough estimates on output size but some groups are using truth thinning and trigger skimming so this will tend to push these sizes down
There are a lot of no-skim SUSY requests in 13 TeV so this might be a bigger portion.
MC Production
Grid not too busy in recent weeks, and not much in system right now
140M fullsim and 180M AF-II to be submitted (from requests in last couple of days plus some special configurations which are currently being set up)
ACTION ITEM FOR SITES: Sites please regularly check and confirm that your historical APEL data has been published and looks correct when comparing with batch system utilization
See example steps circulated by D. Qing (20100406)