Introduction

• Ian Bird (LAPP)

Goals of TSP meeting: - Kick off the collaborative work on the TSPs, help get the new people up to speed - Make a first set of draft milestones: - by each sub-project and project - by service (deployment status, functionality) - Start gathering real resource estimates (CPU/GPU/other, storage, & etc.) - need ground up estimates by sub-project - determine which project partners will be able to provide what level of resources to cross-domain TSPs - start to build an estimate of what we will ask for procurements (via ESCAPE & EOSC-Future), and what we will want from HPC - Understand first steps (e.g. in putting data sets into data lake, …) - Identify any missing input or show stoppers Some of this list can be action items/homework, but we need to get moving on this. If we can do some in the meeting, so much the better. On the planning/milestones: I think a few high level milestones is all we require - enough to show progress and to provide coordination points. We do not need fine grained planning (in my opinion). - Clarify personnel situation Note that we are obliged to monitor how the EOSC-Future funded effort is used, and report on it.

Dark Matter - overview

• Caterina Doglioni (Lund University)

Extreme Universe - overview

• Elena Cuoco

Planning

• Ian Bird (LAPP)

- Milestones, etc - ESCAPE software & services needed (Data Lake, OSSR, ESAP, WP4, - initial VRE, ... etc.)

Resource requirements

• Ian Bird (LAPP)

Initial estimates of needs and timelines

Discussion/planning

AOB

• Ian Bird (LAPP)

- Future meetings and frequency - DM/EU-specific meetings, General meeting as coordination point