The added types for trajectories, simulations and lattice sites need useful implementations of Base.show().

Current state is worst for simulations, looks like this:
Simulation(:ChainPP, 12, 12, "test_ChainPP", true, :debug, 36, 3, 100, 4, Vector{Real}[[1//3, 1//3, 1//3], [1//2, 1//2, 0//1], [1//1, 0//1, 0//1], [0//1, 1//1, 0//1], [0//1, 0//1, 1//1]], Vector{Trajectory}[[LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[1//3, 1//3, 1//3], true, :debug, 1, 36, 3, 100), LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[1//3, 1//3, 1//3], true, :debug, 2, 36, 3, 100), LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[1//3, 1//3, 1//3], true, :debug, 3, 36, 3, 100), LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[1//3, 1//3, 1//3], true, :debug, 4, 36, 3, 100)], [LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[1//2, 1//2, 0//1], true, :debug, 1, 36, 3, 100), LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[1//2, 1//2, 0//1], true, :debug, 2, 36, 3, 100), LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[1//2, 1//2, 0//1], true, :debug, 3, 36, 3, 100), LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[1//2, 1//2, 0//1], true, :debug, 4, 36, 3, 100)], [LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[1//1, 0//1, 0//1], true, :debug, 1, 36, 3, 100), LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[1//1, 0//1, 0//1], true, :debug, 2, 36, 3, 100), LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[1//1, 0//1, 0//1], true, :debug, 3, 36, 3, 100), LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[1//1, 0//1, 0//1], true, :debug, 4, 36, 3, 100)], [LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[0//1, 1//1, 0//1], true, :debug, 1, 36, 3, 100), LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[0//1, 1//1, 0//1], true, :debug, 2, 36, 3, 100), LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[0//1, 1//1, 0//1], true, :debug, 3, 36, 3, 100), LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[0//1, 1//1, 0//1], true, :debug, 4, 36, 3, 100)], [LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[0//1, 0//1, 1//1], true, :debug, 1, 36, 3, 100), LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[0//1, 0//1, 1//1], true, :debug, 2, 36, 3, 100), LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[0//1, 0//1, 1//1], true, :debug, 3, 36, 3, 100), LatticeCircuits.PPChainTrajectory(12, 12, "test_ChainPP", Real[0//1, 0//1, 1//1], true, :debug, 4, 36, 3, 100)]])

Including Makie in the main package increases bloat. Instead, we should have a separate Plotting package and also have some debugging visualisation tools with UnicodePlots.

Observables can be measured multiple time due to periodic boundary conditions. May give better statistics per unit time if asynchronously parallelised.

Save ensemble as matrix and use reshape in simulate()?!

Creating and storing all possible operators for a given trajectory should significantly improve performance, since every operator is used far more often than O(N) times per trajectory.

Benchmarked on Apple M1 Pro. Slower RAM is going to increase the effect.

For final release, restructure classes and data management

• "Circuit" class which more abstractly captures the initial state and how to evolve it
• separate thermalization and sampling, with new methods (eliminate "simulate" and "run" methods)
• (optionally) compressed/efficient permanent storage of thermalized states

The JLD2 header may be wasteful, as well as saving all measurements instead of the trajectory average. Currently, a single trajectory saves 50-100 KB, while only containing a few bytes of useful information. However, resuming of trajectories requires this.
Proposed compromise: automatically overwrite trajectory measurement series with average on first evaluation, and detect on following evaluations to avoid error. Integrate boolean "finalized" in file.