EDeA Measurement Server
edea-ms provides an API and user interface for planning, executing and analyzing measurement data for electronics engineering purposes. It allows engineering teams or collaborating individuals to automate tests and share results in a unified way, be it for board bringup, silicon evaluation or other test and measurement tasks.
This project is based on the original EDeA Project proposal and takes further inspiration from the TestOps Manifesto by Keysight.
Current Status
We're using and developing this at Fully Automated for our OSHW and consulting projects. It's in a usable state, but currently only used internally. If you intend to use this, please contact us so we can understand the usecase of other engineering teams better.
Running it
To make it as easy as possible to use, we've published a package on pypi which can just be installed like this:
pip install edea_ms
# or with optional dependencies for rendering charts server-side
pip install "edea_ms[optional]"
And it can be run locally like this:
python -m edea_ms --local
This starts a webserver which is only reachable on the local machine without any user authentication to keep it simple for single user installs or just trying it out. To set up authentication to collaborate with others in a team see the docs on Authentication.
Development
To run the server from the repository, it needs both the backend and the frontend like this:
# run the server
rye run uvicorn edea_ms.main:app --reload
# run the frontend
npm run dev
Building the package
In case you want to bundle a modified frontend into your own package, simply run:
npm run build # this will compile the frontend to static files
rye build --wheel # to build the final wheel with the frontend embedded in it
Measurement Client
See the EDeA TMC project for a library with which one can write test programs with.
Licenses
The server code is licensed under the EUPL-1.2 license and the frontend code is licensed under the MIT license. Images and artwork are licensed under CC BY-ND 4.0.
Linking the server code (e.g. using it as a library) is allowed under the EUPL-1.2, even for commercial use. Modifications should be shared but the server code is structured in a way that it can easily be integrated in other systems (internal or otherwise) without modifying the core.
If you want to host a modified frontend internally or externally, please replace the logos so that it's clear that it is a modified distribution.
Metadata
Release files for edea-ms 0.3.0
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 |
|---|---|---|---|---|
| edea_ms-0.3.0.tar.gz | 37.2 kB | Without provenance | Details for edea_ms-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| edea_ms-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for edea_ms-0.3.0-py3-none-any.whl |
Total release size: 1.8 MB
Release files / edea_ms-0.3.0.tar.gz
| Download URL | edea_ms-0.3.0.tar.gz |
|---|---|
| Size | 37.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bf0b176913d493932eb29153f4655d6f40642c31b654166bbdd2b381aac0cd9e
|
|
BLAKE2b-256 checksum How to use checksums |
2763476fd1afcff82ea900b273a930dc5234751a4d29c2ae914f5a42ceb4435a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Release files / edea_ms-0.3.0-py3-none-any.whl
| Download URL | edea_ms-0.3.0-py3-none-any.whl |
|---|---|
| Size | 1.8 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
43dfd80cf9e11e735d8a0160f434545ec873a9bc7a673404c049d8673b816ee2
|
|
BLAKE2b-256 checksum How to use checksums |
739e98cdc15fc87e147f0f535c8cc7f1acfbc19f9ef38f6382e418929a8b3d7d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for edea-ms 0.3.0
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.