ubii-node-python 0.3.1.dev2
Ubi Interact Python Node
Requires Python: >=3.7
Keywords: ubi-interact,ubii,distributed,vr,augmented

Ubi Interact Python Node
========================

This project implements the
`Ubi-Interact <https://github.com/SandroWeber/ubi-interact>`__ Protocol
in Pyhton. Ubi Interact is a framework developed at TUM (Technical
University of Munich) for developing distributed and reactive
applications, the main focus of the Python node is to allow the
implementation of ``processing-modules`` in Python.

Documentation is available `here <https://ubii-node-python.readthedocs.io/en/develop/>`_.

Installation
------------

Python Version
~~~~~~~~~~~~~~

The ``Ubi-Interact-Python-Node`` should be compatible with all python
versions **>= 3.7**. If you experience bugs feel free to report them.

Windows:
~~~~~~~~

The ``Ubi-Interact-Python-Node`` aims to be cross-platform, working with
most interesting computational packages is easier under Linux
nonetheless. Installation via ``pip`` is recommended, if you use
something else (e.g.``Anaconda``) refer to the documentation of your
python distribution / package management tool how to install packages
from pypi.

You can use the Windows python wrapper ``py.exe`` (detailed instructions
in the `Python
Documentation <https://docs.python.org/3/using/windows.html>`__) to
choose the python version of your environment.

   If you plan to use a virtual environment - which is recommended -
   typically an *Unrestricted* execution policy is needed to run the
   activation script for the python environment. The following
   instructions assume you are using *Powershell*, and have the right
   `ExecutionPolicy <https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies>`__
   set.

-  Python version 3.7 or greater
-  Virtual Environment (recommended) with pip installed
   (``py -m venv env`` followed by ``./env/Scripts/activate.ps1``)
-  Continue at `PyPi <#pypi>`__

Linux (and MacOS)
~~~~~~~~~~~~~~~~~

If you are not using Windows, you probably have a working python
installation. Sometimes the different versions have aliases such as
``python3``, so make sure to create the virtual environment with the
appropriate python executable (or specify the executable for the
environment during creation).

-  Python version 3.7 of greater
-  Virtual Environment (recommended) with pip installed
   (e.g.``python3 -m venv env`` followed by
   ``source ./env/bin/activate``)
-  Continue at `PyPi <#pypi>`__

PyPi
~~~~

After activating the environment, install the package from pypi. The
package supplies different `extras <#extras>`__, to install additional
dependencies for optional features. You can make sure everything is
working correctly by calling the ``ubii-client`` script which gets
installed as part of the ``cli`` extra.

::

   $ python -m pip install ubii-node-python[cli]
   $ ubii-client --help

Editable / Local Install
~~~~~~~~~~~~~~~~~~~~~~~~

Instead of installing from PyPi you can clone the repository and install
the package “from source”. Editable installs are supported.

::

   $ git clone git@github.com:SandroWeber/ubii-node-python.git
   $ cd ubii-node-python
   $ < create and activate virtual env >
   $ pip install -e .[cli]
   $ ubii-client --help

Extras
~~~~~~

This packages uses
`extras <https://www.python.org/dev/peps/pep-0508/#id12>`__.

-  ``[test]`` Requirements to run ``pytest`` suite if you install the
   package from source, and not from PyPi

      Currently the ``[test]`` extra depends on some processing-module
      packages. Make sure you have all requirements installed
      (especially on Windows some processing dependencies are not in
      pypi)

-  ``[cli]`` Installs a `CLI <#CLI>`__ script which runs the node and
   auto-discovers installed Processing Modules (see
   `below <#processing-modules>`__)

-  ``[docs]`` Install requirements to build documentation

Usage
-----

To use the ``ubii-node-python`` package to implement your own python
nodes refer to the `package
documentation <#ubi-interact-python-node>`__. To start a python client
refer to `CLI <#CLI>`__.

CLI
~~~

Basic functionality is provided through a command line interface which
allows to run a python node which is able to import and load processing
modules.

