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

Bugfix for fiducial circuit line labels #418

Merged
merged 1 commit into from
Apr 15, 2024

Conversation

coreyostrove
Copy link
Contributor

This is a quick bugfix for issue #396. The fix here is to simply force each of the line labels for candidate fiducial circuits to match the state space labels of the input target model. This is a suboptimal fix looking forward to many-qubit systems (as I mentioned in a comment on #396), but we don't presently have the infrastructure needed for doing this a better way and this fix should be fine for 99% of use cases with ExplicitOpModels in the few-qubit setting.

This forces each candidate fiducial to have line labels that match the state space labels for the target model. Suboptimal fix for many-qubit systems, but should be fine for 99% of use cases with ExplicitOpModels in the few-qubit setting.
@coreyostrove coreyostrove added this to the 0.9.12.2 milestone Apr 9, 2024
@coreyostrove coreyostrove self-assigned this Apr 9, 2024
@coreyostrove coreyostrove requested review from a team as code owners April 9, 2024 04:26
Copy link
Contributor

@sserita sserita left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree that this is a short-term fix but better to have it for now. Thanks!

@sserita sserita merged commit 2de76d6 into develop Apr 15, 2024
4 checks passed
sserita added a commit that referenced this pull request Apr 15, 2024
@sserita sserita mentioned this pull request Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants