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:
Remove CTI/XML support first, while retaining legacy- reaction implementations (which can still be instantiated from YAML) … see Cantera/cantera#1291
Remove legacy Kinetics handlers second … see Cantera/cantera#1292
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 Cantera/cantera#1291Kineticshandlers second … see Cantera/cantera#1292References
New in Cantera 2.6:
63
87
139
Work deferred to Cantera 3.0:
142