Motivation
Currently, when comparing noise parameters to their actual usage in emulation, it's difficult to see the derived/computed quantities. Most noise parameters are used directly, but some (like sigmas for doppler and atom positions in register noise) are derived from the input parameters. Having a report would make it easier to:
- Understand what values are actually being used in the emulation
- Debug and validate noise model configurations
- Compare expected vs actual noise parameters
Proposed Solution
Create a method (e.g., NoiseModel.report() or similar) that outputs:
- All noise parameters as directly used in emulation
- Derived quantities (particularly sigmas for doppler and atom position register noise)
- Clear labeling to distinguish input parameters from computed values
Additional Context
This would primarily benefit users debugging simulations or validating that their noise model configurations produce the expected behavior in emulation.
Motivation
Currently, when comparing noise parameters to their actual usage in emulation, it's difficult to see the derived/computed quantities. Most noise parameters are used directly, but some (like sigmas for doppler and atom positions in register noise) are derived from the input parameters. Having a report would make it easier to:
Proposed Solution
Create a method (e.g.,
NoiseModel.report()or similar) that outputs:Additional Context
This would primarily benefit users debugging simulations or validating that their noise model configurations produce the expected behavior in emulation.