k7
CCBY: Cassette by Alvaro Cabrera from the Noun Project
Usage
Check file format
python -m k7.k7 --check myfile.k7
k7 format
{"location": "grenoble", "tx_length": 100, "start_date": "2018-01-11 16:32:22", "stop_date": "2018-01-13 16:21:30", "node_count": 44, "channels": [11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26], "interframe_duration": 100}
datetime,src,dst,channel,mean_rssi,pdr,tx_count
2018-01-11 16:33:07,18,19,11,-53.2,1.0
2018-01-11 16:33:07,17,14,11,-84.03,0.97
2018-01-11 16:33:07,23,27,11,-83.88,1.0
2018-01-11 16:33:30,16,14,11,-67.03,1.0
2018-01-11 16:33:30,22,49,11,-70.0,1.0
...
Header
Each k7 starts with a one-line header. The header is the json dump of a dict. The header contains the dataset meta data. Ex:
{"location": "grenoble", "tx_length": 100, "start_date": "2017-06-20 16:22:15", "stop_date": "2017-06-21 10:29:29", "node_count": 50, "channels": [11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26], "interframe_duration": 10}
Data
| datetime | src | dst | channel | mean_rssi | pdr | tx_count |
|---|---|---|---|---|---|---|
| iso8601 string | int | int | int | float | float (0-1) | int |
Standard example:
| datetime | src | dst | channel | mean_rssi | pdr | tx_count |
|---|---|---|---|---|---|---|
| 2017-12-19 21:35:41 | 0 | 1 | 11 | -74.5 | 1.0 | 100 |
The source or destination can be empty (i.e when measured on all the neighbors of the src):
| datetime | src | dst | channel | mean_rssi | pdr | tx_count |
|---|---|---|---|---|---|---|
| 2017-12-19 21:35:41 | 11 | -74.5 | 0.7 | 100 |
Unknown channel:
| datetime | src | dst | channel | mean_rssi | pdr | tx_count |
|---|---|---|---|---|---|---|
| 2017-12-19 21:35:41 | 1 | 2 | -79.5 | 1.0 | 100 |
When the channel value is empty, it means that the channel is unknown for that measurement.
Metadata
Release files for k7 0.4.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 | |
|---|---|---|---|---|
| k7-0.4.2.tar.gz | 4.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| k7-0.4.2-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 9.3 kB
Release files / k7-0.4.2.tar.gz
| Download URL | k7-0.4.2.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a4cbba266c177370d5c88b51ef59b22c3a84f9c245ce2beaadd2b19e5af2474f
|
|
BLAKE2b-256 checksum How to use checksums |
b4252b2411d1f161b0106095b78c4298e2cdf6347d9fd5a71054316ace2bfc89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.18.4 setuptools/39.1.0 requests-toolbelt/0.8.0 tqdm/4.19.9 CPython/2.7.15rc1
|
Release files / k7-0.4.2-py2-none-any.whl
| Download URL | k7-0.4.2-py2-none-any.whl |
|---|---|
| Size | 4.9 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
4d8e52e29fa2b495b0df907d0d974a523ada3dc5166b2e1a588199a2e63ffe82
|
|
BLAKE2b-256 checksum How to use checksums |
2e046f4e92849a445759335de8e0708f69ca7bf25ad620646975f8484db8764a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.18.4 setuptools/39.1.0 requests-toolbelt/0.8.0 tqdm/4.19.9 CPython/2.7.15rc1
|
Security for k7 0.4.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.