---
# System prepended metadata

title: MultiXscale sync meeting 2022-10-24

---

# MultiXscale sync meeting 2022-10-24

## Notes

- **PO is on leave, back on 2 Nov 2022, we should reply by then**
    - includes new Gantt chart, etc.
    - partners should complete there work no later than Mon 31 Oct
    - edit shared doc with track changes enabled
- points raised by Barbara
    - PO accept to indicate whether each participant is EuroHPC member
        - unclear why this was requested
        - Carlo: this question was raised for all CoE's
        - mostly relevant for industry partners
        - goal is to understand if partners are already contributing to EuroHPC
        - unclear whether this is about individuals or institutions or countries
        - someone should check which partners are missing from EuroHPC
    - PM distribution are linked to task distribution
        - no plans to change effort per partner, only tweak planning of tasks within WPs
    - points 6/7/8: each partner should reply via email on this
- Matej: question by laywer on how steering committee (SC) is composed
    - proposal is to just use WP leaders => OK?
        - no objections
        - Carlo: maybe a subset of WP leaders to avoid making SC too large?
    - SC members:
        - scientific part: who?
        - service part: who?
        - Matej as coordinator
        - Alan
        - Sara

## Revising WP tasks

- WP1 (development of EESSI service) + WP5 (support/maintance of EESSI service)
    - 1 additional "consolidation" task T_X
    - some effort for tasks T_X-T_(X-1) is moved into T_X
    - start/end month of current tasks T-X-T_(X-1)) is adjusted (shortened)
        - WP1
            - T1.1 (stable service): M1-M24
            - T1.2 (extending support): M9-M30
            - T1.3 (test suite development): M1-M24
            - T1.4 (RISC-V): M12-M48
            - T1.5 [new] (consolidation): M24-M48
        - WP5
            - T5.1 (support "portal"): M1-M12
            - T5.2 (testing): M6-M30
            - T5.3 (bot): M-1-M12
            - T5.4 [new] (consolidation): M12-M48
    - total effort remains the same for WP1 + WP5
    - deliverables fpr WP1 + WP5 are revised accordingly
        - for WP1: from 4 to 7 deliverables
            - intermediate + final report for T1.1 + T1.3 (2xM12, 2xM24)
            - 1 final report for T1.2, T1.4, T1.5 (1xM24, 2xM48)
        - for WP5: from 4 to 5 deliverables
            - final report for T5.1 + T5.3 (M12)
            - final report for T5.2 (M30)
            - intermediate + final report for T5.4 (M30, M48)
        - reporting efforts spread across partners involved in WP1 + WP5
            - need to check where UB (Alan) would be involved in reporting effort
            - also need to check deliverables for RUG
    - Caspar (SURF) and Kenneth (UGent) are making necessary changes in shared doc for WP1 + WP5
- WP2
    - first deliverable would be split between WP2 partners, individual report from each partner involved
        - more details needed on what will be done with waLBerla
            - Sauro: may not be waLBerla in the end, is that a problem formally if it's not?
            - flexibility of maybe switching to another software should be clear in task description
            - other option is OpenLB
            - both are frameworks which can be extended, need to check which one is better
        - Alan: problem with ?? should be fixed, Sauro agrees
    - Rudolf has changed their deliverable, focused on ESPRESSO, due M9
- WP3
    - one more deliverable needed here?
    - currently 2 deliverables, should be 3 (one more for T3.5)?
- WP4
    - already has 4 deliverables, should be one more at minumum
- WP6
    - Alan will do similar effort, shift things around
    - D6.1 will shift to M12 to cover first reporting period
    - current 4 deliverables will stay as is
- WP7
    - HPCNow is missing deliverables in 3 reporting periods
    - D7.2 in M24 (by NIC)
    - D7.4 in M40 (by HPCNow!)
    - can the partner for these be swapped?
        - that would mean two deliverables for NIC in M40 => stagger one to M45?
        - Alan/Matej: yes, ok to swap
    - one extra deliverable
- Leonardo and IIT need to provide 2 more deliverables
    - one extra already covered by splitting 1st deliverable in WP2
    - should also be in different reporting periods
    - PO asked for this so there is reporting for all effort being done
    - Sauro (IIT) and Carlo (Leonardo) will discuss this
- issue with budget for JSC due to double counting of overhead
    - feedback of project officer needed for this to see what is possible w.r.t. reallocating that PM budget
    - Barbara can share contact info for "in-case-of-emergency" person for this with Godehard
    - Alan: concerns ~122K euro (~12PMs)
    - options:
        - reuse money
            - to fix problem with underestimate of Leonardo's effort?
            - Carlo: can't shift money from one country to another at this point
                - Volker: may not be a problem?
                - Italy's budget contribution was approved already, increasing that is problematic
            - Godehard: would imply that (some) of the money can only be reallocated to Univ. of Stuttgart
            - Alan: could be motivated due to request for additional deliverables
        - give money back, because doing something else is too complicated

- next sync call: Fri 28 Oct at 11:00 CEST
    - Sauro is travelling
    - OK for the others

- Sauro is requesting to make sure that his GMail is always in CC in important communication on the project