Update nonlinear channel flow benchmark #6164
Open
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.
This is a follow-up PR that is based on #6159. I here also rework the nonlinear channel flow benchmark. I still need to check some tests, but one thing I already noticed is: If I change the boundary traction value or the boundary velocity value the solver converge much better than with the values they are set to know. I kept the values the same to reproduce the figure like they are in the original paper, but I wanted to record this somewhere. It is curious how the traction benchmark stagnates at a constant nonlinear solver tolerance, even for models that use the standard Picard solver (therefore it is not related to the Newton solver or the defect correction solver).