add lower bound for rectangular doamins #749
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fractalsbyx
pushed a commit
to fractalsbyx/phaseField
that referenced
this pull request
Dec 11, 2025
fractalsbyx
pushed a commit
to fractalsbyx/phaseField
that referenced
this pull request
Dec 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Add lower bound to rectangular domains. Closes allow users to set a different lower bound than the origin for a rectangular domain #748.
What is the current behavior? (You can also link to an open issue here)
Currently, the lower bound of the domain defaults to the origin.
What is the new behavior (if this is a feature change)?
The user can now specify the lower bound of the domain, avoiding shifting equations.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No
Other information: