lmlib
Open-source and for Python
A Model-Based Signal Processing Library Working With Windowed Linear State-Space and Polynomial Signal Models.
Website and Documentation: lmlib.ch
Direct Links to:
Install lmlib
-
pip:
pip install lmlib -
conda: see here
Developer Info
Installation via:
- pip (dev-mode):
pip install -e lmlib - Git Workflow Guide
How to build documenation
python3.14 -m venv venv
source venv/bin/activate
pip install -r requirements.txt
- create gallery
python scripts/create_gallery.py
- build doc
mkdocs build -c
- livereload
mkdocs serve --livereload -c
Deployment Documentation
The automated pipeline consists of four sequential jobs:
1. release Job (tags only):
- Triggered by: Tags matching refs/tags/*
- Purpose: Creates a GitHub release with tag message as notes
- Outputs: Official release on GitHub
2. build_gallery Job
- Triggered by: Any push to develop or tags
- Purpose: Generates gallery documentation from code examples
- Output: docs/_generated folder as artifact
3. build_mkdocs Job
- Prerequisite: build_gallery must succeed
- Purpose:
- Downloads generated docs from previous step
- Creates API documentation and changelog
- Replaces version placeholders with actual version
- Builds the complete MkDocs site
- Output: ./site folder as artifact
4. deploy Job
- Prerequisite: build_mkdocs must succeed
- Purpose: Deploys the built site to GitHub Pages
- Destination: gh-pages branch
- Result: Documentation becomes live at your GitHub Pages URL
How to trigger new release:
git push -a vX.X.X
- Then a text editor opens for release notes (make double newlines for a newline in the release notes of github)
this is a new major release:
* new feature
* removed functions
* faster backend
How to change release notes in news:
- Update release notes directly on github page and save
- Rerun job 3. build_mkdocs. this will update the news website with the latest release notes.
How to make changes on documenation without release:
- Push main branche with newest documentation
Metadata
Release files for lmlib 3.0.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 | |
|---|---|---|---|---|
| lmlib-3.0.1.tar.gz | 13.0 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lmlib-3.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.0 MB
Release files / lmlib-3.0.1.tar.gz
| Download URL | lmlib-3.0.1.tar.gz |
|---|---|
| Size | 13.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
75f9a949e9d13c80e1e0de15417364ad4b9e1228389b1b828e36e8a7f61d4da7
|
|
BLAKE2b-256 checksum How to use checksums |
761ddfa79769fceb13fefd7c25dee720542de3e84f85ac4c6ca4c998c73cc6bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Release files / lmlib-3.0.1-py3-none-any.whl
| Download URL | lmlib-3.0.1-py3-none-any.whl |
|---|---|
| Size | 6.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6b5d0c21572e6a4465c868541afda43229fe67b1c82d29df1e3797d28ff9ff65
|
|
BLAKE2b-256 checksum How to use checksums |
fd1fd9cb249dc1df65b0f94f0d3ce38cab0decd0c6ca8faff3bad1bbee5a6dc7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Security for lmlib 3.0.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.