Help and diagnostics ==================== This section maps an observed problem to the layer at which it should be investigated. For a concrete error message, start with :doc:`troubleshooting`. .. toctree:: :maxdepth: 1 troubleshooting Contributors can find the build, review, and publication workflow in :doc:`Maintaining the documentation `. This page is also linked directly from the documentation start page. Further checks -------------- * :doc:`Validate configurations <../configuration/validation>` covers DOT paths, NPORT data, and CI checks. * :doc:`Testing and commissioning <../framework/testing>` puts unit, virtual end-to-end, safety, Qt, and hardware tests into context. * :doc:`Measurement history and output files <../results/history-files>` explains autosave, resume, intermediate states, and relocated log files. * The :doc:`API reference <../../api/index>` documents exceptions and public interfaces. * The :doc:`archive <../archive/index>` preserves earlier guides clearly separated from current operating and development information. Safety-related failures ----------------------- If the RF level is unexpected, amplifier protection is missing, or RF-off cannot be reached, stop the measurement in a controlled manner. Investigate the cause only after RF has been switched off. Do not disable protection features for diagnostic convenience.