Template Level on DomainGeometry

[EmilyBourne]

Merge Request - GuideLine Checklist

Guideline to check code before resolve WIP and approval, respectively.
As many checkboxes as possible should be ticked.

Checks by code author:

Always to be checked:

• There is at least one issue associated with the pull request.
• New code adheres with the coding guidelines
• No large data files have been added to the repository. Maximum size for files should be of the order of KB not MB. In particular avoid adding of pdf, word, or other files that cannot be change-tracked correctly by git.

If functions were changed or functionality was added:

• Tests for new functionality has been added
• A local test was succesful

If new functionality was added:

• There is appropriate documentation of your work. (use doxygen style comments)

If new third party software is used:

• Did you pay attention to its license? Please remember to add it to the wiki after successful merging.

If new mathematical methods or epidemiological terms are used:

• Are new methods referenced? Did you provide further documentation?

Checks by code reviewer(s):

• Is the code clean of development artifacts e.g., unnecessary comments, prints, ...
• The ticket goals for each associated issue are reached or problems are clearly addressed (i.e., a new issue was introduced).
• There are appropriate unit tests and they pass.
• The git history is clean and linearized for the merge request. All reviewers should squash commits and write a simple and meaningful commit message.
• Coverage report for new code is acceptable.
• No large data files have been added to the repository. Maximum size for files should be of the order of KB not MB. In particular avoid adding of pdf, word, or other files that cannot be change-tracked correctly by git.

[julianlitz]

@EmilyBourne It would be better to merge this before my large Mumps Pull request right?
The merge conflicts here are minor.
I can easily copy my Mumps PR changes in a new PR based on a new branch.

Or would it be better to start fresh from a new main branch after we merged the Mumps PR?
I could help you out to get the changes done here up and running in a newer branch version.

[EmilyBourne]

@EmilyBourne It would be better to merge this before my large Mumps Pull request right? The merge conflicts here are minor. I can easily copy my Mumps PR changes in a new PR based on a new branch.

Or would it be better to start fresh from a new main branch after we merged the Mumps PR? I could help you out to get the changes done here up and running in a newer branch version.

If possible yes. Ever PR gives me a massive number of conflicts. And there are several steps so starting afresh is not ideal