FAQ

Should I use --system-site-packages during the installation?

Generally, we recommend not using that flag. An installation from scratch via uv into a dedicated virtual environment is recommended. Then, all packages will be installed as indicated in the uv.lock file, which corresponds to the tested versions in the GitHub workflows. However, if a (e.g., proprietary) package is only available globally on your system, you have to use --system-site-packages.

Can the measurements run any faster?

On a reasonably new computer (e.g., 2023), the software can collect a datapoint every 600µs, assuming that the datapoint itself requires no acquisition time. Profiling a run in matrix-script yielded the following result: The time to allow the visualization of the currently executed line amounts to approximately 200µs. The time to open the datafile, add the datapoint and close it again also takes approximately 200µs. Everything else takes the remaining 200µs and was not further investigated.

If a 3× speed increase would be beneficial in your use case, please open an issue on the GitHub repository.

What is the relation between matrix-script and matrix-gui?

matrix-gui provides a zero-programming interface to measurements, which might be preferable to some users, while matrix-script requires short Python scripts to define the measurements. This should mostly be a matter of preference, and the capabilities of matrix-gui should not be limited by design. However, the possibility to run arbitrary Python code in matrix-script will to some extent allow lower-level control.

Is there a Dark mode?

Yes, Dark mode is provided for all matr1x graphical user interfaces. This includes dynamic, automatic switching between light and dark mode based on the system settings. Consequently, this extends to the user guide as well, where all images are provided in two variants.

Do you accept patches for upstream bugs?

Unfortunately, it is not possible for us to accept patches for upstream bugs. This was attempted in the past and only led to increased complexity, a higher maintenance burden, and potential regressions. In very rare cases where our software does not work properly at all and an upstream fix is not (and will not be) available, we will consider patches.