Troubleshooting
Troubleshooting
Structured checks for configuration, transport, data, and analysis failures.
Begin with diagnostics
pmoke --config config.toml doctor
pmoke --config config.toml doctor --json > doctor.jsonThe report separates compiled-feature errors, controller failures, instrument address failures, storage access, Python imports, and config diagnostics.
Instrument does not answer
- Compare the normalized URI and required feature in
doctoroutput. - Confirm the model's transports with
pmoke instruments explain MODEL. - Query a SCPI instrument explicitly with
pmoke instruments query. - For Prologix, distinguish adapter reachability from the instrument PAD.
- Increase the URI timeout only after checking cabling and command termination.
Analysis rejects artifacts
- Run
pmoke raw verifybefore conversion or analysis. - Keep
acquisition/manifest.tomlwith every referenced waveform. - Rerun the upstream stage named by a stale-stage diagnostic.
- Use a new
--run-dirwhen acquisition settings differ. - Preserve the last published analysis; failed runs remain under an incomplete tree.
Lock-in warnings
Treat Nyquist, excessive gain, ill-conditioned integer-period coefficients, and settling-range warnings as numerical diagnostics rather than formatting noise. Select a stable filter and output stride before increasing smoothing.