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

Cutting decompose step should return a subexperiment dictionary #387

Closed
caleb-johnson opened this issue Aug 30, 2023 · 2 comments
Closed
Labels
cutting QPD-based circuit cutting code good first issue Good for newcomers

Comments

@caleb-johnson
Copy link
Collaborator

caleb-johnson commented Aug 30, 2023

For circuit cutting, users should have a way to map a subexperiment index (output from the decompose step) to the specific sample/sub-observable from which it was created. The sample could be represented in a number of ways -- maybe a list of (basis, id) tuples would be an intuitive representation of a "sample"?

@garrison garrison added the cutting QPD-based circuit cutting code label Aug 30, 2023
@garrison
Copy link
Member

garrison commented Aug 30, 2023

This is a continuation of the conversation at #378 (comment):

I think [that ordering the observables like sample_{0}observable_{0}, sample_{0}observable_{1}, ..., sample_{0}observable_{N}, ..., sample_{M}observable_{N}] is fine as a first step, but I would really like to move away from this and instead expose an explicit map that allows looking up each (sample, observable) from the index in this flat list and vice versa. The reason is because some experiments are actually redundant (#262) or potentially even unnecessary, i.e. if the only observables in that subregion are all Pauli Is (in which case those experiments can be skipped altogether).

@caleb-johnson
Copy link
Collaborator Author

This issue is stale. Dictionaries are now used in cutting-for-width workflows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cutting QPD-based circuit cutting code good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants