Physical resource estimation script #66
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a script that reads logical resource estimate solution files and generates physical resource estimate solution files in order to address #45. The generated solution files include algorithm run time, overall run time, number of physical qubits, and some details about the assumed architecture.
Most fields from the LRE solution files are retained, with a few exceptions. Importantly, the solution and solver UUIDs are replaced. The LRE solution and solver UUIDs are recorded however in the
logical_resource_estimate_solution_uuid
andlogical_resource_estimate_solver_uuid
fields ofsolver_details
.Note that for a given task, the script may not be able to find code distances that yield the required overall success rate. In this case the task will still be included in the new solution file, but it will not contain the fields for algorithm run time etc.
Note that the example PRE config uses a physical error rate of 1e-4, which corresponds to the "optimistic" case in arXiv:2011.03494. I chose this value because I wanted to make sure that the example config will successfully generate resource estimates for at least one of the benchmark tasks. I've tested it with planted solution 1 (14 orbitals).