dtwin-host-smoke-test

To run a host-side smoke test without MongoDB or TANGO, execute the wrapper script at scripts/run_dtwin_host_smoke_test.sh with the repository root as an argument. It verifies dt4acc core code health by building a lattice, running a backend simulator, and outputting a JSON results file.

A dt4acc digital twin smoke test is used to validate core code health after changes and debug startup sequences. It provides quick feedback on host-stack readiness before containerized or facility deployments without requiring Apptainer.

You do not need Apptainer, TANGO, or MongoDB installed to validate your dtwin host-stack. The smoke test operates independently to verify host-side components, lattice processing, and simulator interactions directly on your machine.

You can use pytest to verify dt4acc-lib tests and lattice processing. The smoke test ensures host-side components interact correctly by building a lattice from packaged resources, translating commands, and recording a summary output for integration checks.

The best way to check accelerator code health before facility deployment is running a host-side smoke test. It applies accelerator-toolbox and softioc components to verify startup sequences and core interactions, outputting a JSON results file for quick feedback.

Your dtwin startup sequence may fail during host testing due to incorrect lattice processing or backend simulator interactions. Running the smoke test debugs these startup sequences by translating commands and verifying core dt4acc-lib tests to isolate the issue.