qtlab-users — QTLab users mailing list

[Qtlab-users] question about using SharedGObject to interact with GUI

[Chunqing D. <cd...@uw...>]

Dear Qtlab users,

We are trying to build a GUI on top of Qtlab for parameter management and performing multi-dimensional sweeps in experiments. I have noticed the qtlab gui interact with the shell through SharedGObject.So I wrote a simple class for testing as below:

from lib.network.object_sharer import SharedGObject

class Test_share_class(SharedGObject):

    att = 1

    def __init__(self, **kwargs):
        SharedGObject.__init__(self, 'test_share')

    def do_sth_to_let_GUI_know(self):
        print "In Qtlab shell"

    def func_called_by_GUI(self):
        print "Called by GUI"
        self.att = self.att + 1

In the GUI client site, I have the following code:
import gtk
from gettext import gettext as _L
from lib.network.object_sharer import helper

class SQD_GUI_START(gtk.Button):

    def __init__(self):
        gtk.Button.__init__(self, _L('SQD GUI'))

        self.set_sensitive(True)
        self.connect('clicked', self._call_func)


    def _call_func(self, sender):
        '''
        behavior when clicking the button
        '''
        ob = helper.find_object('test_share')
        ob.func_called_by_GUI()

Using this, I can call the function "func_called_by_GUI" from the GUI by clicking a button.

Additionally, I would like to make the GUI acknowledge whenever "do_sth_to_let_GUI_know" is called using the qtlab shell. Would some of you give me some advice on how to implement this functionality? I will really appreciate it.

Regards,
Chunqing Deng

Re: [Qtlab-users] question on "Remote_Instrument"

[Reinier H. <re...@he...>]

Dear all,

We recently had some server issues, and the latest QTlab versions are
now available at http://qtwork.tudelft.nl/git

I also integrated the instrument sharing functionality in a much
better way now. That makes it very easy to use an instrument on one
computer that is physically connected to another one. Documentation
for how to use it is in the wiki:
https://sourceforge.net/apps/mediawiki/qtlab/index.php?title=Sharing_instruments

Please continue to send new instrument drivers to the list or me directly!

Regards,
Reinier

On Mon, Apr 23, 2012 at 5:05 PM, Chunqing Deng <cd...@iq...> wrote:
> Dear Qtlab users,
>
>
>
> First, I would like to thank the qtlab developing term for providing such a
> versatile and power measurement platform. My name is Chunqing Deng. I am a
> Ph.D student in Superconducting Quantum Device group in University of
> Waterloo.
>
>
>
> Now I have a question considering some remote control function, through
> which we can run measurement scripts from computers which are not directly
> connected to the instruments. I looked at the qtlab source code and found an
> Instrument called "Remote_Instrument" but I am not sure how to use it. So I
> would like to ask the experienced users for some ideas about how to use this
> remote_instrument. I will be very grateful if someone could help me or
> provide some sample codes.
>
>
>
> I am also very happy to contribute to the qtlab community. I will upload
> more drivers once they are finished and tested properly in our lab.
>
>
>
> Best regards,
>
>
>
> Chunqing Deng
>
>
>
> Institute for Quantum Computing
>
> Department of Physics and Astronomy
>
> University of Waterloo
>
> Office: RAC 2003
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
>
> _______________________________________________
> Qtlab-users mailing list
> Qtl...@li...
> https://lists.sourceforge.net/lists/listinfo/qtlab-users
>



-- 
Reinier Heeres
Tel: +31 6 10852639

Re: [Qtlab-users] question on "Remote_Instrument"

[Reinier H. <re...@he...>]

Dear Chunqing,

Thanks for your mail, and of course great that QTLab is working well for you!

First of all: on which version of QTlab are you? I hope already on
0.3, where the gui and the "main qtlab console" are in separate
processes. (Looking at the VERSION file or typing qt.version() in
QTlab should tell you).

The 'Remote_Instrument' code can be improved to use the client/server
approach present in v0.3. I completely forgot about this, but I can
try to fix that in a week or two; it shouldn't be very hard and will
simplify things quite a bit. However, in the mean time there are two
approaches you could take:

1. The Remote_Instrument approach. (You might need to fix
source/lib/network/tcpserver.py, line 36: "allowed_ip='.*'"). (I would
recommend this one).

In the QTLab that contains an instrument you would like to use on
another machine, type:

    from lib.network import remote_instrument
    remote_instrument.start_server()

This will start a listener on a TCP/IP port for connections from other
computers; be sure that the firewall allows this.

On the other machine, either:

    ins = qt.instruments.create('remote_test', 'Remote_Instrument',
remote_name='ins1', host='10.0.0.2')

or:

    from lib.network import remote_instrument
    remote_instrument.create_all('10.0.0.2')

