Submitted “~760M(bulk)+new requests” events and ~95% done (30M queued)
Due to the file losses at Taiwan, some specific samples do not have sufficient events (e.g. Powheg Z to tautau)
Will rerun samples for these. Discussing with Prodsys2 machinery to automate rerunning of lost jobs/files
Not much in the system at the moment, but some large requests in the pipeline
Expect the 500M fullsim in about 10 days
Also will run new Sherpa V+jets rather than rerun duplicated events samples
Set cpuTimeUnit=HS06sPerEvent and leaveLogs=yes for all tasks by default (from today 16:00).
Logs will be left on the DATADISK of the site where they are produced (i.e. not moved to T1)
Long standing AMI tag issue with processing type - merge tag has label "recon" instead of merge.AOD
Derivation Production
Should be 100% complete but some tasks went into finished state without completing all the jobs
Changed the brokerage today to send pmerge jobs to any other site after 24h (when the site went offline after finishing the reco jobs the pmerge jobs were expiring after 24h)
Task completion goal will be set to 100% for data derivation tasks so that the tasks will go to “exhausted” state instead of “finished” for us to act on them
AMI markes the datasets made from “finished” tasks as “ALL EVENTS AVAILABLE” in the same way as for “done” tasks. This should change soon after discussions with Prodsys2 and AMI teams.
A set of “finished” tasks have been identified from data derivations and reran to have complete stats, PC was notified yesterday to give the message in the meeting. We will provide the list of affected datasets in the dpd twiki
AtlasDerivation cache based on 20.7 will be built for reprocessing, deadline to collect the tags from groups is Monday December 14th
One more AtlasDerivation cache based on 20.1 is also requested for EXOT2 and HIGG4D* derivations, same deadline as above will apply
Reprocessing
Express stream - essentially done, using release 20.7.3.2
Three r-tags in the end, after periods G,H,J had to be resubmitted due to missed IBL bowing fix conditions folder
Question: Can empty containers be deleted as causes confusion for analyzers?
Some jobs with too large ESD, format really not useable anymore
One new crash so far, looks like problem with RAW input, see ADCSUPPORT-4407.
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)