Vortex street validation#1223
Conversation
Co-authored-by: Niklas Neher <73897120+LasNikas@users.noreply.github.com>
Co-authored-by: Niklas Neher <73897120+LasNikas@users.noreply.github.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1223 +/- ##
=======================================
Coverage 90.04% 90.04%
=======================================
Files 136 136
Lines 10595 10595
=======================================
Hits 9540 9540
Misses 1055 1055
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@LasNikas @svchb I'm unsure how to validate this example from CI. The highest resolution with acceptable runtime would be 0.2. This runs in 1 minute on a large CPU, so we might be able to get it to run to t=2 in 5-10 minutes in CI, which is already longer than I'd prefer for a CI test. However, the result with this resolution looks like this: Of course, we can validate against these results to detect changes in the codebase, but I'd much prefer testing against a useful Strouhal number. |



Second part of #781. Based on #1221.
This is the plot based on the reference files, which I created by running the validation file at the default resolution of 0.05:
