The field ionization framework that found its way into the code last year provides us with the opportunity to implement a first collisional ionization model into PIConGPU if the input parameters can be treated like fields.
In order to get closer to comparing our simulations to known results from iPICLS2D a fitted Thomas-Fermi pressure ionization model has been chosen.
Atoms in the Thomas-Fermi model consist of a core potential and an electron density. The dominating effects for ionization in the pressure ionization model are ion-ion and electron-electron collisions. Ionization potentials are being depressed due to an overlap of the core potentials while the bound electrons get kicked out of the atom by colliding with other electrons.
Ion mass density and electron temperature are the two defining input parameters of this model. It is based on the assumption that the process takes place in thermal equilibrium - which is an assumption that can never hold in a laser-matter interaction. Nevertheless it is a model that is relatively easy to implement. The model calculations result in an average charge state Z* that can be used to induce the ionization process. In order to neglect the fast electrons and only take the thermalized part a cutoff-momentum/energy is used before the temperature calculation.
For more info see
"temperature" functor that makes use of shapes and can interpolate over multiple ordersinclude/particles/particleToGrid/derivedAttributes"temperature" functorFieldTmp handle "temperature" as well as density or implement two (n?) FieldTmpsupdate 2017-04-18 the following two tasks have been relocated to issue #1967
@DrThomasKluge this might also be of interest to you
Yes, it is of interest to me. I would only soften two points from above:
Yes, renaming it and not calling it "temperature" occured to me, too. It would then be more appropriately named throughout the code and only in the place where it will be used like a "temperature" the contradiction can be explained in a comment.
Is this THE @DrThomasKluge on GitHub? In case of the renaming: I'm for it!
@bussmann, it most certainly is the one!
Yay!
@n01r can you please split out new issues in independent follow-up issues so we can close this as implemented in 0.3.0?