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

Action from previous meetings

  • Jorge and Dave clarified the meaning of Hyper-diffusion.
  • Alexei added a reference to the Perevezev-Corrigan paper on numerical schemes for stiff transport:
    https://doi.org/10.1016/j.cpc.2008.05.006
  • Progress has been made on testing flux expansion in the ETS-6 (by Jorge).
  • Recent developments in the develop branch are now included in the branch IPramp. 

Active branches

The content of the flux-field in core_transport was discussed and it was agreed that this should include the actual flux when the equations are solved and the sources and intertia when the equations are not solved.

ACTION:

  • Thomas: Make sure the flux from the transport solver is implemented as agreed in the discussion above.

Planning the verification on ITER Scenarios

No-one objected and had any comments on the plan presented by Nathan. Therefore we will go ahead and implement them.

There are a large number of ASTRA cases in the ITER Scenario Database, we could use any of them. However, we should be aware that they are now working on improving the internal data-consistency in all of these shot.

Proposed tests:

  • Add test suite for checking the internal consistency
  • Note that there is already such a suite (developed or used (?) by ITER Expert Group). The latest person to use it was Colin Roach.

ACTION:

  • Thomas: Implement IDS consistency checking for ETS-6, to be used to analyse ETS-6 input and output.

Any other business

Gergo:

If anyone sees a warning from runaway-indicator, please let me know! They are now hunting run-away cases.

Jorge:

  • Testing the AL using data from est6
  • ETS-6 generates typically IDSs with 5 slices
  • They take 300-400 ms to read per IDS
  • But distribution_sources 10 times longer!
  • We need a way to avoid reading large IDSs when starting a workflow, using IDSs from ETS-6
  • Options:
    • Do not store distribution_sources, waves... - add option to not store them
    • Remove them afterwards with a script
    • Do not read them in UALInit; need a discussion on what IDSs to store.

ACTION:

  • WIMAS-2 team: Decide on which IDS to read with UALInit in the ETS-6 workflow.
  • Thomas: Implement decision on which IDS to read with UALInit in the ETS-6 workflow.
There are minutes attached to this event. Show them.