Regular VC#9

Friday 9 Jul 2021, 09:30 → 11:30 Europe/Berlin

ZOOM

1 Greetings, agenda approval, misc.

1) Do we agree next topical VC to be on SOLPS?..
2) Do we need to discuss publications and conferences?..

SOLPS-ITER topical VC:

Date should be discussed.

1) S.Wiesen "What is needed to reach convergence with SOLPS-ITER?"

 --> DEMO (WPDES)

2) K.Ghoos/KUL "Error and convergence assesment in SOLPS-ITER" 

3) W.Dekeyser "Extended grid status: new code features"

4) X.Bonnin "ITER needs and current developments"

     - bottlenecks, time-dependent, drifts?..

 

Leaning the code

Preparation to the "code camp" event. Concepting the leaning including the strategy of how to carry this out.

2 Guiding slides for the code leaning

Speaker: Dmitriy Borodin (FZJ)

CodeLeaningGL_DBorodin_v1.pptx

1) Use SLACK (professional licence is needed) [DB]

2) Blocking the whole week is preferable to keep the focus!

3) In case of any possibility we should do it in person being prepared for online as well. FZJ will be the host [DB].

4) Decisions on I/O should be agreed with neigbour TSVVs. IMAS and HDF5 relation should be clarified. [DB]

5) If OOP is used the class structure should be pre-concepted before the leaning event.

6) Are adjoints (TAPENADE) compatible with OOP?.. [JG/WD]

7) Concerns PB: learning is needed from all of us to use OOP; OOP may cause performance issues

8)  FORTRAN (OOP) is selected over C++

9) No full OPP reconception is attempted. We install objects by necessity, it is not self-purposed. We always should always be keeping the code usable.

10) Preconcepting the new core is necessary.

3 Experience from the recent HDF5 output development including OOP in FORTRAN

Speaker: Jorge Gonzalez (DIFFER)

2021-07-09 HDF5 and OOP.pdf

4 Experience from the EIRENE OpenMP parallelization and refactoring

Huw Leggate, Yannick Marandet, Paul Genesio

yannick_paul_huw_code_leaning.pdf

EIRENE licencing

EIRENE_DCoC_v2.docx

EIRENE_FZJL_v02Jul.docx

5 Licence summary and guidelines for the discussion

Speaker: Dmitriy Borodin (FZJ)

EIRENE_UA_DBorodin_v0.pptx

Remarks type A: "This passage in licence concerns me, because..."

•DB: Should we introduce “EIRENE-NGM-DEVELOPERS” group author name? Should we introduce official EIRENE reference, mandatory for “USERs”? Should we enforce the pin board rules?

•DB: Are “USERs-AD’s”, “EPL (EIRENE Public Licence)” are acceptable to all?

 

Remarks type B: "I suggest the following to be added/corrected in the licence..."

•GS/YM: we should enforce good practice to publish the modified code (or additional routines) as metadata together with the results.

•DB: Should developer code of conduct (DCoC) and role of PI be hardwired into the licences?

 

Remarks type C: "I have concern, but no explicit idea for the solution"

 

 

[Dead line: Fri, 16th of July]