This is the backbone of my (Isaac Robinson) high school research project. The idea is that drones have limited processing power and so cannot actually do very intensive tasks on their own. My solution to this problem was to make each drone borrow CPU time from other drones in a swarm when necessary. The method essentially changes the architecture of the system from a bunch of individual drones in a swarm to a computational cluster just long enough to get an intensive task done. This saves money, power, and makes it possible to use low-power drones for high-power tasks.
I chose to demonstrate this idea by creating a trigger which would alert a drone of the precense of something requiring more intensive processing, and then distributing this processing. For me, the intensive processing so far is facial detection. I have shown this method to be highly effective, and am currently in the process of improving it.
I am also building real drones to demonstrate this idea. My project is documented at sites.google.com/site/paralleldrone.
If you have any questions or comments, please feel free to contact me at isaacrob@me.com.
Metadata
Release files for distdrone3 0.0.2
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 |
|---|---|---|---|---|
| distdrone3-0.0.2.tar.gz | 18.5 kB | Without provenance | Details for distdrone3-0.0.2.tar.gz |
Release files / distdrone3-0.0.2.tar.gz
| Download URL | distdrone3-0.0.2.tar.gz |
|---|---|
| Size | 18.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3a4841b91a686d5d4e4604370ad961f1cb5fbcb095f3d29638eec7fd9d08319d
|
|
BLAKE2b-256 checksum How to use checksums |
9e5b853f81b85917df34f6d568648ba0f76d8490b8341e04ed0613925877ff8f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for distdrone3 0.0.2
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.