::

   $ ubii-client --help

   usage: ubii-client [-h]
                      [--processing-modules PROCESSING_MODULES]
                      [--verbose] [--debug]
                      [--log-config LOG_CONFIG]

   options:
     -h, --help            show this help message and exit
     --processing-modules PROCESSING_MODULES
     --no-discover
     --verbose, -v
     --debug
     --log-config LOG_CONFIG

(non obvious) arguments:

-  ``--debug`` Debug mode changes the exception handling, and increases
   verbosity. In debug mode the Node does not try to handle exceptions,
   and fails loudly
-  ``--log-config`` optional path to a **.yaml** file containing a
   dictionary of logging options consistent with the
   ```logging.config.dictConfig`` <https://docs.python.org/3/library/logging.config.html#logging.config.dictConfig>`__
   format (`example
   config <src/ubii/framework/util/logging_config.yaml>`__)
-  ``--no-discover`` flag to turn off auto discovery of processing
   modules via entry points
-  ``--processing-modules`` specify a list of import paths for *Ubi
   Interact Procesing Modules* implemented using the
   ``ubi-interact-python`` framework, see
   `processing-modules <#processing-modules>`__. Use it together with
   `auto discovery <#processing-modules>`__ during development or as a
   fallback


Processing Modules
^^^^^^^^^^^^^^^^^^

Below is a list of processing modules that are compatible with the
python node. To try them, install them inside the same virtual
environment (refer to the documentation of the specific module). If you
develop new Processing Modules, use the entry point group
*ubii.processing_modules* to advertise them in your package, so that the
``ubii-client`` script (or your own implementation) can discover them.
Read the ``setup.cfg`` configs of the example modules below and the
`setuptools
documentation <https://setuptools.pypa.io/en/latest/userguide/entry_point.html>`__
for more details.

-  `ubii-ocr-module <https://github.com/saggitar/ubii-processing-module-ocr>`__

Example usage after install of module:

::

   $ pip install ubii-processing-module-ocr
   $ ubii-client
   > Loaded processing module factories <class 'ubii.processing_modules.ocr.tesseract_ocr.TesseractOCR_EAST'>, ...
   > ...

or with cli argument to only load specific processing modules (also
turning off auto discovery in this example)

::

   $ pip install ubii-processing-module-ocr
   $ ubii-client --no-discover --processing-modules ubii.processing_modules.ocr.tesseract_ocr.TesseractOCR_EAST
   > Loaded processing module factories <class 'ubii.processing_modules.ocr.tesseract_ocr.TesseractOCR_EAST'>
   > ...

0.2.0a1.dev29 (2022-04-01)
==========================

Documentation
-------------
- Updated documentation of ``codestare.async_utils`` module


0.2.0a1.dev22 (2022-03-25)
==========================

Bug Fixes
---------
- Fixed bug introduced by changed json backend URL that was not correctly propagated during client runtime


0.1.0 (2022-03-25)
==================

New Features
------------
- Auto reconnect when master node shuts down

Bug Fixes
---------
- Fixed package name refactoring breaking some imports

- Fixed bug introduced by changed json backend URL that was not correctly propagated during client runtime

- Fixed additional errors caused by renaming


0.1.0 (2022-03-25)
==================

New Features
------------
- Auto reconnect when master node shuts down

Bug Fixes
---------
- Fixed package name refactoring breaking some imports

- Fixed additional errors caused by renaming


0.2.0.a1.dev13 (2022-02-16)
===========================

New Features
------------
- Auto reconnect when master node shuts down

Bug Fixes
---------
- Fixed package name refactoring breaking some imports

- Fixed additional errors caused by renaming


0.2.0.a1.dev3 (2022-02-02)
==========================

Documentation
-------------
- Setting up documentation and Changelog



BSD 3-Clause License

Copyright (c) 2022, Maximilian Schmidt (ga97lul@mytum.de)
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

- Redistributions of source code must retain the above copyright notice, this
  list of conditions and the following disclaimer.

- Redistributions in binary form must reproduce the above copyright notice,
  this list of conditions and the following disclaimer in the documentation
  and/or other materials provided with the distribution.

- Neither the name of the copyright holder nor the names of its
  contributors may be used to endorse or promote products derived from
  this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.