-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
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
feat(GWE): Introduce Groundwater Energy Transport #1493
feat(GWE): Introduce Groundwater Energy Transport #1493
Conversation
039b9ba
to
4601d0f
Compare
42643d6
to
f82e6fd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, @emorway-usgs. I had a bunch of really minor comments in here that could all be addressed after a merge. Have a quick look and let me know if we should merge this morning.
On a more consequential note, we should probably discuss a bit more the package naming conventions for GWE. We can do this after the merge. For example, GWE has an MST Package, but the input for the MST Package is different from the input for the GWT MST Package. I wonder if this will ultimately cause confusion. Not sure there is a right or wrong answer, but we might think about whether the FYTPE uniquely describes a package or whether package format is now uniquely defined by MODELTYPE and FTYPE.
…and MODFLOW-USGS#1493 (comment) and reran mf6ivar.py, which updated the tex files in this commit
2828acb
to
bc75370
Compare
…and MODFLOW-USGS#1493 (comment) and reran mf6ivar.py, which updated the tex files in this commit
bc75370
to
1753af2
Compare
… is the dominant process in heat transport
…al solutions from Carslaw & Jaeger (1947)
… failing as downloaded contents from its failure are working locally.
5929f30
to
34125e7
Compare
… Actions doesn't yield the same output that the logs are reporting. This particular autotest has an analytical solution (and a plot) that might be better shown on the modflow6-examples repo anyway
Perhaps there would be a way to generalize what's going on here and reduce duplication?
Let the PR fun begin...