[Trivial] Correct documentation and usage of numlevel#1339
[Trivial] Correct documentation and usage of numlevel#1339adamdempsey90 wants to merge 2 commits intodevelopfrom
Conversation
|
@par-hermes format |
|
Thanks for the fix! |
pgrete
left a comment
There was a problem hiding this comment.
Line 1128 in 1e9a566
if (pib->block_name.compare(0, 27, "parthenon/static_refinement") == 0) {conditional leads me to believe that we are using the max level info also for static mesh refinement.
I also think that this makes from a logical point of view in cases where I want to have some regions statically refined and other adaptively.
Overall, there should be a global max level (which is the current parameter), and then there's the level for the static regions individually as well as for the adaptive criteria.
AMR + |
This might just be an artemis thing though. |
pgrete
left a comment
There was a problem hiding this comment.
Thanks for pointing out the default value for static meshes.
At some point point, allowing both SMR and AMR would be nice.
|
|
||
| <parthenon/mesh> | ||
| refinement = none | ||
| numlevel = 2 |
There was a problem hiding this comment.
AMR is done for this test case (enabled via command line parameters for some steps).
So this needs to either stay or added to the test cases with AMR in advection_convergence.py
| max_level_ref_ = | ||
| pin->GetOrAddInteger("parthenon/mesh", "numlevel", 1, | ||
| "maximum level of refinement globally when AMR is on"); |
There was a problem hiding this comment.
This change might need a rebuilt of the autogenerated parameter docs as the string changed.
PR Summary
numlevelis only read and used with AMR, but the docstring reads as if you need it with SMR. This has caused some confusion, so I'm correcting it.PR Checklist