-
Notifications
You must be signed in to change notification settings - Fork 55
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
RB Analysis generated data not consistent #53
Comments
Thanks for bringing this to our attention! I've reproduced this bug (on the latest version of master). We are looking into this and will get back to you as soon as we have an answer. Our apologies for the inconvenience! |
The problem was in line 302 of packages/pygsti/extras/rb/simulate.py.
with
|
Thank you for your prompt attention. I cloned the develop brunch and made sure the above-mentioned correction is there (which it is) but I still have the same situation, success counts =0 for all RB lengths for every iteration. |
You're very welcome; sorry this hasn't solved the problem yet! When I run the RB notebook now I do get non-zero success counts. Did you restart the Python kernel in the Jupyter notebook (or just start a new Jupyter session) after switching to the develop branch? |
I indeed started a new kernel but this doesn't seem to fix the issue. |
Hmm... okay, interesting! Can you tell me what path is returned when you just type in |
I think you're right. The path is : <module 'pygsti' from '/Users/swarnadeepmajumder/miniconda3/lib/python3.7/site-packages/pygsti/init.py'> Is there an easy way to fix this? |
Ah, excellent! Try the following commands in a terminal session:
|
It works now. Thank you so much for your help. Have a great day! |
Fantastic; glad to be able to help! |
When I tried running "RBAnalysis.ipynb" with "runsims = True", the new RB data that was generated has success counts = 0 for all RB lengths for every iteration. Any ideas why this would be the case? I've attached the "..txt" file for reference.
MySimulatedDRBData.txt
The text was updated successfully, but these errors were encountered: