Streamwise Periodic restarts using flow.meta + Multizone PerSurface output by TobiKattmann · Pull Request #1527

Streamwise Periodic restarts using flow.meta + Multizone PerSurface output by TobiKattmann · Pull Request #1527 · su2code/SU2

added 4 commits

January 24, 2022 16:51

…h that setting.

Note though that the comment in the pressure update computation of the streamwise periodicity
still holds: Currently the pressure update for massflow is omitted in the first iteration,
as the function is called in the Preprocessing phase which leads to multiple calls during 1 iteration.
Ideally this whole method is called in another place or a setup has to be found which prevents multiple calls.

Not working yet. E.g. FLOW_COEFF_SURF[0] is not longer reported as ignored
hist output filed but all values for these in the history file are zero.
Not sure why tbh

CConfig checks whether the DV_MARKERs appear in the marker list. But for multizone
cases it can happen, that the marker to be deformed are just in the zonal configs.
The check would fail although everything is alright.
To check it right one would need to check this after all zonal cfgs were read and then
check it once with a loop over all cfgs to see whether DV_MARKER appears somewhere there.

In multizone everything is done again + attaching the zone indices. So one
had to do the AddHistPerSurf and SetHistPerSurf for multizone again.

TobiKattmann changed the title ~~Streamwise Periodic restarts using flow.meta~~ Streamwise Periodic restarts using flow.meta + Multizone PerSurface output

Feb 1, 2022

When using WALL_TIME as the first SCREEN_OUTPUT field, in Testcase.py,
the code would never reach the iter_missing=True block as the line would
produce a ValueError for every line. And because the default was
iter_missing=False and passed=True ... the test reports passed.
Setting the defaults to the non-passed version fixes that issue.

….. which I believe is not clever programming, especially for regression tests.

Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>

Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>

Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>

This is due to the previously merged PR #1530 where an NDIME error in the mesh was fixed (where the reg test values already changed) and as this PR makes the same case a restarted one... the values have to be adapted again