NPPS Leadership Team

[Torre Wenaus <wenaus AT gmail.com>]

Thanks Alexei. Revised version of 2022-2026

• 2022-2026: increase to ~5 FTEs

• Add 1 FTE database effort, working on EIC application of cross-experiment conditions DB and hardware DB common efforts

• Include management of metadata and analysis processes towards analysis preservation in the scope of the core team

• Core team contributes to computing model development

• Increase processing support to full FTE

Torre

On Tue, Jan 28, 2020 at 3:31 AM alexei <alexei.klimentov AT cern.ch> wrote:

Hi Torre,

 it looks very good, two comments, may be staffing plan should be more aggressive after 2021, ~5 FTE ?

 I would add a bullet about computing model (I remember Chris comment about amount of data, but CM isn’t only about data volume)

Cheers, Alexei

On Jan 27, 2020, at 7:53 PM, Torre Wenaus via Phys-npps-mgmt-l <phys-npps-mgmt-l AT lists.bnl.gov> wrote:

Thanks Brett, I had 3 words 'repositories, releases, containers' to cover that but I appreciate the detail! 

  Torre

On Mon, Jan 27, 2020 at 1:50 PM Brett Viren <bv AT bnl.gov> wrote:

Maybe these already are part of some existing bullets but I think there
is some effort closer to the end users that isn't called out.

- source release manager, coordinating with developers, setting and
  goals for future releases

- building releases, set up a meta-build system (Spack?) and then
  ongoing care and feeding.

- validating releases, including initial CI setup and later care and
  feeding, developing validating code, pushing on developers to provide
  tests

- distributing binaries, initial set up + care and feeding (CVMFS?,
  GitHub Packages?)

- end-user runtime configuration management (eg, production of user
  setup scripts, "environment modules", Spack "views").


-Brett.

Torre Wenaus via Phys-npps-mgmt-l <phys-npps-mgmt-l AT lists.bnl.gov>
writes:

> Hi all,
> Jamie asked for input on BNL EIC sw effort as input to the NP budgeting going on right now.
> Here's my first version. Comments appreciated.
>
> * 2020-2021: Yellow Report detector design and physics performance studies
>
> * Software work in support:
>
> * Community: detector simu, reco, analysis software
>
> * Labs:
>
> * software framework and toolkit for simu, reco
>
> * fast simulation
>
> * analysis tools
>
> * doc, tutorials
>
> * software infrastructure
>
> * distributed processing support (data and workload management)
>
> * 2022-2026: Detector development, test beams
>
> * Software work in support:
>
> * Community: detector simu, reco, analysis software
>
> * Community and lab
>
> * integrating streaming DAQ and offline computing in online+offline processing workflows
>
> * Labs: as above
>
> BNL EIC software effort
>
> * Today: ½ FTE
>
> * ½ FTE of computing infrastructure (Maxim) is the only dedicated effort at BNL (besides
>  Torre time on coordination). Small fractions of people with commitments elsewhere.
>  Particularly Chris leveraging sPHENIX software, Kolya supporting eic-smear, Alexander and
>  Elke’s postdocs.
>
> * in contrast, JLab has large fractions of Markus Diefenthaler (coordination, evgen), Dmitry
>  Romanov (jupyter based interfaces, tutorials, simu and reco infrastructure), Julia Furletova
>  (g4e simu framework), David Alexander and the Jana team (reco)
>
> * ASAP: increase to 2 FTE
>
> * EIC is starting a new ‘greenfield’ framework/simu/reco development effort. If we want to
>  play a role, we need effort
>
> * Add 1 FTE ASAP framework/simu/reco developer to participate in greenfield effort
>
> * Bring computing support effort to 1 FTE. Effort up to now is mainly collaborative tools,
>  websites etc. With software development consolidating to common community efforts, we
>  need software support (repositories, releases, containers, documentation tools) and user
>  support in addition.
>
> * 2021: increase to 3.5 FTE
>
> * Add a second dedicated software developer working both on common framework (including
>  contributing to user support and documentation)  and BNL-specific software priorities as
>  the detector collaboration(s) and institutional responsibilities take shape
>
> * Add ½ FTE for processing support: distributed computing, platform porting, analysis
>  processing. A small level that leverages existing activity.
>
> * 2022-2026: flat planning for now, sustain  3.5 FTEs
>
> Torre
>
> _______________________________________________
> Phys-npps-mgmt-l mailing list
> Phys-npps-mgmt-l AT lists.bnl.gov
> https://lists.bnl.gov/mailman/listinfo/phys-npps-mgmt-l

_______________________________________________
Phys-npps-mgmt-l mailing list
Phys-npps-mgmt-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/phys-npps-mgmt-l