Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I created the Class QPU in order to make simulations applying noise just as the real QPU (Quantum Procesing Units) have.
I added some data about several QPUs in the market, that can be accessed through the cloud, through an sql script in order to be accessed later from the QPU class.
It calculates the noise parametres and initiates a QRegistry with noise enabled.
Just at the creation of the registry and at measurements it applies the SPAM error (State Preparation And Measurement) as a ratio of preparing (or measuring) the state 1 when it shoud be the state 0 and viceversa.
In order to apply the gate fidelity it checks if it is a 2 qbit gate or a 1 qbit gate in order to apply the right fidelity from the noise parameters. It calculates a noisy gate as seen in parser.py (lines 326-340) to be applied to the registry.
I had to change the usage of the gates to apply in a way that I feel it is more intuitive mostly in the gates like the U gate that need some parameters like an angle. Also targets must be lists even if there is only one target to the gate.
For example:
Before we had to use:
Now it is used like: