fix: Issue with parallel pyMechanical instance on linux#1654
Conversation
…allel instances of pyMechanical and fix frequent memory issues during Mechanical startup
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Coverage variation | ✅ +0.00% coverage variation (-1.00%) |
| Diff coverage | ✅ ∅ diff coverage |
Coverage variation details
Coverable lines Covered lines Coverage Common ancestor commit (5c3559d) 3321 2680 80.70% Head commit (e5069be) 3321 (+0) 2680 (+0) 80.70% (+0.00%) Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch:
<coverage of head commit> - <coverage of common ancestor commit>
Diff coverage details
Coverable lines Covered lines Diff coverage Pull request (#1654) 0 0 ∅ (not applicable) Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified:
<covered lines added or modified>/<coverable lines added or modified> * 100%
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
|
The documentation for this pull request will be available at https://mechanical.docs.pyansys.com/pull/1654. Please allow some time for the documentation to be deployed. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1654 +/- ##
=======================================
Coverage 80.69% 80.69%
=======================================
Files 43 43
Lines 3321 3321
=======================================
Hits 2680 2680
Misses 641 641 🚀 New features to boost your workflow:
|
|
This PR has been closed. Documentation for this pull request will shortly be removed from its former deployment address. |
Summary
Fixes issues seen in workflows where numerous pyMechanical instances are started in parallel at the same time and exceptions or crashes are seen when Mechanical is starting.
Fixes #1653
Changes
-
MWSUB_SPACEenvironment variable added before Mechanical starts. It needs to be a unique alpha-numeric value which will be assigned to each new instance of pyMechanical that starts. This is a mainwin variable that will assign a sub-space of memory for each Mechanical instance started through pyMechanical. It can be disabled throughMWSUB_SPACE_OFF=1variable.Visual of the change:

Type of change
Checklist
feat: add modal analysis support)