-
Notifications
You must be signed in to change notification settings - Fork 0
Sync meeting 2023 10 10
Kenneth Hoste edited this page Oct 22, 2023
·
1 revision
- Monthly, every 2nd Tuesday of the month at 10:00 CE(S)T
- Notes of previous meetings at https://github.com/multixscale/meetings/wiki
attending: Neja, Alan, Kenneth, Caspar, Lara, Bob, Julián, Maxim, Pedro, Susana, Satish, Xin excused: ...
-
internal progress report 2023Q3 to MultiXscale SC
- deadline 20 Oct 2023
- input (PMs + overview of activity) needed from all partners involved in WP1+WP5
- ideally directly in the progress report drafts
- OK for RUG, SURF, HPCNow!, UB
- still missing for UGent, UiB
-
deliverables due in M12
- 31 Dec 2023 is hard deadline for final version of these deliverables
- ballpark: ~10 pages per deliverable (shorter is better)
- executive summary is important
- 1-2 pages
- reasonable overview of what's in the report
- that's what is most likely to be read in detail by reviewers
- tie it + section overview back to deliverable description in MultiXscale project description
- planning
- early draft 1 Nov
- at minimum structure of deliverable (titles for sections + subsections)
- incl. high-level overview of stuff to mention (bullet-point style, or better)
- feedback by Alan on early draft
- complete draft ready by 24 Nov
- ready for review by others
- feedback by Alan representing SC by 1 Dec
- input for finalizing deliverables
- camera-ready by Thu 7 Dec, goes to SC
- final OK by SC by Tue 12 Dec
- ready to submit by Neja by Fri 15 Dec (hard deadline 31 Dec)
- early draft 1 Nov
- Question (for Alan?): who reviews drafts of deliverables?
- Alan will + 1 other project partner
-
date of review
- week of 19-23 Feb 2024 (probably Mon 19 Feb)
-
Overview of M12 Deliverables & Milestones
- D1.1 [RUG, report, issue, overleaf]: Report on shared software stack prototype
- complete draft by RUG (Bob), review by UGent (Kenneth) + Alan
- D1.2 [SURF, report, issue, overleaf]: Plan for the design of a portable test suite
- complete draft by SURF (Caspar), review by UGent (Lara) + Alan
- for software releases, there should also be a DOI
- D5.1 [UiB, other, issue, overleaf]: Community contribution policy & Github App
- type "OTHER" => contrib policy in EESSI docs + bot GitHub App release in GitHub
- 2-3 pager document along with software release
- executive summary (half-page)?
- docs can be included as appendix as PDF
- for software releases, there should also be a DOI
- complete draft by UiB (Thomas), review by UGent (Kenneth) + Alan
- type "OTHER" => contrib policy in EESSI docs + bot GitHub App release in GitHub
- D5.2 [UGent, other / report?, issue, overleaf]: Support portal
- type "OTHER" => support portal @ https://gitlab.com/eessi/support
- complete draft by UGent (Kenneth + Lara), review by HPCNow + Alan
- D6.1 [UB - Alan] Guidelines for Community Outreach, Education, and Training
- complete draft by Alan, review by Caspar
- Alan will set up Overleaf project for this
- D8.4 [NIC - Neja] Risk management Report
- Neja + Alan (?)
- big risk is money (national co-funding by Italy, Slovenia) and hires (JSC + scientific partners, NIC (Neja))
- late-ish kickoff
- late-ish hires: May (UGent), ??? (SURF), ??? (RUG)
- D1.1 [RUG, report, issue, overleaf]: Report on shared software stack prototype
-
Milestones due M12
- Milestone 2 [SURF]: "Shared software stack support for at least 1 accelerator". Means of verification: List of required dependency packages defined by WPs 2-4 included in published software stack (Table 3? Or Table 12?).
- interpretation is unclear here...
- ESSPResSo and/or LAMMPS with GPU support included is sufficient (Alan)
- first step is getting CUDA samples working in EESSI (ideally in Oct)
- how do we need to report on milestones?!
- in periodic report for 1st period M1-M12
- due early Feb'24, before project review meeting
- per task report for each work package
- cross-ref for deliverables for tasks being wrapped up in M12
- in periodic report for 1st period M1-M12
- Milestone 8 [NIC]: Applications developed by CoE (Table 11) available to users of EuroHPC JU systems via automated deployment platform, including documentation for users, required software stack, automated testing and quality checks
- How is this due M12?!
- Seems like this is a mistake in List of Milestones
- Alan: was injected during negotiation
- this exact same milestone is there for all CoE's
- we can defend this early with what we have in place
- Milestone 2 [SURF]: "Shared software stack support for at least 1 accelerator". Means of verification: List of required dependency packages defined by WPs 2-4 included in published software stack (Table 3? Or Table 12?).
-
overview of MultiXscale planning
-
WP status updates
- [SURF] WP1 Developing a Central Platform for Scientific Software on Emerging Exascale Technologies
- [UGent] T1.1 Stable (EESSI) - due M12+M24
- ....
- [RUG] T1.2 Extending support (starts M9, due M30)
- ...
- [SURF] T1.3 Test suite - due M12+M24
- ...
- [BSC] T1.4 RISC-V (starts M13)
- ...
- [SURF] T1.5 Consolidation (starts M25)
- [UGent] T1.1 Stable (EESSI) - due M12+M24
- [UGent] WP5 Building, Supporting and Maintaining a Central Shared Stack of Optimized Scientific Software Installations
- [UGent] T5.1 Support portal - due M12
- ...
- [SURF] T5.2 Monitoring/testing (starts M9)
- ...
- [UiB] T5.3 community contributions (bot) - due M12
- ...
- [UGent] T5.4 support/maintenance (starts M13)
- ...
- [UGent] T5.1 Support portal - due M12
- [UB] WP6 Community outreach, education, and training
- ...
- [HPCNow] WP7 Dissemination, Exploitation & Communication
- ...
- [SURF] WP1 Developing a Central Platform for Scientific Software on Emerging Exascale Technologies
-
AOB
- Extra person (Petra) to help out with MultiXscale website
see https://github.com/multixscale/meetings/wiki/Sync-meeting-2023-09-12
- https://github.com/multixscale/meetings/wiki/Sync-meeting-2023-09-12
- https://github.com/multixscale/meetings/wiki/Sync-meeting-2023-08-08
- https://github.com/multixscale/meetings/wiki/Sync-meeting-2023-07-11
- https://github.com/multixscale/meetings/wiki/Sync-meeting-2023-06-13
- https://github.com/multixscale/meetings/wiki/Sync-meeting-2023-05-09
- https://github.com/multixscale/meetings/wiki/Sync-meeting-2023-04-11
- https://github.com/multixscale/meetings/wiki/Sync-meeting-2023-03-14
- https://github.com/multixscale/meetings/wiki/Sync-meeting-2023-02-14
- https://github.com/multixscale/meetings/wiki/sync-meeting-2023-01-10
TO COPY-PASTE
- overview of MultiXscale planning
- WP status updates
- [SURF] WP1 Developing a Central Platform for Scientific Software on Emerging Exascale Technologies
- [UGent] T1.1 Stable (EESSI) - due M12+M24
- ...
- [RUG] T1.2 Extending support (starts M9, due M30)
- [SURF] T1.3 Test suite - due M12+M24
- ...
- [BSC] T1.4 RISC-V (starts M13)
- [SURF] T1.5 Consolidation (starts M25)
- [UGent] T1.1 Stable (EESSI) - due M12+M24
- [UGent] WP5 Building, Supporting and Maintaining a Central Shared Stack of Optimized Scientific Software Installations
- [UGent] T5.1 Support portal - due M12
- ...
- [SURF] T5.2 Monitoring/testing (starts M9)
- [UiB] T5.3 community contributions (bot) - due M12
- ...
- [UGent] T5.4 support/maintenance (starts M13)
- [UGent] T5.1 Support portal - due M12
- [UB] WP6 Community outreach, education, and training
- ...
- [HPCNow] WP7 Dissemination, Exploitation & Communication
- ...
- [SURF] WP1 Developing a Central Platform for Scientific Software on Emerging Exascale Technologies