Hi Alexander, On 20 July 2012 00:21, Alexander Mouschovias <[email protected]> wrote:
> Hi guys, > > I'm working with tutorial 4 from the 2011 workshop (available at > https://github.com/jack-h/tutorials_devel). In the get_data function from > poco_plot_cross.py, it seems to me that a_0r=b_0r, a_1i=b_1i, etc. At least > in my use case, they are always equal. Can someone tell me, is this a > remnant from some previous version, the start of some new feature, or > something else? > As far as I can tell a and b in the get_data() method of poco_plot_cross.py are indeed the same thing. One ends up being plotted as the magnitude and one as the phase, but they are the same data, read from the same brams. I assume this is an artefact from reusing code and removing a feature. Whatever it is, I don't think you're missing anything devious (or if you are, I am too). I've removed the superfluous double read and pushed to github. > > Another note from the same script: in the drawDataCallback function, I > needed to add "fig.canvas.draw()" right before > "fig.canvas.manager.window.after(100, drawDataCallback,baseline)" to get it > to update the plot properly. (This also applies to poco_plot_auto.py.) > Assuming this isn't just my computer acting strangely, hopefully that can > get added to the version that will be used in the Auguest CASPER workshop. > I don't seem to need the draw() call. Someone more knowledgeable in the intricacies of matplotlib may have some advice, but it doesn't hurt my system to have the draw() call you need, so I've added that too in the latest github push. > > Thanks! > > -----Alexander > If you have the time to check these changes work for you -- in particular that your plotting is now fixed -- I'd appreciate if you let me know. (Obviously also let me know if I've just broken everything -- it's quite late over here and I should probably go to sleep!) Cheers, Jack
