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

New LOM: Transmon Transition Energy #920

Open
ferrispnugraha opened this issue Feb 10, 2023 · 4 comments
Open

New LOM: Transmon Transition Energy #920

ferrispnugraha opened this issue Feb 10, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@ferrispnugraha
Copy link

Information

  • Qiskit Metal version: 0.1.2
  • Python version: 3.11.0 | packaged by conda-forge | (main, Oct 25 2022, 06:12:32) [MSC v.1929 64 bit (AMD64)]
  • Operating system: Windows-10-10.0.19044-SP0

What is the current behavior?

image
Too large energy levels (order of 10^3 GHz)

Steps to reproduce the problem

Inspired from the Qiskit_Metal\qiskit-metal\tutorials\4 Analysis\A. Core - EM and quantization\4.04 New LOM and Fluxonium Example.ipynb, sweep a transmon qubit with $n_g$. The transmon parameters are based on Transmon_5p5GHz_fQ_cmat.txt

HilbertSpace:  subsystems
-------------------------

Transmon------------| [Transmon_2]
                    | EJ: 13278.758148398147
                    | EC: 335.4436048599739
                    | ng: 0.001
                    | ncut: 150
                    | truncated_dim: 10
                    |
                    | dim: 301

What is the expected behavior?

image

@ferrispnugraha ferrispnugraha added the bug Something isn't working label Feb 10, 2023
@priti-ashvin-shah-ibm
Copy link
Collaborator

priti-ashvin-shah-ibm commented Feb 10, 2023

Hi @schwarz11 , can you add more information?

Please show the code you used to sweep. Also, did you recently make a conda env? Was it October 25th?

If you don't get the results you want, it could be the components within your design, vs the software repo. If you want help to use Metal, discussions are in Slack. You need to join Qiskit workspace, then ask on #metal. Issues are used to request code changes or bugs within the software.

@ferrispnugraha
Copy link
Author

Hi @priti-ashvin-shah-ibm , thank you for the reply!

Here is the code I used for the results above. Basically, I am trying to sweep charge to transmon, in the same way as sweeping flux to fluxonium in the tutorial. I have also checked that my scqubits is up-to-date (version 3.1.0) in the environment.

image
image
image
image
image

@zachparrott
Copy link

zachparrott commented Mar 30, 2023

It appears the EJ and EC values in your scqubits Transmon object are in MHz * h not GHz * h, this is giving the scaling of 1e3.

Python 3.9.16 (main, Mar  8 2023, 10:39:24) [MSC v.1916 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import scqubits as scq
>>> tmon1 = scq.Transmon(13278, 335, 0.001, 150)
>>> ev1 = tmon1.eigenvals()
>>> ev1 - ev1[0]
array([    0.        ,  5608.01726784, 10821.28811915, 15597.19000465,
       19612.15215931, 23961.14733016])
>>> # now rescale
>>> tmon2 = scq.Transmon(13.278, 0.335, 0.001, 150)
>>> ev2 = tmon2.eigenvals()
>>> ev2 - ev2[0]
array([ 0.        ,  5.60801727, 10.82128812, 15.59719   , 19.61215216,
       23.96114733])

@ferrispnugraha
Copy link
Author

Hi @zachparrott , it seems that you're right. Then, I think special care needs to be performed for units when transferring from transmon to composite system before calculating the hilbertspace , hence qubit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants