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

Enhance lxcat2yaml.py by adding an option to obtain elastic collision cross sections from effective cross sections #207

Open
BangShiuh opened this issue Jul 26, 2024 · 0 comments
Labels
feature-request New feature request

Comments

@BangShiuh
Copy link

Abstract

lxcat data uses different system to account for the elastic collision. The first one is to use directly the elastic collision cross section. The second one is to use the effective collision cross section. The effective cross section is the total cross section which includes elastic and inelastic cross sections. The elastic cross section can be obtained by substracting the inelastic cross section from the effective cross section. Since the electron energy levels can be different for the effective cross section and the inelastic cross section, the inelastic cross section needs to be interpolated forst onto the electron energy grid of the effective cross section.

Motivation

Make Cantera compatible to both using effective and elastic cross section data systems.

  • What problem is it trying to solve?
    Enhance to current feature for ease of use.
  • Who is affected by the change?
    Only the plasma simulation workflow
  • Why is this a good solution?
    This enhancement allows Cantera to use both elastic and effective cross section data without needing to identify "elastic" and "effective" for the electron collision plasma reactions.

Possible Solutions

As described above, we need to add the parsing code to obtain the elastic cross section from an effective cross section.

References

Links to related Pull Requests, GitHub Issues, Users' Group topics, or other relevant material.

@BangShiuh BangShiuh added the feature-request New feature request label Jul 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature request
Projects
None yet
Development

No branches or pull requests

1 participant