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

Activation barrier input file (EAs.inp, EAg.inp) #13

Open
wittregr opened this issue Apr 8, 2020 · 2 comments
Open

Activation barrier input file (EAs.inp, EAg.inp) #13

wittregr opened this issue Apr 8, 2020 · 2 comments
Labels
enhancement New feature or request temporary-fix A possible alternate strategy can be used to solve this for now.

Comments

@wittregr
Copy link
Contributor

wittregr commented Apr 8, 2020

Chemkin allows for activation energies to be set for each run in a series as specified in Tflow.inp. These activation energies are usually set to allow a temperature-dependent activation energy. Therefore, a separate activation energy in the EA input file aligned with the temperature of the simulation as specified in Tflow.inp accomplishes this task. Chemkin provides two input files for this purpose; one for the surface reactions (EAs.inp) and one for the gas reactions (EAg.inp). In addition, there is a flag in tube.inp to turn on/off the use of a separate EA input file (lEA). In the EA input file EA's are specified by reaction. If the IEA flag is True then Chemkin looks for an EA in the EA input file otherwise it uses the EA specified in surf.inp or gas.inp.

@skasiraj skasiraj added enhancement New feature or request temporary-fix A possible alternate strategy can be used to solve this for now. labels Nov 1, 2021
@skasiraj
Copy link
Contributor

skasiraj commented Nov 1, 2021

@wittregr In OpenMKM we can run parametrized studies at various T,P and flow-rate (analogous to the Tflow file in Chemkin). But at this time we cannot change the parameters (such as Ea in this case) specifically for each run via a paramter in the input files. An alternate solution would be to use pMuTT to generate a unique reactor.yaml and thermo.xml, for each of these distinct cases (where the Ea is unique to the given T). You could use the omkm-python interface to do this automatically from python. Please contact me if this is something you are interested in.

@mbkumar
Copy link
Contributor

mbkumar commented Nov 1, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request temporary-fix A possible alternate strategy can be used to solve this for now.
Projects
None yet
Development

No branches or pull requests

3 participants