Repository navigation
Forward rigid connectors to quasi-static mechanics - #11
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Correct boundary-condition dispatch for the staggered
quasi_staticroute byforwarding active rotation-free rigid connectors to
QuasiStaticSolver.solve.The solver already accepts this argument and implements reduced mechanics.
The explicit and legacy staggered routes already forward their connectors.
The previous call supplied the master Dirichlet values but omitted the slave
constraints. A six-node, four-element elastic regression detects the omission.
The corrected call recovers the connector-constrained solution and preserves
ordinary non-connector mechanics and the existing nonconvergence guard.
The contribution lane is solver boundary-condition dispatch. The implementation
was checked against
BoundaryConditions,QuasiStaticSolver.solve, thestaggered dispatcher and the holed-plate configuration. Capability documentation
and the changelog describe the narrow validation scope.
Verification
then all six pass with the argument forwarded.
an analytical reaction, moment balance, direct-solver agreement and the
unchanged non-connector route.
python -m pytest -q testspython -m phast run examples/quasistatic/notched_holed_plate/config.yaml --validate-onlysphinx-build -W -b html docs <external-output-directory>git diff --checkOn the old dispatcher, the small elastic case produces a maximum slave
displacement difference of 0.004 against the connector-constrained solution
under a prescribed master displacement of 0.01. This is a bounded regression,
not a newly executed full fracture benchmark.
Scope
The holed-plate example remains on
quasi_static_legacy. Damage convergencecriteria, solver defaults, constitutive kernels, example inputs and historical
results are unchanged. Full nonlinear Q2 trajectories and accelerator checks
are outside this CPU elastic dispatch correction and were not run.