kalibrate
Python wrapper for Kalibrate.
Returns scan data in structured format.
Example usage:
import kalibrate
scanner = kalibrate.Kal("/usr/local/bin/kal")
# Scan a band
band_results = scanner.scan_band("GSM850", gain=45)
# Scan a channel
channel_results = scanner.scan_channel("232", gain=45)
And what you get for scanning a band:
[{'band': 'GSM-850',
'base_freq': 869200000.0,
'channel': '128',
'channel_detect_threshold': '259970.196875',
'device': '0: Generic RTL2832U OEM',
'final_freq': '869175933',
'gain': '45.0',
'mod_freq': 24067.0,
'modifier': '-',
'power': '299318.41',
'sample_rate': '270833.002142'},
{'band': 'GSM-850',
'base_freq': 890000000.0,
'channel': '232',
'channel_detect_threshold': '259970.196875',
'device': '0: Generic RTL2832U OEM',
'final_freq': '890022169',
'gain': '45.0',
'mod_freq': 22169.0,
'modifier': '+',
'power': '780303.16',
'sample_rate': '270833.002142'}]
Channel scan results:
{'device': '0: Generic RTL2832U OEM',
'channel': '232',
'band': 'GSM-850',
'gain': '45.0',
'sample_rate': '270833.002142',
'frequency': '890MHz',
'average_absolute_error': '-33.445',
'measurements':
['29921.37',
'29952.37',
'29900.71'],
'raw_scan_result': 'ORIGINAL FULL SCAN BODY GOES HERE'}
Note: Kalibrate’s output for this feature starts numbering with offset 1. This abstraction starts at 0, because that’s how Python numbers things. So you’ll find your measurement for the first offset labeled “offset 1:” in the original output, and in channel_scan[“measurements”][0] in the output of the channel scan. This format is new in version 2 of this library, and is a breaking change from the way v1 presented this information.
v2.1.0 (2018-12-25)
Changes
Adding build, coverage, and quality badges to README.rst. [Ash Wilson]
Python 3.6, 3.7 compatibility. [Ash Wilson]
Other
Create pyup.io config file. [pyup-bot]
v2.0 (2018-10-17)
Changes
Better-structured format for channel scans. [Ash Wilson]
Adding CodeClimate config. [Ash Wilson]
Removing Python2.6 because this ain’t the antique roadshow.
Closes #3
Add “avg_absolute_error” to scan_channel() output. [Ash Wilson]
v1.1.1 (2017-01-06)
Update travis. [ashmastaflash]
Metadata
Release files for kalibrate 2.2.1
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 |
|---|---|---|---|---|
| kalibrate-2.2.1.tar.gz | 5.3 kB | Without provenance | Details for kalibrate-2.2.1.tar.gz |
Release files / kalibrate-2.2.1.tar.gz
| Download URL | kalibrate-2.2.1.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d159c2040cbb864e5644f0fa49547f723bb32fc15b4477d9ed4d07199ef03c02
|
|
BLAKE2b-256 checksum How to use checksums |
7403f4872541d82d9933398a51e164d346cd85d19f8d69e854a935351f6b984e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/42.0.2 requests-toolbelt/0.9.1 tqdm/4.41.0 CPython/2.7.15
|
Security for kalibrate 2.2.1
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.