WIMAS-2 Weekly Meeting

→ Europe/Berlin
https://kth-se.zoom.us/j/7764082514

https://kth-se.zoom.us/j/7764082514
Thomas Jonsson
Description

WIMAS-2 Weekly Meeting are technical meetings to plan and coordinate the development of the ETS-6 workflow.

 

Remote participation:

https://kth-se.zoom.us/j/7764082514

Thomas
Hide

WIMAS-2 14/10 Minutes

Minutes by Nathan Cummings and Thomas Jonsson

Whats new in ETS

 - fill summary tool presented
 - separate toroidal/poloidal rotation equations introduced in branch ‘rotation’ - replacing branch ‘bulk_rotation’
 - developments in Impurities
 - developments in core_profiles - ‘update_core_profiles’ actor introduced and update to ‘combine_core_profiles’ underway
 - new actor ‘database_hcd’
 - workflow updates with new actors

  • DY: So we can HCD as OFF, STATIC, INTERPRETATIVE. Why is not PREDICTIVE an option?
    • Answer from TJ: What we're selecting here is the power wave forms and not the computational mode source profiles.
  • AP: You already have an update_core_profiles to update core_profiles each time equilibrium is updated. Do you also modify the transport coefficients?
    • PS: Need to update transport coeffs if updating core_profiles
    • PS: We cannot scale transport coefficient - they have to be recalculated. 
    • PS: Approach is use-case dependant
    • DY: Should we throw a warning?
    • PS: A control mechanism is necessary
      ...more details to be added later on.

Actions

  • NEOWES work - wait for Bruce

Core-edge sprint

Andreas: PENN actor for ETS6 by Monday
Need input from RUI re SOLPSZ1

ITER Scenarios

DC: Please included all input and output shot-files in the public database.

A new webpage was created with instructions on how to populate the public database:
https://users.euro-fusion.org/iterphysicswiki/index.php/The_public_IDS_database

For those who have write access in the public db:

For people who want to have their data stored in the public database:

  • Send an email to Pär Strand with
    • Specify: user-id (where shot-file is stored), database name (i.e. the machine or tokamak name), version of the data-dictionary (at present the version is 3), shot number, run number
    • Provide a text file with detail descriptions. This file should include a qualitative description of the data and where the data came from, such that it can be recreated. The instructions are (by David Coster):
What is the purpose of this shot/run?
* data from an experiment
* data to be used for code development test cases
* ???

For experimental data:
* why was this discharge chosen?  [what is interesting about the data? what physics problem was addressed in this discharge]
* what are the limitations of the data?  [e.g. core good, edge bad; no impurities]
* what modifications have been made to the experimental data [e.g. D split 50:50 into D & T]
* are there any references about this discharge [e.g. TRANSP runs, Task Force presentations]

For code development cases:
* how was the case created?
* what are the limitations of the data?
* what sorts of tests are envisaged with this data?

Abbreviations

DY: Dmitriy Yadykin
TJ: Thomas Jonsson
PS: Pär Strand
AP: Alexei Polevoi
DC: David Coster

There are minutes attached to this event. Show them.