Match mostly cosmetic differences between main and production, adds an esdg entropy-to-conserved
conversion util test to test_euler.py.
This change set trivially reduces the difference between production and main, but helps eliminate some merge conflicts in current developments (mostly Tulio's) when running production tests.
Questions for the review:
[ ] Is the scope and purpose of the PR clear?
[ ] The PR should have a description.
[ ] The PR should have a guide if needed (e.g., an ordering).
[ ] Is every top-level method and class documented? Are things that should be documented actually so?
[ ] Is the interface understandable? (I.e. can someone figure out what stuff does?) Is it well-defined?
[ ] Does the implementation do what the docstring claims?
[ ] Is everything that is implemented covered by tests?
[ ] Do you see any immediate risks or performance disadvantages with the design? Example: what do interface normals attach to?
Match mostly cosmetic differences between main and production, adds an esdg entropy-to-conserved conversion util test to
test_euler.py
.This change set trivially reduces the difference between production and main, but helps eliminate some merge conflicts in current developments (mostly Tulio's) when running production tests.
Questions for the review: