Skip to content

Added get_ising_sw_all function which caomputes X and Z single qubit … #3

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

Vinay-Tripathi
Copy link
Member

…coeefients and all two-qubit interactions i.e. XX, YY, ZZ between any qubit pair

…coeefients and all two-qubit interactions i.e. XX, YY, ZZ between any qubit pair
@MostafaKhezri
Copy link
Contributor

I don't think you need to calculate the coefficients between all pairs of qubits, since not all qubits are coupled together, and qubits that are not directly coupled will have very small coupling values (as you can see in your example notebook as well). You can keep this method that you already have, just because ZZ between non-neighbor qubits may not be very small, but XX and YY will definitely be very small. However, please add the requested functionality below as well:

Modify the methods that I already have (full SW and PWSW) to include ability to calculate XX and YY couplings as an option. You'd essentially add an option to my previous methods, for example XX_YY=True, so that when this option is true in those methods they calculate XX and YY as well, and when it is false they don't do that (they just do what I initially had). Of course all these terms will only be calculated for qubits that are neighbor and coupled via a coupler element (not next-nearest neighbors).

…_sw_all by get_ising_sw_ho which calculates only ZZ even for higher order. Also modified the example notebook higher_order_and_other_couplings.ipynb
…or non-MRT regime. Defined a function for CSFQ class get_phi_z_cutoff which gives the upper limit of phi_z allowed for flux qubit.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants