Closed benegee closed 4 months ago
This checklist is meant to assist creators of PRs (to let them know what reviewers will typically look for) and reviewers (to guide them in a structured review process). Items do not need to be checked explicitly for a PR to be eligible for merging.
NEWS.md
.Created with :heart: by the Trixi.jl community.
Would we want to have such checks? What is our policy in regard to user assistance?
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 96.30%. Comparing base (
4bf61a0
) to head (607c70a
). Report is 3 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Would we want to have such checks? What is our policy in regard to user assistance?
I would be fine having such a check. Right now, we just check that the dimensions fit
What about the other core devs, e.g., @trixi-framework/principal-developers?
Intuitively, I am not a big fan. One would have to add mesh-specific checks to the semidiscretization, which I don't think is good practice regarding modularity and extensibility.
Good point.
I was misled by a comment in basis_lobatto_legendre.jl, thinking
polydeg = 0
would be an exceptional but valid setting. It however only works with TreeMesh. See https://github.com/trixi-framework/Trixi.jl/pull/1489So I extended the comment.
Would there be an easy way to catch such a setting early and warn users?