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

Disable neutral transport #13

Open
wants to merge 22 commits into
base: master
Choose a base branch
from
Open

Conversation

mikekryjak
Copy link
Owner

@mikekryjak mikekryjak commented Aug 23, 2024

Using this as the base:

Adding flags to suppress transport in one of the directions to aid in the investigation

bendudson and others added 22 commits March 1, 2024 19:34
Apply limiter/upwinding to both X and Y advection
Seems to work better for neutral perpendicular diffusion than MC.
Take field (Nn, Pn, NVn) and Dnn separately; only upwind the field,
and use cell face average values for Dnn.

Also add neutral_conduction switch.
target settings used in SOL and PFR regions, rather than SOL and PFR
settings.
Seems to help with smoothness of profiles
Same as anomalous_diffusion, obtain flows in X and Y for output
when diagnose = true.

Note: Only saves perpendicular flux, not parallel flux.
- For debugging purposes
- added setting for pressure floor. Added temporary debug flags for using floored Nn and Pn in DnnNn and DnnPn calculation (otherwise they could unbalance and lead to density loss - need more testing). There is a secondary floor which kicks in at zero gradient, this is now linked to the primary floor (but 2 orders of magnitude below).
- Seems to make energy imbalance less imbalanced, but I haven't gone through the maths yet
Upwinding and limiting with MC/MinMod are causing checkerboarding and/or crashes in the neutral_mixed example and provide seemingly no benefit in production runs. Reverting to original operator but with added flow diagnostics. Left warnings on the other operators, maybe we'll get back to them at some point.
Upwinding and limiting with MC/MinMod are causing checkerboarding and/or crashes in the neutral_mixed example and provide seemingly no benefit in production runs. Reverting to original operator but with added flow diagnostics. Left warnings on the other operators, maybe we'll get back to them at some point.

Squashed with commit to update operator choice.
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