The Tomographer C++ Framework groups a set of classes and functions which allow to reliably analyze data from quantum experiments. These serve in particular as components for the tomorun executable program.

Tomographer's Components

The classes and routines of the project belong to several categories:

Tools

These are basic tools and utilities:

most tools, e.g. C++ language utilities and matrix utilities, are located in the namespace Tomographer::Tools;
Tomographer::MAT provides a set of routines to read data from MATLAB files (based on the MatIO library);
Tomographer provides a lightweight mechanism for logging messages. See Logging and Loggers;
Some more utilities are provided in Tomographer::SolveCLyap and Tomographer::SphCoords.

Specifying the Quantum Tomography Problem

A quantum tomography setting with measurement results is specified as following in our generic framework:

A type complying with the MatrQ Interface specifies which C++ types to use to store a density matrix and parameterizations of it. For the moment this should be a Tomographer::MatrQ instance.
A type implementing the TomoProblem Interface stores the experimental data and is responsible for calculating the loglikelihood function. For the moment, you should use Tomographer::IndepMeasTomoProblem.

Note: These type interfaces above might change in the future.

Running the Metropolis-Hastings Random Walk

The Tomographer::MHRandomWalk takes care of running a Metropolis-Hastings random walk. You need to give it a specification of the random walk parameters, including what the state space is, the jump function, starting point, step size, etc. in the form of a type implementing the MHWalker Interface.
The Tomographer::DMStateSpaceLLHMHWalker is a type implementing the MHWalker Interface, which is capable of running a random walk on the space of quantum states represented by dense C++ Eigen matrices, and using the distribution proportional to the loglikelihood function on the Hilbert-Schmidt measure.
While running the random walk, you'll want to collect some form of statistics. This is done with objects which comply with the MHRWStatsCollector Interface. For example, see Tomographer::ValueHistogramMHRWStatsCollector and Tomographer::ValueHistogramWithBinningMHRWStatsCollector.

Multiprocessing: Running Tasks in Parallel

An abstract multiprocessing framework is specified using a set of interfaces, see Task Manager/Dispatcher Interfaces. This requires on one hand an implementation of a multiprocessing environment, and on the other hand a specification of which tasks are to be run.
Classes in the Tomographer::MultiProc::OMP namespace are an implementation of a multiprocessing environment using OpenMP. This dispatches the tasks over several threads (on a same machine).
The Tomographer::MHRWTasks namespace groups a set of classes which may be used to specify tasks to run which consist of abstract Metropolis-Hastings random walks.

Documentation Pages

Important Namespaces

Tomographer — base Tomographer namespace
Tomographer::Tools — namespace for various tools
Additional tools are available in selected namespaces. See the List of Namespaces.

Specific Topics

Other Specific Resources

Useful Resources for Debugging