Closed hajdik closed 1 year ago
Merging #193 (9e7bf7c) into main (52ebeaf) will decrease coverage by
0.09%
. The diff coverage is0.00%
.
@@ Coverage Diff @@
## main #193 +/- ##
==========================================
- Coverage 64.87% 64.78% -0.09%
==========================================
Files 47 47
Lines 11953 11969 +16
==========================================
Hits 7754 7754
- Misses 4199 4215 +16
Impacted Files | Coverage Δ | |
---|---|---|
pygeo/mphys/mphys_dvgeo.py | 0.00% <0.00%> (ø) |
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more
Lucas is testing this with his case, don't merge until we double check that it's good there.
I added other functions I've been needing in MPhys to this PR and updated the info. Lucas said local shape variables have been working for him so I think everything is good to go.
This PR is still ready for review and now has docstrings, by popular demand.
From today's maintenance meeting, we decided to remove methods from the MPhys wrapper that do not add input / outputs for OpenMDAO (with the exception of adding a reference axis). Instead, we should add a method that just returns the DVGeo object so the user can directly interface with the underlying object methods.
From today's maintenance meeting, we decided to remove methods from the MPhys wrapper that do not add input / outputs for OpenMDAO (with the exception of adding a reference axis). Instead, we should add a method that just returns the DVGeo object so the user can directly interface with the underlying object methods.
These changes have been addressed.
Purpose
Adding addLocalSectionDVs to the MPhys wrapper and adding ways to return the geometry component's DVCon and DVGeo (or child DVGeo) objects so the user can use each class's methods directly
Expected time until merged
2 months
Type of change
Testing
soon
Checklist
flake8
andblack
to make sure the Python code adheres to PEP-8 and is consistently formattedfprettify
or C/C++ code withclang-format
as applicable