-
-
Notifications
You must be signed in to change notification settings - Fork 346
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate Solution in oneD objects #1345
Integrate Solution in oneD objects #1345
Conversation
ff0665a
to
b4ef404
Compare
c5e0c83
to
3c9463b
Compare
3c9463b
to
0e42b69
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
81cfbd9
to
0111336
Compare
a9918c5
to
88f514a
Compare
Rebased to latest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks pretty good to me, @ischoegl. My main question is about the necessity of the StFlow::m_trans_shared
object.
88f514a
to
2957c95
Compare
@speth ... thank you for the review! |
090ed85
to
781c8c2
Compare
Transport::transportType() is not consistent with nomenclature used in the Python API, which uses Transport.transport_model.
Co-authored-by: Bryan Weber <bryan.w.weber@gmail.com>
781c8c2
to
1f34cfe
Compare
Changes proposed in this pull request
StFlow
objects fromSolution
Transport::transportModel
consistentThe PR excludes
clib/ctonedim
, whereSolution
is currently completely absent.If applicable, fill in the issue number this pull request is fixing
Preliminary work for Cantera/enhancements#137
If applicable, provide an example illustrating new features this pull request is introducing
Checklist
scons build
&scons test
) and unit tests address code coverage