gds_fdtd.execution.backends

gds_fdtd simulation toolbox.

Execution backends: where a JobSpec runs. LocalBackend executes in-process; SubprocessBackend spawns gds-fdtd run job.json --out dir — proving the serialization boundary and giving crash isolation and parallelism (a sweep can submit N jobs and collect as they finish).

Handles are in-memory only (no job database), which is out of scope here.

Classes

ExecutionBackend(*args, **kwargs)
JobHandle(id, out_dir, _state, ~typing.Any] =)	Opaque ticket for a submitted job.
LocalBackend()	Runs the job synchronously in this process; submit() blocks.
SubprocessBackend([extra_imports])	Runs each job as python -m gds_fdtd.cli run ... (crash-isolated).