The split collar's crossing limit reads the walk-off of empty columns and bands
I maintainer di solito rispondono entro 1 giorno
Una pull request collegata è già stata integrata.
- #439 di @jtravs — integrata
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 12/100
- Tipo di issue
- Refactoring
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- numpy, python
- Ambito
- backend, performance
Direzione di ricerca
The limit is computed by solprop.translate.linop.walk_off_rate, which takes the largest walk-off over all reference-frequency columns and the requested band. Read that function, then the step-size collar in the propagation loop, and the witnesses in tests/test_transverse_reads.py. Done means radial_filament_512 and cartesian_filament_256 land within 1 % of unclamped step counts while the #149 witnesses still leave less than 1e-3 of the launch.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
What happens
#439 (for #149) holds split-collar steps to 0.5 w / max|dtau/dz|. The rate comes from the translated operator (solprop.translate.linop.walk_off_rate), not from where the light is. It takes the largest of two sets of bins: every column at the reference frequency, and the frame's column over the requested band. Because nothing in it depends on where the light is, it is conservative in three ways, each measured on an Apple M5 Max:
- Empty columns at the carrier. On
radial_filament_512andcartesian_filament_256, the outermost transverse columns' walk-off at 800 nm sets the limit, at 3.0e-4 m and 8.8e-4 m. Those columns hold little of the filament's light. Accepted steps rise from 130 to 173 and from 55 to 67. In SEP 40's tilted-packet witnesses (tests/test_transverse_reads.py) the frame follows the packet, so the empty on-axis columns walk at 4e-10 s/m against it. The limit would be 1.1e-4 m, and #439 runs those witnesses without a temporal collar instead. - The whole requested band on the frame's column. On the #149 GNLSE witness the band's bluest bin walks 6.6 times faster than the pulse does.
Multisteptakes 95 steps where about 23 at the pulse's own rate would do (#149'sdz_max = 0.074 mrow). - Evanescent columns of a tabulated operator. A separable operator's evanescent bins are passed over. A radial (tabulated) operator's are not: on a radial grid fine enough to hold an evanescent column at the reference frequency, that column reads the frame's rate, about
1/c, and the limit collapses.
Why it matters
These are step costs, not wrong answers: the limit only binds when it is stricter than the run needs. But a filament on a fine grid pays a third more steps for light that is not there.
To do
- Weigh a rate taken over where the light is, read from the launch or at the monitor's checks. Any such rate must still work on the native,
numba_cpuandnumpy_refstep loops, and must not move the tracking cases' steps. - Exclude evanescent bins on tabulated operators. That needs the column's longitudinal wavenumber, which
LinearOperator.beta0does not give on the radial route: it is recorded as 0 there.
Done when
radial_filament_512 and cartesian_filament_256 take within 1 % of their unclamped step counts while #149's two witnesses still leave less than 1e-3 of the launch.
- Lingua principale
- Python
- Stelle
- 3
- Fork
- 3
- Merge medio
- 8h 37m
- PR unite (30g)
- 159
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di LupoLab/solprop
-
docs/dev/backends.md still lists the removed set_held_plane and held_observationForse già presa Una pull request collegata a questa issue è aperta o già unita. Apertadocumentation priority: low
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
performance priority: low
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
I maintainer di solito rispondono entro 1 giorno
-
The TDSE steady-current certificate can refuse a resolved taper on a band far above its frequenciesApertaarea: tdse enhancement priority: low
Difficoltà 2/5 1-3 ore Idoneità per principianti 60/100
I maintainer di solito rispondono entro 1 giorno
-
The band-edge term that floors comparisons between windows is recorded only in an archived SEPApertaarea: boundaries documentation priority: low
Difficoltà 2/5 Mezza giornata Idoneità per principianti 62/100
I maintainer di solito rispondono entro 1 giorno
-
area: backends bug priority: low
Difficoltà 2/5 Mezza giornata Idoneità per principianti 66/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di LupoLab/solprop
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
NVIDIA/auto-ontology#463 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
NousResearch/hermes-agent#151165 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
I maintainer di solito rispondono entro 1 giorno
-
code-health
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
tinaudio/synth-setter#3750 ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug] vllm-sr config migrate drops providers.models[].deploymentForse già presa @Bevisy l’ha presa oggi. Apertaneeds-acceptance wg/developer-experience-ecosystem
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
vllm-project/semantic-router#5996 ·
I maintainer di solito rispondono entro 2 giorni