.. -*-coding: utf-8 -*-

Measurement Guide for Reverberation Chambers
============================================

This page summarizes practical measurement guidance for ``MpyLab`` in
mode-stirred (reverberation) chamber setups.

Overview
--------

``MpyLab`` integrates device control, acquisition, and evaluation in one Python
runtime. Typical measurements are executed by a small measurement script plus one
configuration file.

Recommended project layout per measurement campaign:

- one dedicated folder for the measurement script and configuration
- optional ``.dot`` file describing the measurement graph
- autosave/output files generated by the runtime

Measurement runtime
-------------------

A measurement run creates an ``MSC`` object, either from scratch or from persisted
state (pickle). The runtime handles:

- instrument communication
- execution of measurement routines
- evaluation routines
- autosave and persistence of intermediate state

Persisting the state allows long-running measurements to resume from previous checkpoints.

Measurement graph (DOT)
-----------------------

The setup topology (instruments, cables, couplers, attenuators, paths) is defined
as a graph in a ``.dot`` file. This graph is used by the runtime to resolve signal
paths and evaluate measured quantities.

The DOT parser and grammar references are documented separately:

- :doc:`dot-grammar`
- :doc:`dat-file-grammar`

Notes
-----

This English page is the maintained counterpart of the historical German
measurement guideline and focuses on the current workflow concepts.

Historical reference
--------------------

An English translation of the historical detailed guide is available below:

.. toctree::
   :maxdepth: 1

   historical-measurement-guide.rst