Open pcarruscag opened 2 years ago
Now we have a regression script dedicated to the V&V examples see #1538 I have added a high-lift case to the website (here, and here). I think that to avoid the issue of outdated files in V&V repo, the best strategy is to add only meshes and documentation to the V&V repo (without duplicating the website). Then anything needed to run the case should be put under regression (via the TestCases and SU2 repos as usual). If the meshes are too large for GitHub, and are not publicly available elsewhere, we can use the SU2 Foundation Google drive. The config files can be forced to remain updated by running them in --dry_run mode in the V&V regressions.
So I think the next steps would be:
So if you have ever done any V&V of an SU2 feature not covered yet please consider adding the data to the V&V repo, the results to the website, and creating a minimal regression test for it. If you have never done any V&V, please consider reviving one of the existing ones.
[WIP]
Because we can only pin up to 3 issues in GitHub, I'm creating this one to track major aspects we need to fix or implement in SU2. This issue shall only contain the list and a brief description, with links to associated issues and pull requests. To propose major issues / development areas please use discussion #1486
The purpose of this list is two fold:
To be clear, all contributions are welcome, even if they do not fit in one of the categories below. The main objective here is consolidation, making SU2 do more things well (v&v'd, unit-tested, documented, etc.)
Documentation
update/simplify the info in these pages(done), etc.).Turbulence models
Validation and Verification
Testing and test cases
Code maintenance
Robust convergence
Customization
Optimization
Completely new development areas