David McKay

You could loop it in with the tomography code, but I would just make it as a notebook example

I think 2 is best because we also want to avoid having the scheduler code in too many places and/or make the schedule code too complicated. In the short term...

The problem you're describing can even be present in Qasm QPT (not involving pulse at all). I would say if you restrict all singles to be defined only in terms...

Oak Ridge agreed to tackle this

The ignis architecture is based on a module that creates circuits and then a class that fits the results of those circuits. In this case, similar to tomography, you would...

> because the counts dictionary is not marginalized. Could you explain what you mean here with an example?

@chriseclectic wasn't there a marginal counts in terra? I can't seem to find it

I'll probably soften my stance after thinking about it and I shouldn't have said *all* fitters. The examples I were thinking of are things like T1, T2, T2* where the...

I would disagree because ignis is about characterizing noise on specific physical qubits

But this is a psuedo-validation, because the fitter knows what the data should be.