ForceFreeStates - FEATURE - Widen the harmonic range at startup when the forcing spectrum needs it

Abierto
#563 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
julia

Línea de trabajo

Start by locating the ForceFreeStates setup and the forcing materialization paths for file forcing and coil Biot–Savart; the issue does not name files or tests. Read how the current harmonic bounds and edge-harmonic flux check are calculated, then trace where the spectrum is used in the FFS solve and PE stage. Done when the range widens based on the stated flux criterion, reports the selected bounds, and reuses the materialized spectrum.

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

Descripción

Goal

Check the forcing spectrum at the start of a run, and widen the ForceFreeStates (FFS) poloidal harmonic range (mlow:mhigh) when it is too narrow to resolve the forcing.

Motivation

The FFS harmonic range is fixed from the q profile plus delta_mlow/delta_mhigh, before the forcing is looked at. The forcing is then projected onto that range. Any forcing flux outside it is silently dropped:

  • File forcing: normal_field_T file forcing is now projected onto the run's harmonics (see #549). The B·n̂ → flux weight spreads amplitude several harmonics beyond the file's own, so a file that reaches the edge of the run's range loses flux there.
  • Coil forcing: coil forcing is decomposed directly on mlow:mhigh and is truncated the same way.

Today the only check is the warning added in #549. It covers truncation of the file's own spectrum, not truncation by the run.

Proposal

  • Early materialization: materialize the forcing spectrum (file conversion or coil Biot–Savart) before the FFS solve, on a range wider than the default.
  • Range criterion: use the same edge-harmonic criterion as the file check. If the harmonics at or beyond the run's mlow/mhigh carry more than a set fraction of the forcing flux, widen the range until they don't. Report the chosen range with an @info.
  • Option: make the widening opt-out, or behind a deck option, since it raises mpert and the cost of the solve. A user-set range that is too narrow should at least warn.
  • Reuse: reuse the early spectrum in the perturbed-equilibrium (PE) stage rather than materializing it twice.
Lenguaje dominante
Julia
Estrellas
11
Forks
7
Merge medio
3 d 11 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.