*** Indico will be down for maintenance on Fri 8th Nov 7:00-9:00 CET (German Timezone) ***
Zoom Meeting Details:
https://us02web.zoom.us/j/83877454031?pwd=d01jd2U0bXM0OHkweGkxOXc5azlZdz09
Meeting ID: 838 7745 4031
Passcode: 726225
Additional materials relevant to the Project Board:
List of Actions from the 1st PB-Theory
No. |
Resp. Person(s) |
Description |
Status |
A1 |
Denis Kalupin, Frank Jenko |
Action on WPAC to establish and send Instructions to the TSVV PIs on data and code management procedures including location of hosting |
IN PROGRESS (installation of DevOps and virtual nodes have been endorsed by the HPC PB, implementation is in progress. Criteria for EUROfusion standard software were distributed and discussed with PIs at the E-TASC SB) |
A2 |
Emilia Genangeli |
PMU Admin shall investigate the possibility to increase the travel funds if possible and propose it to the next PB as change request. |
NOT STARTED (waits for signature of EUROfusion Grant Agreement and the final version of the budget) |
A3 |
Denis Kalupin |
PMU shall interact with the TSVV and ACH PIs to allocate the present mission budget at least for 2021 |
DONE (A few planned missions were reported by PIs, IMS mission application shall be submitted) |
A4 |
Denis Kalupin |
Potential absence of IMASified data must be included as a risk in WPAC PEP |
DONE (PMP is updated) |
A5 |
Denis Kalupin, Frank Jenko |
PMU & E-TASC SB shall propose the collaborative structure that would involve WPTE and ACH to insure that by 2024 experimental data required by TSVVs are available for all EUROfusion machines. (data mapping and data access tolls) |
IN PROGRESS (partially covered by established Thrust structure, additional discussions are needed within DataBase group) |
A6 |
Denis Kalupin |
PMU shall approach TSVV PIs to check if corrections to the work programme 2021-2022 are needed, the summary shall be presented to the following PB as change request |
DONE (PIs were approached via email and during the last E-TASC SB: no changes were reported) |
A7 |
Denis Kalupin |
Interactions between the E-TASC SB and the Theory PB shall be clearly identified in updated PEP. |
DONE (PMP is updated) |
Discussions:
Q: The PB asked for additional clarifications on A5, namely if other (than WPAC) work packages shall be involved in provision of IMASified data and if there are resources allocated to such activities?
R: Due to the budget cuts it is difficult to allocate additional resources to cover such work, nonetheless PMU will promote this activities through Thrusts, Data Base group and WPs.
Actions A3, A4, A6 and A7 were closed.
Summary of WP activities in 2021, deviations from the plan approved at the previous PB, Planning of 2022
Taking in account the coverage of EIRENE support in 2022 by ACH-MPG, it is proposed:
Reduce the EIRENE support trough ACH-VTT in 2022 (by 6 PMs)
Redistribute the freed 6pm on following tasks:
This revision was recommended by the E-TASC SB at its meeting on 29.Sept.2021.
The Project Board approved CR1.
The board took note on CR2 (as it is a minor editorial change to the PMP). FSD CO shall update the document accordingly.
WPAC Annual Work Plan - 2022
Frank Jenko (E-TASC SB Co-Chair) presented:
Discussions:
Q: How the presented monitoring approach will influence the distribution of ACH resources?
R: The monitoring table shall provide the overview, which will help all involved parties to understand “where we are” with development of TSVV codes. It will help to correct the ACH programme to support areas in the table, which are currently covered in red. The distribution of resources is the task of the E-TASC SB which will follow TSVV requests, taking in account the original numbers indicated in TSVV proposals.
R: E-TASC tries to avoid a “throw over the fence” approach in code development, TSVV and ACH shall have a one team approach, when thr ACH coordinator is also considered to be the code owner. It was always the goal of the E-TASC to develop professional software for community use.
C: The declared goal of EUROfusion standard software might be difficult to achieve, particularly with the shared responsibility for the code development between TSVV and ACH. The knowledge of some specific topics, like IMAS can be limited.
R: A training on IMAS was already organized by ACH-IPPLM (https://indico.euro-fusion.org/event/1246/, https://indico.euro-fusion.org/event/1247/), which made the introduction to the topic to all people who could attend it. For others, the training is recorded and materials are available at the meeting page.
C: Some of projects indicated IMASification as not applicable.
R: The summary table represents just a first collection of information from TSVV PIs. The E-TASC SB has the view that IMAS is the default standard and it will be required for all codes delivered in TSVVs.
Q: The composition of Thrusts is defined in a certain way, whereas there can be other synergies not covered by the present layout
R: Thrusts should not be setting up the boundaries for the knowledge exchange, all TSVVs reach out to any WP or attend any Thrust meeting. The current Thrust layout represents some logical
grouping, that seems to be reasonable and so far it works well. Thrust#4 is a bit more isolated, but the E-TASC SB promotes cross-involvement between stellarator and tokamak communities.
Q: Some of TSVV PIs report that allocated ACH resources are not sufficient, in particular to cover some code optimization tasks. Is there a mechanism to guarantee the fairness of ACH resource distribution?
R: Indeed there is some shortage of ACH resources in 2021-2022 due to startup phase. The distribution is always assessed and approved by the E-TASC SB following the TSVV requests and available ACH resources. During 2023-2025, ACH resources allocation will compensate for the initial unbalance in the distribution between TSVVs and a fair distribution will thus be obtained on the overall period 2021-2025.
Q: Are highlights indicated by Thrusts going to have impact on the TSVV programme?
R: Yes, E-TASC SB will follow up on them.
Discussions
C: There are issues reported by TSVV and ACH participants to establish an account on the ITER computing cluster
A8: FSD CO together with ITER RO to investigate the situation with establishing new accounts and propose a solution
C: Renewal of the Gateway User Board (GUB) is needed
R: FSD is already acting in this direction, unfortunately there have been no replies from WPs
A9: FSD at its general meeting shall discuss the renewal of the GUB with PLs
C: Some TSVV PIs reported a high load of the Gateway cluster
R: This can be temporary issue as also a number of nodes will be moves from Marconi-Fusion into the Gateway. Nothing was reported at the last Gateway operation committee
A10: FSD CO must bring this point to the attention of the next operation committee
Summary of WP activities in 2021, deviations from the plan approved at the previous PB, Planning of 2022
E. Genangeli presented the financial summary and CWP budget revision:
Discussions:
C: The work plan submitted to the commission corresponds to the previously foreseen amount of (~750M€), the work allocated to UKAEA and EPFL is supposed to be carried out as planned but to be covered with national funds for those beneficiaries as long as they are not associated.
Q: When JDC plans to start?
R: The JDC shall start on 01.11.2021, it will be located at JET and will be covered by national UK funds as other UKAEA contributions.
Q: With the current budget evolution, will it be possible to cover HPC resources in 2024-2025?
R: There are some reserved resources but a better answer can be only given after we know whether or not we get additional budget from the UK contribution, when the detailed situation is known.
Next, 3rd Theory Project Board will take place on 10.03.2022, 9:00-11:00 CET.
https://indico.euro-fusion.org/event/1451/
List of open actions
No. |
Resp. Person(s) |
Description |
Status |
A1 |
Denis Kalupin, Frank Jenko |
Action on WPAC to establish and send Instructions to the TSVV PIs on data and code management procedures including location of hosting |
IN PROGRESS (installation of DevOps and virtual nodes have been endorsed by the HPC PB, implementation is in progress. Criteria for EUROfusion standard software were distributed and discussed with PIs at the E-TASC SB) |
A2 |
Emilia Genangeli |
PMU Admin shall investigate the possibility to increase the travel funds if possible and propose it to the next PB as change request. |
NOT STARTED (waits for signature of EUROfusion Grant Agreement and the final version of the budget) |
A5 |
Denis Kalupin, Frank Jenko |
PMU & E-TASC SB shall propose the collaborative structure that would involve WPTE and ACH to insure that by 2024 experimental data required by TSVVs are available for all EUROfusion machines. (data mapping and data access tolls) |
IN PROGRESS (partially covered by established Thrust structure, additional discussions are needed within DataBase group) |
A8 |
Denis Kalupin Simon Pinches |
FSD CO together with ITER RO to investigate the situation with establishing of new accounts and propose the solution
|
NEW |
A9 |
Denis Kalupin Volker Naulin |
FSD at its general meeting shall discuss the renewal of the GUB with PLs
|
NEW |
A10 |
Denis Kalupin |
FSD CO must bring this point to the attention of the next operation committee
|
NEW |