Closed jonwzheng closed 9 months ago
⚠️ One or more regression tests failed. Please download the failed results and run the tests locally or check the log to see why.
beep boop this comment was written by a bot :robot:
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (
f9246f9
) 55.14% compared to head (c0ea448
) 55.16%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Re-running CI in the hope that the failures were spurious Julia dependency stuff.
Branch was outdated - rebased.
@jonwzheng I think there is just a simple formatting error in this table: https://github.com/ReactionMechanismGenerator/RMG-Py/actions/runs/7932965819/job/21660635035?pr=2612#step:9:335
@jonwzheng I think there is just a simple formatting error in this table: https://github.com/ReactionMechanismGenerator/RMG-Py/actions/runs/7932965819/job/21660635035?pr=2612#step:9:335
fixed this in the latest commit!
⚠️ One or more regression tests failed. Please download the failed results and run the tests locally or check the log to see why.
beep boop this comment was written by a bot :robot:
@jonwzheng could you check the live docs pages online and see if the changes here are reflected there?
Ugh, the latest doc building action fixes still aren't working. @jonwzheng could you put another pair of eyes on this workflow file and tell me if you see what is wrong? https://github.com/ReactionMechanismGenerator/RMG-Py/blob/main/.github/workflows/docs.yml
Here is the workflow run from merging this PR, it seems like the building worked but then the push failed?? https://github.com/ReactionMechanismGenerator/RMG-Py/actions/runs/7935329144/job/21668223608
I'm looking into this and it looks like documentation build workflow has had this issue as early as last week: see this for example.
Yeah, it looks like it's something specifically with the push step even though the build works. I'm not too familiar with how the workflow automation works, so I don't see anything that strikes me as particularly wrong.
The error nothing to commit, working tree clean
is really weird. Is there any chance that the /build/html
in the Publish documentation
action is different from the build/html/
compiled during Make documentation - to publish
? I'm not sure how else to explain that there's nothing to commit unless we're operating in the original (rather than re-created) directory.
I think there could be a difference between documentation/build/html
and build/html
?
Seem to be doing the git actions (checking out, committing, etc.) in the latter, but building the documentation in the former?
Could add some path printing stuff to debug, or could try something like https://github.com/mxschmitt/action-tmate to poke around and see what's happening.
Motivation or Problem
See #2605. We have decided to remove group additivity as a valid estimator for kinetics. Now, only rate rules will be supported moving forward. A previous commit (9f293bec90a093cf23b42089bb7bb0b14e05a2a7) removed the main group additivity estimator methods. However, there were still a few references to kinetic group additivity, including as the default method for
get_kinetics
ifkinetics_estimator
is not provided. There were also some mentions in the documentation and docstrings that suggest group additivity is supported.Description of Changes
This PR removes most mentions of kinetic group additivity from the code, documentation, and docstrings.
However, this commit does not remove the
KineticsGroup
class (seermgpy/data/kinetics/groups.py
), which is used extensively in the definition of aKineticsFamily
. I would welcome some discussion on whether we should remove those and rewrite the kinetics family code as well, or if we want to keep it for compatibility / future reference/use etc.Testing
A local version of RMG-website using this commit hash seems to return the same kinetics as is currently returned on RMG-Py.