Skip to content
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

Remove legacy Kinetics infrastructure for Cantera 3.0 #149

Closed
ischoegl opened this issue May 1, 2022 · 0 comments · Fixed by Cantera/cantera#1292
Closed

Remove legacy Kinetics infrastructure for Cantera 3.0 #149

ischoegl opened this issue May 1, 2022 · 0 comments · Fixed by Cantera/cantera#1292
Assignees
Labels
work-in-progress An enhancement that someone is currently working on

Comments

@ischoegl
Copy link
Member

ischoegl commented May 1, 2022

Abstract

Cantera 2.6 introduces a major redesign of how reaction rates are handled internally to improve extensibility and enable new capabilities. After release of 2.6, the "legacy" kinetics infrastructure is slated for removal. At the same time, the CTI/XML input format will be removed.

With Cantera 2.6 being the last version that fully supports CTI/XML, this means that substantial amounts of legacy code will be removed for Cantera 3.0.

Possible Solutions

The following roadmap is proposed:

  1. Remove CTI/XML support first, while retaining legacy- reaction implementations (which can still be instantiated from YAML) … see Remove deprecated CTI & XML formats cantera#1291
  2. Remove legacy Kinetics handlers second … see Remove legacy kinetics cantera#1292
  3. Resume work towards Cantera 3.0

References

New in Cantera 2.6:

Work deferred to Cantera 3.0:

@ischoegl ischoegl added the feature-request New feature request label May 1, 2022
@ischoegl ischoegl self-assigned this May 1, 2022
@ischoegl ischoegl added work-in-progress An enhancement that someone is currently working on and removed feature-request New feature request labels May 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
work-in-progress An enhancement that someone is currently working on
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant