Skip to content

Cleanup/separate experimental code

Dennis Gläser requested to merge cleanup/separate-experimental-code into master

What this MR does / why does DuMux need it:

Moves all experimental classes/header into a subfolder experimental which mimicks the dumux folder structure. This avoids confusion between experimental and non-experimental headers and also separates testing of experimental features.

Before you request a review from someone, make sure to revise the following points:

  • does the new code follow the style guide?
  • do the test pipelines pass? (see guide on how to run pipelines for a merge request)
  • is the code you changed and/or the new code you wrote covered in the test suite? (if not, extend the existing tests or write new ones)
  • does your change affect public interfaces or behavior, or, does it introduce a new feature? If so, document the change in
  • is the list of the header includes complete? ("include what you use")
  • all files have to end with a \n character. Make sure there is no \ No newline at end of file comment in "Changes" of this MR.
Edited by Timo Koch

Merge request reports