<rjo>
sb0: yes. i would not let the "waiting" issues delay rc1.
<rjo>
sb0: all i noticed that the dds setting time can even be as long as 200 us (on pipistrello) and it seems to fluctuate a lot.
<rjo>
sb0: i was unable to determine wether it is actually wrong timestamps or just too much cpu time being lost.
<sb0>
the analyzer should give the timestamps
<sb0>
rjo, whitequark, shall I take care of the remote imports on controllers?
<sb0>
and an opencv/video controller sounds like a good demo
<rjo>
sb0: remote imports and the datacrunching thing?
<sb0>
yes
<rjo>
sb0: if you end up wrapping a camera api, i would try to stay away from opencv.
<rjo>
sb0: i had written parts of pydc1394 and pyflycapture2 (windows people love it and the cameras)
<rjo>
sb0: and i have a API wrapper for the andor cameras.
<sb0>
can i easily demonstrate the remote import of a function that does e.g. face recognition?
<rjo>
that may look cool but is not useful in the lab ;)
<sb0>
yes
<sb0>
what would be useful in the lab, and semi-trivial to implement?
<rjo>
the neutrals would be convinced by the demonstration that you can fit a 2D gaussian to noise 2D gaussian data.
<rjo>
and they would be really impressed if you can fit a fermi profile (with a nasty and expensive dilogarithm) to noise fermi profile data.
<sb0>
is there copy-paste/library code for that?
<rjo>
the former has been done many times. there must be github code "bec fit gaussian parabola thomas fermi thermal" would be a set of search words.
<rjo>
for dilog/polylog it is a bit more involved but would be nice because it would showcase linking c libraries (in this case gsl) with python and the data crunching.
<rjo>
and potentially even dynamic compilation (numba/cython/weave...)
<rjo>
i wrote code for that a couple years ago (weave+gsl).
stekern has quit [Ping timeout: 244 seconds]
stekern has joined #m-labs
<sb0>
whitequark, how do I get a QScrollArea to expand its child widget?