2. Directly use the instrument as a SharedObject. The disadvantage is
that the instrument will not "really" look like an instrument to the
client QTlab and therefore you cannot use the instrument from the gui
there.
On the QTLab where you want to use an instrument from another computer, type:

    from lib.network import object_sharer as objsh
    objsh.start_glibtcp_client('10.0.0.2')
    ins = objsh.find_object('instrument_INSNAMEHERE')

Let me know if you run into any problems.

Regards,
Reinier

PS: looking forward to your drivers or other code you'd like to share with us.

On Mon, Apr 23, 2012 at 5:05 PM, Chunqing Deng <cd...@iq...> wrote:
> Dear Qtlab users,
>
>
>
> First, I would like to thank the qtlab developing term for providing such a
> versatile and power measurement platform. My name is Chunqing Deng. I am a
> Ph.D student in Superconducting Quantum Device group in University of
> Waterloo.
>
> Now I have a question considering some remote control function, through
> which we can run measurement scripts from computers which are not directly
> connected to the instruments. I looked at the qtlab source code and found an
> Instrument called "Remote_Instrument" but I am not sure how to use it. So I
> would like to ask the experienced users for some ideas about how to use this
> remote_instrument. I will be very grateful if someone could help me or
> provide some sample codes.
>
> I am also very happy to contribute to the qtlab community. I will upload
> more drivers once they are finished and tested properly in our lab.
>
> Best regards,
>
>
> Chunqing Deng
>
>
>
> Institute for Quantum Computing
> Department of Physics and Astronomy
> University of Waterloo
> Office: RAC 2003


-- 
Reinier Heeres
Tel: +31 6 10852639

[Qtlab-users] question on "Remote_Instrument"

[Chunqing D. <cd...@iq...>]

Dear Qtlab users,

 

First, I would like to thank the qtlab developing term for providing such a
versatile and power measurement platform. My name is Chunqing Deng. I am a
Ph.D student in Superconducting Quantum Device group in University of
Waterloo. 

 

Now I have a question considering some remote control function, through
which we can run measurement scripts from computers which are not directly
connected to the instruments. I looked at the qtlab source code and found an
Instrument called "Remote_Instrument" but I am not sure how to use it. So I
would like to ask the experienced users for some ideas about how to use this
remote_instrument. I will be very grateful if someone could help me or
provide some sample codes.

 

I am also very happy to contribute to the qtlab community. I will upload
more drivers once they are finished and tested properly in our lab.

 

Best regards,

 

Chunqing Deng

 

Institute for Quantum Computing

Department of Physics and Astronomy

University of Waterloo

Office: RAC 2003

 

 

[Qtlab-users] QTLab

[Reinier H. <re...@he...>]

Dear QTlab users,

This is the first serious mail we're sending to the qtlab-users
mailing list. We'd like to share some of the recent progress with you
as well as motivate you to send relevant code back to us. Welcome to
new list members btw: we subscribed some people we suspect to use
QTlab, but if you don't want to be on the list you can remove yourself
here: https://lists.sourceforge.net/lists/listinfo/qtlab-users.
Questions and comments can also be posted to this list!

So, for the new stuff:

- Many people are still on the 'old' qtlab (v0.2), which had the gui
and the 'shell' (where you type commands and run scripts) in the same
process. The latest version (on git here:
http://qtwork.nano.tudelft.nl/cgi-bin/gitweb.cgi?p=qtlab;a=summary)
has this separated in 2 processes. This is much better for stability
and both gui and shell response time. We are going to make a new
'release' version of 0.3 soon.

- The new version of course has many bug-fixes, but is certainly not
bug-free. If you run into trouble, please report it at
https://sourceforge.net/tracker/?atid=1166556&group_id=274525&func=browse

- New instruments are added continuously, see
http://qtwork.nano.tudelft.nl/cgi-bin/gitweb.cgi?p=qtlab;a=tree;f=instrument_plugins;h=d7a876c76f53889a7dee137cb7b809e4da4a13c9;hb=d1e2f78de1cd7c21130f09efb1b846efd7cc2336
for the current list.

This also brings us to the next point: we'd like to motivate you to
contribute back to QTlab. The easiest components to contribute are
instrument drivers and there probably are many candidates around. You
can always send these to Pieter or Reinier (or to this list): we're
more than happy to have a quick look, perhaps fix some small things
and put it in git. This way other users can also profit from your
work! Other extensions that come to mind are COM object or DLL
interfaces, file readers, gui extensions or math libraries (all of
which live in source/lib). This will make life easier and more
pleasant for all QTlab users.

Of course new ideas are also welcome, but our time is limited so
unfortunately we cannot guarantee that we can realize them (all).
However, QTlab was intended as a shared project, so do not hesitate to
implement things yourself.

We believe QTlab at the moment is a pretty stable set of components
and does the trick for most experiments.

Happy measuring!

Regards,
Reinier and Pieter

[Qtlab-users] test2

[Pieter C. de G. <pie...@gm...>]

test mail