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

Spitzer tests #227

Merged
merged 36 commits into from
Jul 10, 2024
Merged

Spitzer tests #227

merged 36 commits into from
Jul 10, 2024

Conversation

mrhardman
Copy link
Collaborator

PR to enable tests where vpa and vperp advection routines are used alongside collision operators.

Intended to provide fair tests of the pseudo-spectral and finite-element numerical methods and determine what boundary conditions are required for vperp advection, if any.

mrhardman and others added 30 commits May 21, 2024 14:48
…ly differ by retained example by resolution parameters, and can thus be easily regenerated.
…ns) and 1D3V(neutrals) test with a simple sheath model for electrons.
…r a 2D2V/2D3V simulation with Boltzmann electrons, ions and neutrals and wall boundary condions.
mrhardman added 6 commits July 8, 2024 12:34
…rms in vpa and vperp, for testing of the compatibility of the pseudospectral and the finite-element methods for advection and collisons, respectively. The option is chosen by selecting the [geometry] option = "0D-Spitzer-test", and picking fixed constant values of Ez, dBdr, Er, and dBdr. The vperp_advection!() routine must update the z_advect and r_advect structs if nr == 1 and nz == 1 and the "0D-Spitzer-test" option is being used, leading to some duplication of code. This could be avoided if the speed updates happened outside the function where the advection terms are computed.
@mrhardman mrhardman self-assigned this Jul 8, 2024
@mrhardman mrhardman merged commit 72bd649 into fokker-planck-vperp-bc-experiment Jul 10, 2024
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants