Sample extension : Fix implemented and working, some more use cases being checked - PRODSYS-328
Several datasets in container : Fix implemented and running. Checks ongoing - PRODSYS-327
. Circular buffer for pileup files : Pileup files were not being re-used so large digi+reco tasks crash - PRODSYS-351 - Fix implemented need to be deployed and can be done on-the-fly
Group contacts : Need final implementations to open the ProdSys2 interface to group contacts . PRODSYS-354
Almost all the requests have now been placed in ProdSys2. Still some issues to follow but system is getting more stable.
Simulation (last week): ran 10 Mevents/day
mc12_8TeV: 22M, mc14_13TeV: 41M
Monitor what has been submitted at link below (preliminary numbers using DEfT API) :
Processing of the bad files by Rucio was very fast, and most data recovered that can be
Workflow is much simpler than DQ2
Some lost files will be used to test prodsys2 recovery
GDP
Ensure that all operational procedures are available with Prodsys2/JEDI which used to use with Prodsys1/Panda
Are back at ~100k grid job slots utilized, but still only about half for production
Still many ongoing issues, some minor, some major
Main outstanding issues in production:
The dominant error rate recently is due to the submission of large simulation samples where the secondary minbias pileup or cavern background inputs could not be reused. This happens only to big tasks, each job uses few secondary inputs but when they are all used, the next jobs should start reusing the inputs.
Distribution of secondary inputs - The tasks cannot be assigned to the clouds because the primary and the secondary input datasets are not located in the same cloud. This need manual intervention to create rules ad-hoc.
Data file loss recoveries - In principle we can now recover missing outputs resubmitting the corresponding jobs from finished or completed tasks. With the opportunity of 500 k files lost at SARA we will start developing the operational procedure.
Derivation production merging - Unable to 100% complete the derivation production submitted last December. Suspect loopers in some of the internal merging jobs
New minor pilot release (tomorrow?) for event service
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)