Remove/deprecate legacy Solution handling#1685
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1685 +/- ##
==========================================
+ Coverage 72.76% 72.80% +0.04%
==========================================
Files 378 378
Lines 56986 56956 -30
Branches 20691 20679 -12
==========================================
+ Hits 41468 41469 +1
+ Misses 12463 12434 -29
+ Partials 3055 3053 -2 ☔ View full report in Codecov by Sentry. |
|
Ready for review ... decided to restrict this PR to Reactor cleanup that became possible after the removal of the legacy MATLAB toolbox. |
speth
left a comment
There was a problem hiding this comment.
Thanks, @ischoegl. I had a couple of thoughts on this.
Given the changes made here, can we move toward eliminating the C++ ReactorBase::setSolution and the Python ReactorBase.insert methods? With the requirement that the reactor needs contents from the beginning, I don't think there's a use case for switching them after the fact. (Not necessarily suggesting to resolve this in this PR)
a8aae47 to
a0c3f73
Compare
|
@speth - thank you for your feedback. I believe I started some confusion with a deprecation warning that incorrectly implied that something was introduced in Cantera 3.0, while only being implemented after its release (non-empty Reactors). I updated/corrected the warnings, which should take care of your concerns. Regarding changes to the reactor content after instantiation, we can definitely think about removing this capability, but either |
a0c3f73 to
3f20538
Compare
Changes proposed in this pull request
Removal of legacy MATLAB toolbox #1670 allows for some simplifications / deprecations:
setThermoMgr/setKineticsMgrfor 0DIf applicable, fill in the issue number this pull request is fixing
Partially addresses #1457
A clean resolution of #1457 will require pushing the Python
_WeakrefProxyapproach to the C++ layer?Checklist
scons build&scons test) and unit tests address code coverage