-
Notifications
You must be signed in to change notification settings - Fork 319
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
PyQtgraph live plot does not update #259
Comments
It will be good to combine this issue with #155 |
I'm pretty sure this is due to the So far I hadn't time to finish my other additions to |
@MerlinSmiles I would be very interested in seeing if your solution solves the problem. |
@AdriaanRol yes, at least in the long run that's the goal :D |
No, Don't see anything |
@AdriaanRol I did a very minor cleanup, so there is a lot of hacky stuff in there, but could you try the |
@MerlinSmiles , I could not find your notebook |
its here: |
And no, it wont replace the normal QtPlot, as I still wanted that for comparison (if I remember right) |
Excuse me, probably a typo on my end. I found it now, however upon running the first cell I run into qtawesome (I guess that is something you made?) Could there be some hidden path dependencies in there ?
|
ah shoot |
its here: https://pypi.python.org/pypi/QtAwesome |
@MerlinSmiles I figured Nonetheless I now run into a bug in cell # 3. c0, c1, c2, vsd = gates.chan0, gates.chan1, gates.chan2, source.amplitude
data2 = qc.Loop(c1[-15:15:1],0.001).loop(c0.sweep(30,15,1),0.001).each(
meter.amplitude, # first measurement, at c2=0 -> amplitude_0 bcs it's action 0
qc.Task(c2.set, 1), # action 1 -> c2.set(1)
meter.amplitude, # second measurement, at c2=1 -> amplitude_4 bcs it's action 4
qc.Task(c2.set, 0)
).run(location='data/test2dx', overwrite=True)
plot2Q = QtPlot(data2.chan0, data2.chan1, data2.amplitude_0,name=data2.location)
|
maybe you need to update your pyqtgraph to get that |
Just checked pip list tells me I am running |
no clue why you get that error then. But its not really needed, so what is the error if you remove that line? :) |
could you try to figure out why you dont have that Maybe I should split that timing thing out into an individual PR then, it will take a little until i have the time to look at the other stuff I think schould be there. But that will then also not include the notebook dumping. |
After live plotting working fine for both MatPlot and QtPlot it now doesn't work in my experiment and just waits to plot until the data.sync() has finished (I can't even update my plot manually in the meantime). Perhaps something to do with the fact that it's a 'hard' parameter but I don't really see why that would make a difference... |
@nataliejpg I dont understand exactly. Does your plotting work with the above changes, or did you fix your system? I'll make the changes up there to a separate PR, so it can be added faster. So live plotting works but not in your experiments? Are you running your loop in the background? Then the plotting calls the |
There seems to be a regression so live plotting doesn't work right for array-valued parameters at all right now - @nataliejpg showed it to me with her VNA but I see it in the tutorial too. The issue is with bookkeeping on the DataServer, getting confused about what data it has in its arrays. Investigating... |
Ok, I see, missing context :D |
Sorry, I thought the 'hard' parameter was discussed previously. It's my 'multidimensional parameter'. |
Closing. MP is deprecated. And eventually the new architecture will solve this things. |
Issue made to get rid of the hack in PR #250 .
Steps to reproduce
Expected behaviour
Expect to see a live updating plot of the data
Actual behaviour
Plots only what is in "data" the moment the plot function is called.
Workaround
The following code will keep updating the plot (in the main thread) while the data taking is not finished yet.
System
operating system
OS X El Capitan 10.11.5 (15F34)
qcodes branch
"examples" (only contains notebook so should be close to master)
qcodes commit
Commit: 007e5f9
The text was updated successfully, but these errors were encountered: