Allow users to suppress mitigation with SamplerV2

[yaelbh]

To my understanding, in the absence of resiliency level, the way to suppress any kind of mitigation with SamplerV2 is by

sampler.options.twirling.enable_measure = False

It took me quite some time to figure it out from the docs. I had to go through all the sampler options and check their default values.

There are two options:

1. Improve the documentation to include this use case.
2. Add an option like suppress_mitgation to the interface.

[jyu00]

Instead of having another option that users need to look though docs and find, wouldn't it be better to just make it explicit in the docs? Like having a section telling you what settings are needed to completely turn off any error mitigation / suppression.

[yaelbh]

Yes, this is Option 1.

[jyu00]

oh sorry I only read the title.

I opened this issue for doc update.

[ihincks]

This is maybe more a nit than anything, but I wouldn't classify measurement twirling as mitigation. In my view, error mitigation protocols are broadly any strategy that improves results by incurring extra QPU usage combined with post-processing. Measurement twirling, assuming the stack is efficient, uses the same resources as no measurement twirling. I'd call it noise tailoring (or suppression) because it suppresses coherent bits of the noise model.

[yaelbh]

In view of the issue that @jyu00 has opened, can we then close this one?