Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTML Reports for Non-Gauge Optimized Models #412

Closed
pcwysoc opened this issue Mar 25, 2024 · 2 comments
Closed

HTML Reports for Non-Gauge Optimized Models #412

pcwysoc opened this issue Mar 25, 2024 · 2 comments
Assignees
Labels
bug A bug or regression
Milestone

Comments

@pcwysoc
Copy link

pcwysoc commented Mar 25, 2024

Describe the bug
When gauge optimization is not performed during GST the HTML report does not generate the gauge-dependent figures. There is a similar, less critical, problem for notebook reports.

To Reproduce

GaugeOptReportBug.ipynb.zip

Expected behavior
I believe that the raw estimates and error metrics should still generate, although they won't be as informative. Otherwise, there should be some flag to remove the gauge-dependent sections of the report.

Environment (please complete the following information):

  • pyGSTi version qiskit-feature-mcm
  • python version 3.10
  • OS 13.6.5
@coreyostrove
Copy link
Contributor

Thanks for the bug report, @pcwysoc! And for the example code reproducing the error. I have implemented a fix for this (along with some other issues I discovered along the way) on the branch 'feature-circuitlistsdesign-reporting'. These should be merged into develop sometime soon (there is already a PR for these changes), but in the meantime you can merge that branch into your own if you need this working right away.

@sserita sserita added this to the 0.9.12.2 milestone Apr 2, 2024
@sserita sserita added the fixed-but-not-in-release-yet Bug has been fixed, but isn't in an official release yet (just exists on a development branch) label Apr 15, 2024
@sserita
Copy link
Contributor

sserita commented Apr 15, 2024

Closing as this is now merged in with #415

@sserita sserita closed this as completed Apr 15, 2024
@sserita sserita removed the fixed-but-not-in-release-yet Bug has been fixed, but isn't in an official release yet (just exists on a development branch) label Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A bug or regression
Projects
None yet
Development

No branches or pull requests

3 participants