binaryChargeExchange

Works with VSimPD license.

Kind of MonteCarlo interaction that models the charge exchange of two particles of the same atomic element.

Note

This feature replaces the chargeExchange feature, which was previously implemented in the Vorpal Collision feature.

Note

Caution should be exercised when using binaryChargeExchange reactions in the Monte Carlo framework with variable-weight species kinds; the results may be unreliable. Consider using the newer Reactions framework instead.

binaryChargeExchange Parameters

crossSection (string)

Cross section to be used in the interaction. Possible values are builtIn or functionDefined. See below for required parameters for each choice.

inSpeciesA (string)

Name of the first input species participating in the charge exchange interaction.

inSpeciesB (string)

Name of the second input species participating in the charge exchange interaction.

outSpeciesA (string)

Name of the output species resulting from particle inSpeciesA exchanging charge with inSpeciesB.

outSpeciesB (string)

Name of the output species resulting from particle inSpeciesB exchanging charge with inSpeciesA.

builtIn Parameters

Please see Types of collisions for the available builtIn gases.

The builtIn option is based on the semi-empirical formula from [LS05] for all gas types except Xe and Ar. For Xe and Ar background neutral gases the builtIn cross section data is used from the data found in experiments by [MPL+02].

If the builtIn cross section type is used the following parameters must be set:

inSpeciesAtomicWeight (real)

Atomic weight of the incident species.

inSpeciesName (string)

Name of the element of the incident species.

functionDefined Parameters

If the functionDefined cross section type is used, the following parameters must be set:

OAFunc (block, required)

An OAFunc block of name crossSectionFunc must be used inside the Interaction block. The OAFunc block allows the user to define its own cross section for the interaction, either through a two-column data file or through an expression. The kinds of OAFunc available for this interaction are interpolatedFromFile, LXcatFile, or expression. The OAFunc must return the value of the cross section in m2.

Please see OAFunc Block for more information on the OAFunc block.

crossSectionVariable (string, optional, default = velocity)

Used in the case when an OAFunc function is given for the cross section to specify whether the parameter of the function is either the:

  • relative collision velocity magnitude of the incident particle in m-1: crossSectionVariable = velocity

  • kinetic energy of the incident particle in eV: crossSectionVariable = energy

Example binaryChargeExchange Block

<Interaction chargeXchange>
  kind = binaryChargeExchange
  inSpeciesA = oxygen0
  inSpeciesB = oxygen1
  outSpeciesA = oxygen1
  outSpeciesB = oxygen0
  inSpeciesAtomicWeight = 16.0
  speciesName = oxygen
  crossSection = builtIn
</Interaction>