dora-rs
/
dora
Not watched
1
0
Fork 0
Code
Releases 124 Wiki evaluate Activity
Issues 0 Pull Requests 0 Datasets Model Cloudbrain HPC
You can not select more than 25 topics Topics must start with a chinese character,a letter or number, can include dashes ('-') and can be up to 35 characters long.
2400 Commits
57 Branches
16 MB
7734 Download
Tree: 0e8a47e8b5
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '0e8a47e8b5'
${ noResults }
dora/apis/python/node/README.md

README.md 339 B
Raw Normal View History

Adding `next`, `send_output` for Python node API Adding `next` and `send_output` requires an async threadpool as the communication Layer defined by the Middleware Layer returns an async Future stream. I solve this issue by adding a tokio runtime on a separater thread that is connected with two channels. One for sending data and one for receiving data. Those channel are then exposed synchronously to Python. This should not be cause for concern as channel are really fast. Looking at Zenoh Python client, they are heavily using `pyo3-asyncio` implementation of futures to pass Rust futures into Python. This can be a solution as well, but, from previous experiment, I'm concerned about performance on such solution. I have experienced that putting futures from Rust into the `asyncio` queue to be slow. I'm concerned also by mixing `async` and `sync` code in Python, as it might be blocking. This might requires 2 threadpool in Python. This might seem as heavy overhead for some operations.
3 years ago
​
​
​
​
​
Remove explicit statement to `python3`and resolve it instead
2 years ago
​
Adding `next`, `send_output` for Python node API Adding `next` and `send_output` requires an async threadpool as the communication Layer defined by the Middleware Layer returns an async Future stream. I solve this issue by adding a tokio runtime on a separater thread that is connected with two channels. One for sending data and one for receiving data. Those channel are then exposed synchronously to Python. This should not be cause for concern as channel are really fast. Looking at Zenoh Python client, they are heavily using `pyo3-asyncio` implementation of futures to pass Rust futures into Python. This can be a solution as well, but, from previous experiment, I'm concerned about performance on such solution. I have experienced that putting futures from Rust into the `asyncio` queue to be slow. I'm concerned also by mixing `async` and `sync` code in Python, as it might be blocking. This might requires 2 threadpool in Python. This might seem as heavy overhead for some operations.
3 years ago
​
​
Remove explicit statement to `python3`and resolve it instead
2 years ago
Adding python IDE typing
1 year ago
​
​
​
​
​
Using `__init__.py` as without using it
1 year ago
Adding python IDE typing
1 year ago
​
 123456789101112131415161718192021 
  1. This crate corresponds to the Node API for Dora.

  2. 

  3. ## Building

  4. 

  5. To build the Python module for development:

  6. 

  7. ```bash

  8. python -m venv .env

  9. source .env/bin/activate

  10. pip install maturin

  11. maturin develop

  12. ```

  13. 

  14. ## Type hinting

  15. 

  16. Type hinting requires to run a second step

  17. 

  18. ```bash

  19. python generate_stubs.py dora dora/__init__.pyi

  20. maturin develop

  21. ```

DORA (Dataflow-Oriented Robotic Architecture) is middleware designed to streamline and simplify the creation of AI-based robotic applications. It offers low latency, composable, and distributed datafl