eml-signal
eml-signal is a small pure-Python package of bounded signal-processing
kernels and contract metadata for EML-style workflows.
The v0 package focuses on deterministic list-based kernels that are easy to test, inspect, and use in synthetic examples for Monowave, Field Kernel Lab, and EML course material.
It does not process copyrighted audio assets, make wellness or medical claims, or claim production DSP or real-time performance.
Kernels
envelope_followerone_pole_lowpassband_energy_toymoving_average_filterzero_crossing_ratehighpass_differenceconvolution_1d
Each kernel returns a SignalResult with values or features, an
operation_count, and a compact contract dictionary.
CLI
eml-signal --help
eml-signal demo envelope
eml-signal demo lowpass
eml-signal demo band-energy
eml-signal validate examples/signal_contract.json
eml-signal examples
eml-signal validate-example signal_contract
validate <path> reads a local contract file. Installed packages also include
bundled examples; use examples to list them and validate-example to validate
one without relying on a source-tree examples/ directory.
Python
from eml_signal import envelope_follower, one_pole_lowpass
signal = [0.0, 0.25, -0.5, 1.0, -0.25]
envelope = envelope_follower(signal, alpha=0.2)
smooth = one_pole_lowpass(signal, alpha=0.25)
print(envelope.operation_count)
print(smooth.values)
Monowave Bridge
The optional Monowave bridge maps bounded synthetic signals into the same broad feature names used by Monowave scenes:
input_levelbass_drivemid_drivetreble_drive
from eml_signal import monowave_feature_summary
features = monowave_feature_summary([0.0, 0.25, -0.5, 0.75])
print(features["features"])
This bridge is for synthetic fixtures and contract checks. It is not a wellness, treatment, production DSP, or real-time performance claim.
Boundaries
- synthetic examples only in v0;
- no therapy, medical, healing, brainwave, entrainment, or consciousness claims;
- no copyrighted audio fixtures;
- no production DSP claim;
- no real-time/mobile performance claim.
Metadata
Release files for eml-signal 0.1.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 |
|---|---|---|---|---|
| eml_signal-0.1.1.tar.gz | 10.8 kB | Without provenance | Details for eml_signal-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| eml_signal-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for eml_signal-0.1.1-py3-none-any.whl |
Total release size: 23.0 kB
Release files / eml_signal-0.1.1.tar.gz
| Download URL | eml_signal-0.1.1.tar.gz |
|---|---|
| Size | 10.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bbc141b00ac58c1ce83977475d2307b98b07437bd7d82ade9a8326eacc4af18d
|
|
BLAKE2b-256 checksum How to use checksums |
ec22a1c2c79afff6f647cd6eb999a100d856d981e6675441333ef50fcc09cb2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Release files / eml_signal-0.1.1-py3-none-any.whl
| Download URL | eml_signal-0.1.1-py3-none-any.whl |
|---|---|
| Size | 12.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
65c106e6f2592aa926899cc4d2cdf4de6c09e52d14cc03db054968bf6b854954
|
|
BLAKE2b-256 checksum How to use checksums |
9acf4f3547dc860af47775dad7cdd22883abdc762d015ec6094514625ac5a442
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Security for eml-signal 0.1.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.