PerturbedEquilibrium - FEATURE - Emit the Lagrangian field-strength perturbation in the Boozer and Hamada field-line gauges

Abierto
  • ¿Algo no está bien?
#560 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
fortran, julia
Área
backend, databases

Línea de trabajo

Read #543 for the existing perpendicular-displacement output, #540 for the gauge contracts, and #429 for the pending choice between an on-demand helper and HDF5 datasets. The Fortran reference implementation and derivation are in GPEC#344, especially docs/pmodb_target_gauge.rst and gen/pmodb_gauge/; first check how their tests map to the Julia code. Done means Boozer and Hamada outputs are available, with tests for parallel-displacement cancellation, zero source, resonant-source rejection, and the independent Hamada-to-Boozer cross-check.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

#543 writes the perturbation that drives neoclassical transport in the perpendicular-displacement gauge (dBoB_lagrangian, div_xi_perp). NEO-2, NEO-RT and other Boozer- or Hamada-based consumers need the Lagrangian field-strength perturbation in their own field-line gauge instead. Changing the gauge adds a displacement w along the field line, which is found from the magnetic differential equation

D w = -(div xi_X + a * delta B_X / B),   a = 2 (Boozer), a = 0 (Hamada),

where angles are in turns and delta B_target = delta B_X + w * partial_theta B. Nonzero resonant sources must fail explicitly rather than being regularized silently.

The Fortran implementation, with its derivation and FortSym-generated kernels, is in GPEC#344 (docs/pmodb_target_gauge.rst, gen/pmodb_gauge/). That PR will not be merged in Fortran, because new features now go to the Julia code. Its tests should be carried over: cancellation of a parallel displacement, zero source, and resonant source rejection. A Hamada-to-Boozer cross-check is also available against an independent kernel.

Proposed scope: after #543 lands, add the gauge solve and dBoB_lagrangian_boozer / _hamada outputs, either to the on-demand helper of #429 or as new HDF5 datasets, whichever the #429 decision prefers. The gauge contracts are documented in #540.

Chris&AI

Lenguaje dominante
Julia
Estrellas
11
Forks
7
Merge medio
4 d 1 h
PR fusionados (30 d)
68

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OpenFUSIONToolkit/GPEC

Todos los issues de OpenFUSIONToolkit/GPEC

Issues similares

Más issues de Julia

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.