Conversation
c9f60bf to
dc3b60d
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1262 +/- ##
==========================================
- Coverage 72.78% 72.76% -0.02%
==========================================
Files 375 378 +3
Lines 56679 56986 +307
Branches 20607 20691 +84
==========================================
+ Hits 41255 41468 +213
- Misses 12400 12463 +63
- Partials 3024 3055 +31 ☔ View full report in Codecov by Sentry. |
dc3b60d to
c31311b
Compare
c31311b to
c4c20ec
Compare
85996ae to
a66b265
Compare
a66b265 to
e3edbef
Compare
|
@speth @bryanwweber I made a file lxcatml2yaml.py, which is used similarly to ctml2yaml. Do you know how to make a list in yaml compact?
|
This is what's know as "flow" style in YAML. Here's how it's done in cantera/interfaces/cython/cantera/ck2yaml.py Lines 90 to 98 in c0ae563 |
e3edbef to
7261d2b
Compare
|
I tried run and debug in vs code. |
7261d2b to
a693a0c
Compare
From the command line, it is definitely possible to run a single test. After executing where the You can also add the |
a693a0c to
705cc7e
Compare
f2af2dd to
877a8db
Compare
|
Almost finish. I will add the test for lxcatml2yaml. |
6082cf1 to
d7138e8
Compare
|
@BangShiuh thank you for the reminder. Could you rebase to the most recent |
|
@ischoegl I did it already but the PR information here is not up-to-date. Should I reopen a PR to fix this issue? |
I had an issue like this just the other day (apparently a glitch in GH). You may be able to fix it by introducing a minor change in one of the commits (example: edit a docstring) and force-push again. |
6a0a6f7 to
7122157
Compare
7122157 to
2c47bd7
Compare
d39019a to
e76ccb1
Compare
|
@speth I have fixed most of the issues. The flag |
speth
left a comment
There was a problem hiding this comment.
Thanks for the continued work on this, @BangShiuh. Overall, I think this is looking really good. A lot of my comments here are just minor issues with spelling / formatting. Probably the two biggest points are
- How this rate type should interact with the automatic third body identification / handling, where I'd like to get @ischoegl's opinion as well
- To see if we can make the example using this feature more physically relevant, and if it's not straightforward to do so in this PR, to document in an enhancement issue the path toward doing so.
e76ccb1 to
6689073
Compare
|
@speth I have addressed most of the issues. The new commit "fix setContext check for reactants" might be the fix. |
|
Many plasma physicists around here are computing close to fully-ionized plasma ; where the electron density cannot be considered negligible compared to the total concentration. @BangShiuh @speth if you're making this assumption ensure a warning or an error is raised if electron density is (for instance) >0.1% of total density. |
My fix works for a yaml reaction initiation, but fails for the initiation without kin object. |
3c3348b to
3c8ead6
Compare
|
@speth take a look and let me know if this fix for the third body issue is fine. |
3c8ead6 to
7ae7339
Compare
8757197 to
2bb61d6
Compare
2bb61d6 to
c9c2f93
Compare
speth
left a comment
There was a problem hiding this comment.
Thanks, @BangShiuh. I modified the last commit to avoid needing to modify the function signature of Reaction::setEquation, which would have been a breaking API change. Otherwise, I think we're good to go. Thanks for your continued work on this!
This PR accomplishes using LXCat data to calculate electron collision reaction rate.
If applicable, fill in the issue number this pull request is fixing
Cantera/enhancements#127
If applicable, provide an example illustrating new features this pull request is introducing
https://github.com/BangShiuh/cantera-examples/blob/main/plasma/plasma.py
Checklist
scons build&scons test) and unit tests address code coverage