Status Update on LHCb Computing Personnel and Task Priorities – December Review
The LHCb computing personnel are currently insufficient to cover all activities, with an estimated need of 40 Full-Time Equivalents (FTE), while only 22.6 FTE are available for operations. Some critical activities, including documentation, performance testing, and software validation, remain uncovered. There is an urgent call for under-represented countries to contribute missing personnel, and a detailed task inventory will be shared with NCB members. This document outlines the shortfall in resources, ongoing development activities, and next steps towards addressing the staffing needs.
Status Update on LHCb Computing Personnel and Task Priorities – December Review
E N D
Presentation Transcript
December Status of Computing Personnel • Currently available people insufficient to cover all activities • Estimate ~40 FTE needed • 22.6 FTE available for operations • Some activities not covered • e.g. documentation, tutorials, event display, software validation, performance and regression testing, web services, Boole+Brunel+(DaVinci) integration • ~5 FTE working on Gaudi and DIRAC development • Barely sufficient to keep our software and computing abreast with evolving technology • CERN, Spain • ~3 FTE working on new activities • Small pockets of effort in various countries, for example: • Italy, UK, CERN (Data Preservation and Outreach) • Italy, Netherlands, Switzerland, CERN (Multicore R&D) • Shortfall ~10 FTE
January FTE share • ~3 additional FTEs identified following December NCB presentation • Encourage under-represented countries to provide missing people
Finding the missing people (slide shown in January) • Inventory of tasks being finalised • Detailed task descriptions, covering both (time limited) development activities and (continuous) support activities • Will be distributed to NCB members in 1-2 weeks • Ask countries to make commitments to work packages • Including both development and support activities • Formalise as addendum to computing MoU • Similar to sub-detectors MoUs • Aim for draft by February CB • Aim for approval at June CB • Regularly monitor compliance, e.g. once per year • If shortfall persists consider option to finance under M&O A • Proposal for cost sharing to be worked out
Finding the missing people • Inventory of tasks being finalised • Detailed task descriptions, covering both (time limited) development activities and (continuous) support activities • Draft distributed to NCB members last week
Project Work Breakdown Structure • Table A • Some fine tuningstill needed
Personnel requirement • Split into • Operation • Minimum neededformedium termoperation • R&D • Activities for improvement, inparticular neededforupgrade anddata preservation • But also to fitinto foreseeableresources for Run 2 • Mostly time limited • Can be smoothedby prioritizing(delayingsome tasks)
Remarks • Total requirement will evolve • Some tasks not yet included, some double counting • Total requirement is ~15 more than presented in December • Some additional items included, increases also ‘available’ personnel • Some time limited tasks counted in 2014 could be postponed to 2015 or later.
Finding the missing people • Inventory of tasks being finalised • Detailed task descriptions, covering both (time limited) development activities and (continuous) support activities • Draft distributed to NCB members last week • Ask countries to make commitments to work packages • Including both development and support activities • Process already started, some success, to be pursued
Coming soon • Updated tables of personnel shortages • Cross referencing WBS of Tasks note • Expect NCB members to validate • Basis for looking for additional contributions
Finding the missing people • Inventory of tasks being finalised • Detailed task descriptions, covering both (time limited) development activities and (continuous) support activities • Draft distributed to NCB members last week • Ask countries to make commitments to work packages • Including both development and support activities • Formalise as addendum to computing MoU • Similar to sub-detectors MoUs • Aim for draft by February CB • Pierluigi’s talk • Aim for approval at June CB • Regularly monitor compliance, e.g. once per year • If shortfall persists consider option to finance under M&O A • Proposal for cost sharing to be worked out
Next steps • Finalise Tasks document and personnel tables • Latest by end March • Address shortages • Look for new commitments (with help from NCB members) • Prioritise “R&D” tasks • Present status at June CB • CB to decide how to proceed • Longer term: • Review tasks document each December • Review personnel each January • Report to first CB of the year