Recipes: launch from a saved field plane, for a two-stage setup

Aperta
  • Qualcosa non va?
#536 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
backend, data

Direzione di ricerca

Start with src/solprop/processing/plane_file.py, recipe/registry.py, and recipe/provenance.py, then read the coupling and recipe guides. Draft a short proposal covering byte handling and provenance for HDF5 files, how the receiving run's input port and grid reach the launch step, and how the coupling model is selected. Done means an agreed design for representing a saved plane as a recipe launch.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: coupling area: gui enhancement priority: low

What is missing. processing.save_field_plane and load_field_plane keep a FieldPlane in a file (#456), but a recipe can't name one as its launch. So a two-stage setup can't be written as a pair of recipes.

Why it matters. A front end can export a plane and a script can launch from it, but a saved setup can't describe the second stage on its own.

What it needs.

  • A registered recipe type that loads a plane file, checked by sha256 like the other data files. build_object decodes a data file to UTF-8 text today (recipe/registry.py), so an HDF5 file needs a path for bytes. recipe/provenance.py embeds data files only up to 16 MiB, so larger planes would stay as references.
  • A step after the route is built. A launch is bound to the receiving run's input port (couple(plane, simulation.input_port(), model=...), then simulation.with_input(result.launch)), and a recipe's Factory.context offers only the grid.
  • A recipe form for the coupling model, since CouplingModel and its keywords aren't registered.

This is a design decision as much as an implementation, so it should start with a short proposal.

Context. src/solprop/processing/plane_file.py, docs/guide/workflows/coupling.md, docs/guide/setup/recipes.md. Related: #175 (general modal planes and the frame).

🤖 Generated with Claude Code

Lingua principale
Python
Stelle
3
Fork
3
Merge medio
8h 14m
PR unite (30g)
151

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di LupoLab/solprop

Tutte le issue di LupoLab/solprop

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.