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(qvol): First version of adding Quantum Volume to Recirq. #27

Closed
wants to merge 4 commits into from

Conversation

KevinVillela
Copy link

This just adds a simple task and driver Script for now. More to come, such as precomputing the generated circuits and the optimal qubits to run on in other tasks.

#24

This just adds a simple task and driver Script for now. More to come, such as precomputing the generated circuits and the optimal qubits to run on in other tasks.
Copy link
Collaborator

@mpharrigan mpharrigan left a comment

Choose a reason for hiding this comment

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

Making the module recirq/benchmarks might be more future proof, what do you think?

I encourage you to add a notebook to docs/benchmarks/Quantum-Volume.ipynb that describes this benchmark and executes the tasks with a simulator. This can be simple for now and can open an issue to flesh out the documentation

tabulation_resolution=0.008),
add_readout_error_correction=task.readout_error_correction)
# Save the results CODE REVIEW QUESTION: This attempts to serialize a QuantumVolumeResult, which contains a
# Circuit, which contains a SerializableDevice, which is not JSON serializable. What's the best way to resolve
Copy link
Collaborator

Choose a reason for hiding this comment

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

does the circuit's device have any bearing on the experiment? or is it just hanging around? [I've always found the fact that a Circuit has a Device to be somewhat vestigial]

If it's just hanging around, you could set it to None with a note. Ideally SerializableDevice would be JSON serializable lol

Copy link
Author

Choose a reason for hiding this comment

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

It's just hanging around - setting it to None allows me to serialize it, but then I can't deserialize it because it expects a circuit. I'm thinking I should just try to add serialization to SerializableDevice - WDYT?

@KevinVillela
Copy link
Author

Sorry for the delay, PTAL. Thanks!

@mpharrigan
Copy link
Collaborator

closing as stale

@mpharrigan mpharrigan closed this Nov 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants