Skip to content

Add documentation to set methods for bound violation in QN acceleration#861

Open
Fujikawas wants to merge 2 commits intomasterfrom
addQNBoundDocu
Open

Add documentation to set methods for bound violation in QN acceleration#861
Fujikawas wants to merge 2 commits intomasterfrom
addQNBoundDocu

Conversation

@Fujikawas
Copy link
Copy Markdown
Member

To provide hints on using the new feature in acceleration configuration added by precice/precice#1952.

Copy link
Copy Markdown
Member

@MakisH MakisH left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The current diff looks good, I have not yet looked at the bigger picture.

@MakisH MakisH added the content Content-only issues label Mar 24, 2026
Copy link
Copy Markdown
Member

@MakisH MakisH left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The text looks good to me now. I have no idea about the feature, though, so you tell me when it's ready to merge.

* `clamp`: preCICE checks the accelerated values against the given bound(s) after a QN update step is computed. The violating values will be clamped to the bounds respectively. Non-violating values are not influenced by this check.
* `scale`: preCICE checks the accelerated values against the given bound(s) after a QN update step is computed. If any violation is found, the update from this QN step is scaled by a scalar factor between 0 and 1, to fit all the violating values into the bounded range.

While `discard` and `clamp` are convenient options for single value or occasional bound violation, `scale` helps to retain the direction of the QN step by only shortening the step length. The best option for this attribute is problem-dependent.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ad the bottom of this, a version alert would be useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

content Content-only issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants