1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
|
# Copyright (c) DataLab Platform Developers, BSD 3-Clause license, see LICENSE file.
"""
DataLab Client (:mod:`sigima.client`)
-------------------------------------
The `sigima.client` module provides a proxy to DataLab application through XML-RPC
protocol.
DataLab may be controlled remotely using the `XML-RPC`_ protocol which is
natively supported by Python (and many other languages). Remote controlling
allows to access DataLab main features from a separate process.
From an IDE
^^^^^^^^^^^
DataLab may be controlled remotely from an IDE (e.g. `Spyder`_ or any other
IDE, or even a Jupyter Notebook) that runs a Python script. It allows to
connect to a running DataLab instance, adds a signal and an image, and then
runs calculations. This feature is exposed by the `sigima.client.SimpleRemoteProxy`
class.
From a third-party application
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
DataLab may also be controlled remotely from a third-party application, for the
same purpose.
If the third-party application is written in Python 3, it may directly use
:py:class:`cdlclient.SimpleRemoteProxy` as mentioned above. From another language,
it is also achievable, but it requires to implement a XML-RPC client in this
language using the same methods of proxy server as in the
:py:class:`cdlclient.SimpleRemoteProxy` class.
Data (signals and images) may also be exchanged between DataLab and the remote
client application, in both directions.
The remote client application may be run on the same computer as DataLab or on
different computer. In the latter case, the remote client application must
know the IP address of the computer running DataLab.
The remote client application may be run before or after DataLab. In the latter
case, the remote client application must try to connect to DataLab until it
succeeds.
Supported features
^^^^^^^^^^^^^^^^^^
Supported features are the following:
- Switch to signal or image panel
- Remove all signals and images
- Save current session to a HDF5 file
- Open HDF5 files into current session
- Browse HDF5 file
- Open a signal or an image from file
- Add a signal
- Add an image
- Get object list
- Run calculation with parameters
Example
^^^^^^^
Here is an example in Python 3 of a script that connects to a running DataLab
instance, adds a signal and an image, and then runs calculations (the cell
structure of the script make it convenient to be used in `Spyder`_ IDE):
.. literalinclude:: ../examples/features/datalab_client.py
Additional features
^^^^^^^^^^^^^^^^^^^
For simple remote controlling, :py:class:`sigima.client.SimpleRemoteProxy` may be
used. For more advanced remote controlling, the `datalab.control.proxy.RemoteProxy`
class provided by the DataLab package may be used.
See DataLab documentation for more details about the
``datalab.control.proxy.RemoteProxy`` class (on the section "Remote control").
.. _XML-RPC: https://docs.python.org/3/library/xmlrpc.html
.. _Spyder: https://www.spyder-ide.org/
API
^^^
Remote client
~~~~~~~~~~~~~
.. autoclass:: sigima.client.remote.SimpleRemoteProxy
:members:
Base proxy
~~~~~~~~~~
.. autoclass:: sigima.client.base.SimpleBaseProxy
:members:
"""
from sigima.client.base import SimpleBaseProxy
from sigima.client.remote import SimpleRemoteProxy
__all__ = ["SimpleBaseProxy", "SimpleRemoteProxy"]
# TODO: Refactor the `sigima.client` with `datalab.base` and `datalab.control.remote`
|
