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

feat: support different number of effects for each qubit #93

Open
timmintam opened this issue Aug 15, 2024 · 1 comment
Open

feat: support different number of effects for each qubit #93

timmintam opened this issue Aug 15, 2024 · 1 comment
Assignees
Labels
api change Implies a change in the API enhancement New feature or request

Comments

@timmintam
Copy link
Collaborator

Extend the interface of the RandomizedProjectiveMeasurements class to support different number of effects for each qubit.
We may need to move away from np.ndarray input types for bias and angles to sequences of sequences.

@timmintam timmintam changed the title feat: If we extend this interface to support different number of effects for each qubit in # the future, we may need to move away from np.ndarray input types to sequences of sequences. feat: support different number of effects for each qubit Aug 15, 2024
@timmintam timmintam self-assigned this Aug 15, 2024
@timmintam timmintam added enhancement New feature or request api change Implies a change in the API labels Aug 15, 2024
@timmintam
Copy link
Collaborator Author

As a consequence of #94, the argument bias is now allowed to have some values set to 0 for RandomizedProjectiveMeasurements instances. In practice, this changes the number of effective effects for each qubit.
Although it not the cleanest implementation (one still has to enter some dummy values for angles even if the corresponding bias is set to 0) it works. Maybe we will want to have a cleaner implementation in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api change Implies a change in the API enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant