Skip to main content

A set of tools for importing data from the LXCat project.

Project description

A set of tools developed at the High Voltage Lab (HVL) of ETH Zurich, for reading/writing electron scattering cross sections data, in a format compatible with the LXCat project.

Free software: GNU General Public License v3


>>> pip install lxcat_data_parser


To load an electron scattering cross section set:

>>> import lxcat_data_parser as ldp
>>> data = ldp.CrossSectionSet("N2_data.txt")

The loaded set can be modified and saved again (here the ELASTIC cross section is multiplied by 10):

>>> for cross_section in data.cross_sections:
>>>     if cross_section.type == ldp.CrossSectionTypes.ELASTIC:
>>>["cross section"] *= 10
>>> data.write("N2_data_rescaled.txt")

Cross section data format

Description of the data format taken from the LXCat project. In downloaded files, each collision process is defined by a block consisting of:

  • 1st line: Keyword in capitals indicating the type of the collision. Possible collision types are ELASTIC, EFFECTIVE, EXCITATION, IONIZATION, or ATTACHMENT (capital letters required, key words are case sensitive), where “ELASTIC” is used to denote the elastic momentum transfer cross section and where “EFFECTIVE” denotes the total momentum transfer cross section (sum of elastic momentum transfer and total inelastic cross sections). The latter is useful for solving the Boltzmann equation in the 2-term approximation.
  • 2nd line: Name of the target particle species. This name is a character string, freely chosen by the user, e.g. “Ar”. Optionally for excitation processes, the name of the corresponding excited state can be specified on the same line, separated from the first name either by arrow “->” (dash + greater than) or by double-head arrow “<->” (less than + dash + greater than), e.g. “Ar -> Ar*” and “Ar <-> Ar*”, respectively. In the later case BOLSIG+ will automatically define the inverse superelastic process, constructing the superelastic cross-section by detailed balancing, and considering the indicated excited state as the target. In this case, the ratio of statistical weights must be input in the 3rd line (see below). Alternatively, superelastic collisions could be defined explicitly as excitation collisions with a negative electron energy loss with user input cross sections and species name, “Ar*”, for example.
  • 3rd line: For elastic and effective collisions, the ratio of the electron mass to the target particle mass. For excitation or ionization collisions, the electron energy loss (nominally the threshold energy) in eV. For attachment, the 3rd line is missing. In case of an excitation process where an excited state has been indicated on the 2nd line using double-head arrow “<->”, the 3rd line must specify also ratio of the statistical weights of the final state to the initial state as the second parameter in 3rd line this is needed by BOLSIG+ to calculate the de-excitation cross-section.
  • from 4th line (optionally): User comments and reference information, maximum 100 lines. The only constraint on format is that these comment lines must not start with a number.
  • Finally: Table of the cross section as a function of energy. The table starts and ends by a line of dashes “——” (at least 5), and has otherwise two numbers per line: the energy in eV and the cross section in m2.

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Files for lxcat_data_parser, version 0.1.1
Filename, size File type Python version Upload date Hashes
Filename, size lxcat_data_parser-0.1.1-py3-none-any.whl (7.0 kB) File type Wheel Python version 3.7 Upload date Hashes View

Supported by

AWS AWS Cloud computing Datadog Datadog Monitoring Facebook / Instagram Facebook / Instagram PSF Sponsor Fastly Fastly CDN Google Google Object Storage and Download Analytics Huawei Huawei PSF Sponsor Microsoft Microsoft PSF Sponsor NVIDIA NVIDIA PSF Sponsor Pingdom Pingdom Monitoring Salesforce Salesforce PSF Sponsor Sentry Sentry Error logging StatusPage StatusPage Status page