EESSI
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Versions and GitHub Sync Note Insights Sharing URL Help
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       owned this note    owned this note      
    Published Linked with GitHub
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # MultiXscale WP1+WP5 sync meetings - Monthly, every 2nd Tuesday of the month at 09:30 CE(S)T - Notes of previous meetings at https://github.com/multixscale/meetings/wiki --------------------------- ## Next meetings - Tue 9 Dec 2025 09:30 CET - Tue 13 Jan 2026 09:30 CET - Tue 10 Feb 2026 09:30 CET => Proposal submission is done, we should rediscuss here a couple of items (see blow) - Tue 10 Mar 2026 09:30 CET - Items to discuss in 10 Feb meeting: - Tutorial videos - How to implement 2nd Review responses / what actions are needed (ideas were discussed, but check which one to take action on, divide tasks, etc) --------------------------- ## Agenda/notes 2025-12-09 attendees: - NIC: Petra - UGent: Lara, Kenneth - SURF: Caspar - HPCNow: Helena - UiB: Richard - RUG: Bob - BSC: Julian ### Notes - agenda points prepared by Petra - refreshed template for quarterly reports, to fill out by WP leaders - should be completed for 2025Q4 (Oct-Dec), ideally also for 2025Q3 (Jul-Sept) - was dropped for 2025Q2 because of Periodic Report that was required for project review - impact part: - positive impact related to MultiXscale objectives - risks - lack of Technical Manager (due to Alan leaving UB) - to be discussed further on Thu 11 Dec with Matej/Petra/Alan/Kenneth - access to EuroHPC systems after credentials expire - development project approved for Vega (Dec'25-Dec'26) - leverage service account on Deucalion => Kenneth will contact Bernardo - also aim for JUPITER -> schedule meeting - AWS/Azure credits - refresh of AWS credits coming (very) soon - Kenneth is in touch with Azure w.r.t. a keynote talk in Feb'26, will try to use that as leverage - RISC-V progress towards milestone (June 2026) - next meeting scheduled Thu 18 Dec - ball is in Kenneth's court currently w.r.t. getting relevant PR(s) merged - milestone 6 - good progress by Lara on LAMMPS+OBMD, LAMMPS+XX - Satish is working on pure waLBerla - Anirudh's case w/ lbmpy & pystencils - follow-up meeting on Thu 11 Dec - end goal is to have new EESSI test suite release that includes these tests - overview attendance of events (Jul-Dec 2025) - blog post on EESSI hackathon in Copenhagen => TODO Kenneth... - EESSI hackathon @ EuroHPC Summit 2026 - topic: onboarding software into EESSI - full day on Monday, incl. writing easyconfig - half day on Thursday afternoon - Kenneth will contact Cypriot people who attended hackathon - Kenneth will reply to JU to get update on announcing of EESSI Summit dates & location - update list of systems where EESSI is available - incl. Discoverer, JUPITER/MeluXina/Leonardo is a work-in-progress - also update count on software that's included in EESSI ## Agenda/notes 2025-11-11 attendees: - Petra - Pedro - Caspar - Susana - Bob - Helena - Thomas - Julian - Status of Amendment: - For NIC, they needed to communicate with the ministry, now awaiting response - Stuttgart: add few PMs, without cost increase (i.e. their PM rate turned out different) - No other responses from partners needed, so after these two items, it will be submitted to the portal & separately to the project officer (to send additional documents) - Alan no longer working at Univ. of Barcelona since end of Sept'25 - Ignacio hasn't found anyone for now - Petra: how does this affect the project? - Support rotation - Impact on Technical Manager role? - Should be taken care of by the Steering Committee - WP6 lead: Petra will also push Ignacio on this. Alternatively, another partner needs to take responsibility temporarily. - Only deliverables in our WPs that are left are all in M48, except the sustainability plan (M42), but description says final version in M40, so we'll aim for that - Risks: - Access to EuroHPC systems - Petra prepared access to Vega, waiting for Kenneth for a response - AWS sponsering for build resources: we have until early-mid December to get new funding from them - Last time: Kenneth/Alan/Bob talked to them. Idea was to provide a one-pager. That would be included in AWS overview of open source projects they are sponsoring. One pager is written and sent, but was mostly for next year. - AWS contact has a meeting with Kenneth around supercomputing - Kenneth should ask for an update about 1) the one-pager, 2) credits to fund the rest of the year - Next virtual meeting with AWS contact: 1st of December - Bob will keep an eye on the credits, if they really get too low, we kill all compute and keep them only for storage - To mitigate: should focus more on the checks we agreed on in https://gitlab.com/eessi/support/-/issues/206#note_2849563753 - Thomas will have a look at this - Collect `lscpu` output from different systems in a centralized location (support issue https://gitlab.com/eessi/support/-/issues/206) - General assembly MultiXscale: - March 2026, probably 13th, after the EuroHPC Summit (should be 10-12th) - Will be the last GA meeting - Petra will send around the date for the GA once it is final ### Report on 2nd review - points relevant to WP1+WP5+WP6+WP7 (Petra) - WP1 - RISC-V: set up a repo in development repository - Lots of software already there - PR to software-layer-scripts of EESSI to detect specific RISC-V architectures, the ones in the BSC cluster - For now we only optimize for generic RISC-V, but with the above PR we can optimize further - Next Friday: meeting on next steps with RISC-V - Milestone regarding risc-V toolchain: - Foss is there - LLVM is there, but not a formal EB toolchain - This is about to happen in EB (lfoss, etc), once that's merged we should try to get it installed for RISC-V - Bob reconfigured the bot on the BSC cluster - Couldn't get it to work with versioning scheme that Kenneth proposed (2025.06-1, 2025.06-2, etc) - WP5 - WP6 - EESSI happy hours are continuing - Going well, not a ton of attendance (60% internal, 40% external), but could try to advertise more - Thomas: What is our goal here? - Richard: interaction with users was one of the goals. But lately, there is little interaction from externals. - Caspar: maybe check with the attendees what their main reason is to attend & if they feel it should be continued - Richard: continue until the end of the year, then evaluate and see if/how we continue. - WP7 - Petra: will work with Julia, will share with partners a questionaire (before the end of this year). Please provide feedback on that. - WP8 ### Deliverables/milestones due in coming months - Milestone 6, M36: Tests implemented in test suite for key applications used in WPs 2, 3 or 4 - NIC: OBMD - 2 scripts, one producing data, one validating the outcome - Juelich: All + OBMD - Sorbonne: LPC3D, will provide input scripts - Pair up Lara, Satish, optionally Caspar with these three partners to implement it in ReFrame. ### WP status updates - WP1 (SURF - Caspar) - ... - WP5 (UGent - Kenneth) - ... - WP6 - WP7 --------------------------- ## Notes of previous meetings see https://github.com/multixscale/meetings/wiki ================= ## Agenda/notes 2025-10-14 attendees: - Pedro - Kenneth - Caspar - Susana - Thomas - Satish - Guilia - Petra - Alan - taking away 1 PM for SURF (due to higher PM rate, inflation) - Caspar: underspending in WP6, so thinking about consuming from that - also from WP1+WP5, proportional to effort - Thomas: also underspending in WP6 - started Happy Hours because of this, could be spending 3PMs if we keep this up until end of the project - repeat of webinars could be another PM - overspending in one WP, underspending in another is fine in practice - for UGent: transferring PMs to travel budget, taking it from WP5 - Caspar: look into short videos focusing on a particular topic (WP6) - just a couple of minutes - complements Happy Hours, more focused - software-specific (Espresso, OBMD, ...) - instruction video on dev.eessi.io, ... - Kenneth will make proposal with topics/scenarios - motivation for EESSI - EESSI hands-on demo - EESSI in CI - CIT @ UGroningen has some proper equipment for this - - Alan no longer working at Univ. of Barcelona since end of Sept'25 - impact on Technical Manager role? - Ignacio is trying to find a replacement ### Report on 2nd review - points relevant to WP1+WP5+WP6+WP7 (Petra) - WP1 - what do they mean with "reproducibility layer"? - => ask them to clarify? compat layer? software layer? - maybe better not to ask for clarifications - immutable release snapsots, DOI-tagged versions - tag specific revision of CVMFS repository, put DOI tag on it - make sure we don't garbage collect these! - need to sync with Bob on this - document that specifies how to access that revision, what's in it, etc. - incl. overview of available software? - combo of compat+software layer, across all GPU targets - how often should we do this? - attaching this to bi-monthly EESSI update meetings - container images or squashfs exports for these EESSI "releases" - first step towards "archiving" old EESSI releases - can be mounted in container with Apptainer - start with minimal report, gradually improve that - tagged revision + instructions on how to get access to this specific revision - keep track of mapping between DOI and revision in `EESSI/filesystem-layer` - also document/demonstrate how this helps scientific WPs - blog post showing how to run Espresso/OBMD/... - comprehensive rebuild/run instructions - insufficient docs on RISC-V & Arm - no overview of available software for RISC-V - Arm - docs on CPU detection, structure of repo - migration of legacy software modules to newest GPU generations - already done now? - we're building for all supported GPU generations already now (not yet at time of review) - GPU software installations have now been reinstalled in new structure (inc. CUDA sanity check) - we will also support Blackwell when relevant - WP5 - documentation lacks behind rapid development - software overview missing for EESSI 2025.06 & GPU software - also PR on squashfs - missing reproducility practices - document procedure used to reproduce installations for other CPU targets - cfr. work done by Bob/Caspar - cfr. changes made to EasyBuild - will be relevant soon again for `zen5` + `graviton4` builds in EESSI 2025.06 - testing should cover edge architectures, mixed CPU/GPU nodes, coupled workflows - what's meant with "edge architectures"? - mixed CPU/GPU nodes => already done? - not running tests for CUDA installations on Snellius yet, Caspar will fix this (by setting EESSI_ACCEL_OVERRIDE) - coupled workflows => portable tests coming for OBMD & co - scaling up of human resources (amendment?) - risk of increased support load due to EFP - (Thomas) set up regular meeting with sites? - strictly speaking requests not connected to scientific WPs is out-of-scope for MultiXscale - there's no room to scale up human resources in MultiXscale, not planned - WP6 - retention of ambassadors - more engagement/feedback from ambassadors? - more relevant to Transversal CoE - get people to refer themselves as ambassador for EESSI - clear instructions for ambassadors to give training themselves - maybe via Software Carpentry - make connection with EVITA project in last year of MultiXscale - => reach out to them - document ambassadors in EESSI docs - list of ambassadors (after they agree) - make it clear what it means to be an ambassador - share promo material - (traning) content should be regularly updated - EESSI Happy Hours - also planned repeat of webinars - ISC'26 tutorial proposal - better metrics to identify impact (of training sessions) - EESSI user surveys - 6 months after hackathon/webinar/... - for webinars => Nov'25 - for hackathon => March'26 - assess uptake of using EESSI in CI - ask them if they're using EESSI, for what, on which systems, ... - EESSI system surveys - update of EESSI - provide tooling to evaluate this - usage metrics for EESSI through Stratum-1 mirrors, friendly sites sharing info on proxy usage - scaling of training infrastructure - Magic Castle allows scaling up according to attendance - hybrid format helps with scaling - cluster-as-a-service for ambassadors - integration of EESSI in EOSC - WP7 - Business and Sustainability Plan (D7.3) - governance/ownership models post-M48, leveraging EFP - funding mechanisms => services, sponsorship, tenders - services: - sponsorship: - 10k/year as "gold" sponsor, logo on website - 50k/year as "diamant" sponsor, priority on support requests - in-kind sponsorship - people contributing to EESSI, donating their time, building expertise - AWS to keep hardware resources - support for tenders to solicit help for implementing features, onboarding software, ... - comes with overhead: writing tenders, evaluating tenders, legal aspects, ... - exploring making EESSI a Linux Foundation project - legal entity to accept sponsorship - robust KPIs for adoption, retention - robust KPIs for adoption, retention - some work done in EFP would help here - strengthening of qualitative metrics (outreach -> adoption) - user/system surveys - companies using it (StackHPC, Accenture, Nextmol) - try to engage with "lurkers" through focused webinars - business oriented messaging - D7.5 - WP8 - risk mitigation should be improved - recommendations - EIC Market Place - we should ask them to clarify the recommendations - https://eic.ec.europa.eu/eic-funding-opportunities/eic-pathfinder_en ? - Giulia: platform for *companies*, to let them scale up - maybe helicopter case? - exploitation brief for each exploitable result - EESSI + one of each showcase? - to go into final report, or D7.3? ### Deliverables/milestones due in coming months - ... ### WP status updates - WP1 (SURF - Caspar) - ... - WP5 (UGent - Kenneth) - ... - WP6 - WP7 --------------------------- ## Notes of previous meetings see https://github.com/multixscale/meetings/wiki ----------------------------

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully