-
Notifications
You must be signed in to change notification settings - Fork 189
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
Allow random hp AMR for testing #5781
Conversation
d105fa9
to
3f207ea
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.
you can squash your changes
static double upper_bound() { return 1.0; } | ||
"Possible refinement types and their probability, specified as integer " | ||
"weights. For example, set 'Split: 1' and 'DoNothing: 4' to split each " | ||
"element with 25% probability. The refinement is evaluated in each " |
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.
25 -> 20 (total weight is 5) (or change 4 -> 3 for DoNothing)
* \note This criterion is primarily useful for testing the mechanics of | ||
* h-refinement | ||
* You can specify a probability for each possible `amr::Flag`. It is evaluated | ||
* in each dimension separately. |
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.
mention here (or the option help) that:
- probability for a flag is its weight over sum of weights
- you do not need to specify flags with weight 0
- if all weights are 0, DoNothing is always chosen
Support triggering any of the AMR flags with a specified probability, rather than only h-refinement. Simplifies the reasoning of the AMR criterion and gives more control over the types of refinement. Still enforces a maximum refinement level, which can be deleted once it's enforced globally with an AMR policy.
Done, thanks for reviewing. |
Support triggering any of the AMR flags with a specified probability, rather than only h-refinement. Simplifies the reasoning of the AMR criterion and gives more control over the types of refinement. Still enforces a maximum refinement level, which can be deleted once it's enforced globally with an AMR policy.
Proposed changes
Upgrade instructions
Code review checklist
make doc
to generate the documentation locally intoBUILD_DIR/docs/html
.Then open
index.html
.code review guide.
bugfix
ornew feature
if appropriate.Further comments