Dear all,

Thank you very much for your contributions to the TSVV-A proposal!

I have tried to accommodate all of your requests. Unfortunately, this also required making some cuts to stay within reasonable limits.

Please review the current version (link below), particularly the overall allocations mentioned in the main table, and let me know if you have any comments or objections. 

If the remaining issues with some run type tables (separate emails) can be resolved by Friday evening, I would like to submit the proposal by then to meet an internal IPP deadline.

Thanks a lot, and best regards,
Tobias




-------- Forwarded Message --------
Subject: EUROfusion HPC proposal for TSVV-A
Date: Wed, 15 Oct 2025 16:49:35 +0200
From: Tobias Goerler <tobias.goerler@ipp.mpg.de>


Dear TSVV-A co-proponents,

Contrary to my previous promise not to email you again until the evaluation results are available, I need to address you all on a related matter. As many of you will be aware, the EUROfusion community has been invited to submit proposals for the 10th EUROfusion HPC cycle (1 Mar 2026 – 28 Feb 2027), see

Call.pdf - https://datashare.mpcdf.mpg.de/s/DkLEmtjd6kyK6p6
Annex 1 - Call Document.pdf https://datashare.mpcdf.mpg.de/s/yRFLwgyaW5npRNE

As before, TSVV projects are encouraged to submit a joint proposal, where the scientific details don't need to be covered as they are part of the already reviewed work plan.

Given that the final decision regarding the TSVVs may be taken very close to the EUROfusion HPC deadline (17 November) and we may not have much time for iterations, I propose that we start working on the HPC proposal already. A preliminary draft proposal incorporating information from last year's TSVV-1 proposal is available at

https://datashare.mpcdf.mpg.de/s/Bgr2o9z8fFNrFNP
(password: PEDLH26-EUROFUSION-HPC)

or https://datashare.mpcdf.mpg.de/s/Bgr2o9z8fFNrFNP/download
(password: PEDLH26-EUROFUSION-HPC)

As most of the information is to be provided per code, I suggest that anyone requiring significant HPC allocations for a particular code sends the individual run types/run type descriptions and the corresponding steps/run, walltime, node hours, etc. (see draft) to a single code contact:

(a) GBS: Brenno
(b) GENE: Tobias
(c) GYSELA: Guilhem
(d) GENE-X: Philipp
(e) JOREK-GK: Marina

The code contacts are then kindly asked to revise the specifics of their code in the main table, the code description and the run type list by
***Sunday, 2 November 2025***
(allowing time for iteration and balancing of individual allocation requests and assuming internal deadlines at beneficiary level).

Currently, the proposal considers all TSVV-A team members with more than 0 PM, but further participants can be added. Any feedback regarding the overall allocation and code shares is, of course, very welcome!

Thanks again for all your help! Best regards from Garching,
Tobias