Run a measurement
=================

This entry point is for users who want to run an existing mpylab measurement
class and script.

1. Check the installation
-------------------------

Install mpylab in a virtual environment and start with a virtual workflow.
The required commands are documented under
:doc:`../getting-started/index`.

2. Select a measurement workflow
--------------------------------

:doc:`../measurements/index` describes the available workflows:

* MSC main and EUT calibration, emission, and immunity;
* TEM/GTEM verification, e0y, emission, and immunity;
* amplifier characterization in rack and direct setups.

Observe the technical sequence. An immunity or emission measurement may
depend on reference data from preceding measurements.
For immunity tests, :doc:`using EUT monitoring
<../framework/eut-monitoring>` explains the manual and automatic monitoring
parameters of the existing classes.

3. Check the configuration
--------------------------

A ``conf.py`` defines input and output files, measurement parameters, and
search directories. DOT files describe instruments and signal paths; INI and
DAT files contain instrument and correction data. Start with the :doc:`DOT
reference <../configuration/dot>`, the :doc:`INI and DAT reference
<../configuration/instrument-data>`, and the :doc:`configuration workflow
<../configuration/workflow>`. Run :doc:`validation
<../configuration/validation>` before accessing hardware.

4. Start virtually and use preflight
------------------------------------

The virtual run should use the same measurement script and public instrument
methods as the hardware run. Check:

* frequencies, levels, positions, and dataset descriptions;
* expected output files;
* autosave and resume;
* RF-off and protection limits;
* evaluation and, where applicable, reports.

For safety-critical TEM workflows, also follow the ``HARDWARE_TEST.md`` in
the corresponding template configuration.

5. Preserve the results
-----------------------

The final pickle is the complete history container. Raw data, processed DAT
files, and reports are derived views. Autosave, intermediate, and history
pickles are explained under :doc:`../results/history-files`.

For unexpected behavior, continue with
:doc:`Investigate a problem <troubleshoot>`.