-
-
Notifications
You must be signed in to change notification settings - Fork 397
Wrap up GasKinetics #1101
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
Wrap up GasKinetics #1101
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1101 +/- ##
==========================================
+ Coverage 73.63% 73.73% +0.10%
==========================================
Files 366 370 +4
Lines 48373 48927 +554
==========================================
+ Hits 35619 36077 +458
- Misses 12754 12850 +96
Continue to review full report at Codecov.
|
dd6d7ab to
006c24a
Compare
dda597f to
ed91060
Compare
87e3185 to
1987326
Compare
5deeade to
b16128e
Compare
speth
left a comment
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 for the updates, @ischoegl. Assuming the latest round of tests pass, I think this is ready to merge.
|
🎉 ... I just ran a test with stock ubuntu plus the cython pre-release, which is an environment I can reproduce locally. However, this failed also, and created an additional failure (!). So I'll drop 0de6bee ... |
For flame simulations that don't use the 'eField' solution component, replace the default solution bounds which require this component to remain exactly zero with arbitrarily wide bounds. Small rounding errors can occasionally cause the solver to want to have this component take on a small nonzero value, which could not be satisfied for any step size, resulting in solver failure.
8d05d42 to
ab8fd9f
Compare
|
@speth ... looks like we ended up pushing attempts to fix at the same time; mine definitely didn't work and may have compromised your fix. Dropped my commit and force-pushed, so we should be back to what you tested locally. Crossing fingers that this may finally work. Btw, I truly appreciate you investigating this 'interesting' failure! |
|
@speth ... too bad - CI still fails. I recompiled on my local ubuntu 20.04+latest cython docker image, and still get: which is the exact same setup that I just tried on GH actions (with resulted in two failures). Running on a 10th gen i7 here; have a Xeon on my desktop, which I can try tomorrow. How were you able to reproduce locally? PS: to recap when this started … the first time I saw this failure was when I rebased and adopted your proposed changes (which I pushed at the same time). It’s really hard to pinpoint, as it could have been introduced by any of 70+ commits. |
|
Whoops, look like only tested with my partial extract of the failing test, not with the full test suite. I think my fix did resolve the original problem, which was leading to a 1D solver failure after taking too many timesteps. The error now is different: Is there an issue with the new |
|
This indeed looks like something that would have been introduced by #1133. |
e34aec2 to
11b30ac
Compare
|
@speth ... this helps! Yup, there was a pretty obvious glitch in Thanks for locating the relevant error! So ... this may be ready! |
11b30ac to
1905f96
Compare
Previous implementation assumed number format with four letter exponent blocks; this fix ensures that formatting is correct for very small/large numbers that use five letter exponent blocks (e.g. 'e+100')
1905f96 to
3a662b3
Compare
|
Force-pushed an update that should have less of an impact on performance, while still fixing the glitch in |
speth
left a comment
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.
Looks good to me. Time to merge!
|
🎉
… On Dec 2, 2021, at 10:40 AM, Ray Speth ***@***.***> wrote:
@speth approved this pull request.
Looks good to me. Time to merge!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#1101 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABEC7PEEGDD2JZO7DRDZE23UO6VRVANCNFSM5EINUFJQ>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
Thanks, @speth for your patience in reviewing as well as the assistance in tracking some of the failures down. Much appreciated! |
Changes proposed in this pull request
BlowersMaselReaction3(and associatedBlowersMaselRate) to new frameworkFalloffReaction3and associated reaction rate handlers for pre-existingFalloff,Troe,SRI, andTsangArrhenius.hheader that collects reaction rates forArrhenius3,BlowersMasel3and potential future additions (e.g.ElectronTemperaturein electron-temperature reaction #1099) in analogy toFalloff.h.Unitswith rate objects)ReactionDatamore flexible by providingKineticsreferences toupdatemethodsThirdBodyandThirdbodyCalcChemicallyActivatedReactionare treated as a special case ofFalloffReaction3New
FalloffReaction3and associated rate objects bypassFalloffFactory.handFalloffMgr, which at this point are only used by legacy implementations.If applicable, fill in the issue number this pull request is fixing
Addresses Cantera/enhancements#87
If applicable, provide an example illustrating new features this pull request is introducing
A simple benchmark for YAML (new framework) vs XML (legacy objects) implies a slight overall speedup:
(for comparison, the current
mainshows YAML tests about 1% faster)Checklist
scons build&scons test) and unit tests address code coverage