Skip to content

Simplify the analytical Alfven perturbation PR - #196

Open
rogeriojorge wants to merge 10 commits into
feat/analytical-alfven-perturbationsfrom
simplify/alfven-perturbations
Open

rogeriojorge wants to merge 10 commits into
feat/analytical-alfven-perturbationsfrom
simplify/alfven-perturbations

Conversation

@rogeriojorge

@rogeriojorge rogeriojorge commented Oct 31, 2026 •

Copy link
Copy Markdown
Member

Simplify the perturbation interfaces on #177 and compare loss curves with the same launch seeds. The changes in loss fraction stayed within the reported sampling intervals.

Measurements and test conditions

Core: one Perturbation base (potentials/derivatives/axis stop) shared by the
Boozer and native classes, a single envelope(), shorter mode validation and
trace_boozer docstring. Traces are bitwise identical to before.

Examples: the two analytical/VMEC paper benchmarks, their launcher, comparison
and plotting scripts, conventions, sampling and saved reference data become one
paul_alfven_benchmark.py (Boozer and VMEC backgrounds, --historical for the 2023
conventions) plus a short alfven_perturbation.py. The physics verification
lives in the tests instead of a separate benchmark.

Tests: the Boozer, axis-stop and electromagnetic-verification files are merged
into test_perturbations.py, the VMEC map tests into test_native_gc_perturbations.py;
tests of benchmark-script plumbing are dropped.

Docs: shorter page, one figure regenerated by the benchmark script.
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