-
-
Notifications
You must be signed in to change notification settings - Fork 361
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
Introduce unstrained-flow for BurnerFlame #1477
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1477 +/- ##
==========================================
- Coverage 70.05% 70.05% -0.01%
==========================================
Files 377 377
Lines 57773 57787 +14
Branches 19406 19410 +4
==========================================
+ Hits 40473 40481 +8
- Misses 14739 14745 +6
Partials 2561 2561
... and 2 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
ce76171
to
dc0bdb1
Compare
@speth ... thanks for the suggestion. I updated accordingly. |
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.
Thanks, @ischoegl. This looks good to me.
Changes proposed in this pull request
Prior to this PR,
BurnerFlame
used anAxisymmetricFlow
domain, despitespread_rate
andlambda
not being used.unstrained-flow
domainspread_rate
andlambda
are deactivated in outputIf applicable, fill in the issue number this pull request is fixing
Resolves Cantera/enhancements#171
If applicable, provide an example illustrating new features this pull request is introducing
where
spread_rate
andlambda
do not add information.Checklist
scons build
&scons test
) and unit tests address code coverage