Closed hartytp closed 1 year ago
Thinking about this more, it might be better to have an AggregateModel
instead, which takes a list of tuples (model, name)
as well as a list of common parameters. Then the repeated model functionality here becomes essentially just a special case of AggregateModel
s.
The final thing I want to do here before merging is have the RepeatedModel
calculate the mean / peak-peak values.
This wraps a model to produce a new model with more result channels.
The intended use-case for this feature is situations like: take our single-qubit Rabi flop model and make a new model for simultaneous Rabi flopping on n qubits.