Repository navigation
Avoid shared default control points in mat foundations - #368
Open
Tonylo-lab wants to merge 1 commit into
Open
Tonylo-lab wants to merge 1 commit into
Tonylo-lab wants to merge 1 commit into
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.
FEModel3D.add_mat_foundation()uses shared mutable defaults forx_controlandy_control. Adding a point load to one mat appends control points that affect unrelated mats, including mats in separate models. In a minimal example, a second 2x3 mat with mesh_size=1 and no requested control points generates 12 elements instead of 6 after a load at [1.5, 2.5] is added to the first mat.Use
Nonedefaults, matching the underlyingMatFoundationconstructor, so each mat receives its own control lists. Add four parameterized cases to the existing mesh tests (same/separate models and omitted/explicit controls), checking actual node coordinates and element counts, plus one short changelog entry.Validation on Windows (Python 3.12.15, NumPy 2.5.5, SciPy 1.18.1):
pytest Testing/test_meshes.py Testing/test_needs_update_flag.py Testing/test_analysis_regeneration.py Testing/test_loads.py -q: 27 passed, 2 subtests passed.git diff --check: passed.Not run: the full test suite, graphical visualization validation, or tests on other platforms/Python versions.
AI assistance: OpenAI Codex assisted with investigation, the patch, and the regression tests. The concrete diff was presented for approval before submission, and the targeted checks above were run locally.