You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
legacy-
reaction implementations (which can still be instantiated from YAML) … see Remove deprecated CTI & XML formats cantera#1291Kinetics
handlers second … see Remove legacy kinetics cantera#1292References
New in Cantera 2.6:
Work deferred to Cantera 3.0:
ReactionRate
objects:Reaction
vsMultiRate
cantera#1211The text was updated successfully, but these errors were encountered: