Skip to content

Add KIM collision-frequency scale#182

Open
krystophny wants to merge 1 commit into
feat/flux-pumping/wp5-benchmarkfrom
feat/flux-pumping/wp5-collision-scale
Open

Add KIM collision-frequency scale#182
krystophny wants to merge 1 commit into
feat/flux-pumping/wp5-benchmarkfrom
feat/flux-pumping/wp5-collision-scale

Conversation

@krystophny

@krystophny krystophny commented Jul 12, 2026

Copy link
Copy Markdown
Member

Adds a positive collision_frequency_scale to KIM configuration. It multiplies calculated electron and ion collision frequencies before the Krook argument and Fokker-Planck susceptibility inputs are assembled. The default is 1, so existing collision formulas, profiles, units, and outputs are unchanged. The configured value is displayed and stored in HDF5 provenance.

The periodized-background regression uses a scale of 3 and checks the resulting electron collision frequency against the existing Coulomb-logarithm formula.

Verification

Before: test_periodized_background_feed failed to compile because the configuration value did not exist.

After: the focused regression passes; the full CMake build and all 30 CTest tests pass; bare fo passes Static, Build, Tests, and Lint.

An initial 64-point Krook scout at omega=1e5 overflowed above scale 1. PR 183 traced that result to interpolation of the derived z0 across k_parallel=0, not to the collision-frequency scale. With z0 recomputed from interpolated primitives, scales 1 through 3 remain finite. This PR supplies a controlled sensitivity parameter; it makes no benchmark-acceptance claim.

Relation to Markus's Fokker-Planck periodic branch

This PR provides a controlled sensitivity parameter with a default-preserving implementation. It was used to diagnose the rejected Krook benchmark and is not an FP acceptance mechanism. Keep its provenance and regression independent of the periodic-FP decision in #191.

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.

1 participant