solprop.driver#
The simulation driver: physics objects in, a written run out.
Layer D of docs/dev/architecture.md section 3. The package re-exports Simulation
(simulation, a run that translates once and writes a resumable
file), SimulationSettings (settings), run_problem
(run, the loop over save planes), SimulationRunner
(runner), the keyword interfaces prop_gnlse,
prop_capillary, prop_waveguide, prop_free and prop_planar
(interface), and the TDSE presets and consistency check
(tdse, tdse_consistency). The
constructors’ keyword routes are solprop.driver.routes; scans and their executors
are solprop.driver.scan and solprop.driver.executors; the session’s
service loop, inputs, defaults, metadata, resume, summary and estimate have a module
each. solprop.driver.scaffold stays as the independent fixed-step integrator the
backend tests cross-check against. The manual page is docs/guide/setup/running.md.
Modules
The route defaults: one table, and the pure functions that resolve a default. |
|
What a run will cost, before it runs (SEP 41, S11). |
|
Execute independent scan points under an explicit resource policy. |
|
A run's input: its pulse, its launch, its shot noise and its peak field. |
|
The keyword interface: one call from keywords to a written run. |
|
Record the material and physical reconstruction data needed by saved-run analysis. |
|
The record that says what produced a run, and whether it may be resumed. |
|
Resolve material declarations and population selections at the driver boundary. |
|
The lazy view of a saved plane that a plane observer is shown (SEP 41, S3). |
|
Continue a run from the file it wrote: the resume decision and the restart. |
|
The keyword routes that build a |
|
The outer loop of a run: save planes in, saved planes out. |
|
Run one translated simulation many times on one backend, input by input. |
|
A fixed-step interaction-picture integrator for the mode-averaged GNLSE. |
|
Describe indexed parameter scans and dispatch independent simulations. |
|
The session loop: Python's side of an execution session (SEP 47 section 5). |
|
How a run is stepped, what it records and which backend executes it. |
|
The simulation object: physics objects in, a written, resumable run out. |
|
The block a run shows before its first step: what is about to be computed, and how. |
|
Own the optional TDSE runtime behind the provider-free response seam. |
|
Check a haCC model's weak-field linear response against optmat's helium (SEP 20). |
|
The run glue of a TDSE response (SEP 20): its archive, atomic state and gate. |