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

CollisionIntegral class to support transport/chemistry #154

Open
dreamer2368 opened this issue Jul 6, 2022 · 0 comments
Open

CollisionIntegral class to support transport/chemistry #154

dreamer2368 opened this issue Jul 6, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@dreamer2368
Copy link
Contributor

Currently, collision integrals are implemented within ArgonMixtureTransport. This supports the basic capabilities for the main simulation, though eventually it needs to be separated from a specific transport class and support more functionalities. Specific points are:

  • Need a CollisionIntegral class that is independent of a specific TransportProperties
  • The species pair of a collision integral is determined with the ground states of the pair. It must be possible for users to specify a list of these ground-state-species. Currently, this is specified as ArgonSpcs, limited to argon plasma only.
  • With user-specified ground-state-species list, it will be infeasible to use a compile-time-constant enumeration to specify all collision types. Currently these are identified with ArgonColl. Eventually, with N ground-state-species, we need an array of function pointers of size [(3 + 5) * N * N], each of which computes a collision integral. This will of course require a significant implementation on parsing.
  • Currently, collision integrals are computed through a sort of built-in, hard-coded functions. In order to support uncertainty propagation, at least it must be possible to read a table and fit it into a formatted function.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant