We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mfem/mfem#3598 introduced a new class DGHyperbolicConservationLaws and refactored ex18.cpp and ex18p.cpp.
DGHyperbolicConservationLaws
ex18.cpp
ex18p.cpp
The new implementation leads to ex18.py failing; the solutions are very similar but different enough to not pass. For example
ex18.py
GetMaxCharSpeed
t=2.0
I'll start branch to wrap the new hyperbolic conservation class and update ex18
The text was updated successfully, but these errors were encountered:
https://github.com/mfem/PyMFEM/tree/fix-ex18
Sorry, something went wrong.
@justinlaughlin I started from fix-ex18 and rebased it use mfem_47_dev as a base. https://github.com/mfem/PyMFEM/tree/fix-ex18-v2 I added hyperbolic.i for serial and parallel (build passed, not used yet from ex18).
I will take a look at ex18
Closing this.
No branches or pull requests
mfem/mfem#3598 introduced a new class
DGHyperbolicConservationLaws
and refactoredex18.cpp
andex18p.cpp
.The new implementation leads to
ex18.py
failing; the solutions are very similar but different enough to not pass. For exampleGetMaxCharSpeed
result in 435 time-steps to reacht=2.0
rather than 437.I'll start branch to wrap the new hyperbolic conservation class and update ex18
The text was updated successfully, but these errors were encountered: