loudify
Running a GNU Radio flowgraph in a ZMQ client <-> broker <-> worker setup.
Loudify: LoRa cloudified
Explore the docs »
Report a bug
Request a feature
Summary
This project consist of three different parts namely the client that is running a GNU Radio flowgraph, the worker receiving the data and doing the actual demodulation process and the broker connecting the two together. This repo holds the code for all the parts, be sure to check out gr-lora_sdr to see how this codes integrates into GNU Radio.
Docs
Documentation is built automatically on commits, and can be visited by going to docs
Why
This project together with the GNU Radio code located in gr-lora_sdr is part of my graduation project which is called a Centralized Radio Acces Network gateway for LoRa. Its purpose is to research if it is possible to be able to aggregate LoRa packets originating from different LoRa gateways by making a central point (aka the broker) that all gateways can connect to. The overall high level idea is to let LoRa gateways share information on the reception of their signals.
Installing
Installing the project can be done in two ways, by installing the normal PyPi release
pip install loudify
Or by installing directly from the repo either by doing pip git install
pip install git+https://github.com/martynvdijke/loudify.git
Or by cloning the repo and running flit install
pip install flit
git clone https://github.com/martynvdijke/loudify
cd loudify
flit install
Architecture
For a more detailed overview of the entire architecture and to be able to see how everything is connected visit architecture
Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change. Make sure to add or update tests as appropriate.
Changelog
Metadata
Release files for loudify 0.0.post30
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| loudify-0.0.post30.tar.gz | 4.6 MB | Without provenance | Details for loudify-0.0.post30.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| loudify-0.0.post30-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for loudify-0.0.post30-py2.py3-none-any.whl |
Total release size: 4.6 MB
Release files / loudify-0.0.post30.tar.gz
| Download URL | loudify-0.0.post30.tar.gz |
|---|---|
| Size | 4.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d67987742920e315b62e79fd0cb33d1ed54a901d870427aa3be9d9b4eb67e36d
|
|
BLAKE2b-256 checksum How to use checksums |
193dceef34cec4c93adda99a9f524025a45208b1caad5809b2ab9a60349ebbaa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.25.1
|
Release files / loudify-0.0.post30-py2.py3-none-any.whl
| Download URL | loudify-0.0.post30-py2.py3-none-any.whl |
|---|---|
| Size | 18.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
4d326e8e43a8477fcf864b3b813aff5a018235d0adf8bcb50a02a27ec462ba6c
|
|
BLAKE2b-256 checksum How to use checksums |
8efd5593a13f54856fb0191d72a9ba5c6cd467ca2c96e2601a0654fb4b98e4f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.25.1
|
Security for loudify 0.0.post30
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.