Description
pyComtrade is a python module that provides you a transparent way for reading and writing (not implemented yet) oscillographic files stored in IEEE Comtrade format.
Comtrade stands for COMmon format for Transient Data Exchange for power systems. It is a file format standardised by the IEEE that is used to store transient signals from Digital Fault Recorders, Oscillographs or Digital Protective Relays.
pyComtrade was created and maintained by Miguel Moreto at Federal University of Santa Catarina - Brazil
Feel free to use the module in your program. Don’t forget that pyComtrade is licensed under the GNU version 3 license. For more info about this read the COPYING.txt.
Release Notes
Version 0.3.0 - Added ASCII data file support. - Source code refactored. - Changed metadata handling from lists to dictionaries. - Python 3 support.
Many thanks to the contributors @ldemattos and @bluesdog164 who made most of the changes for this release.
Version 0.2.0
Implemented a method to read digital channels.
Updated example.
Added one more test data with digital channel data.
Version 0.1.0
Reads only analog channels.
Reads only binary Comtrade files (1999 Standard).
To Do
Review the last version of Comtrade Standard C37.111-2013.
Write Comtrade files.
Install
Pip
Run pip install pyComtrade from the command line.
From source (windows and linux)
Extract the source .zip file.
Run:
python.exe setup.py install
Usage
See example1.py at the source file.
Thanks for using pyComtrade module.
1 maintainer
Metadata
1 maintainer
Release files for pyComtrade 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyComtrade-0.3.1-py3.8.egg | Legacy Egg format | - | - | Details |
Release files / pyComtrade-0.3.1-py3.8.egg
| Download URL | pyComtrade-0.3.1-py3.8.egg |
|---|---|
| Size | 12.9 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
d520ea3f7c8c4fdc8f5b398ab86ed1352a7be327a61d516e012001db3b59f581
|
|
BLAKE2b-256 checksum How to use checksums |
7f1bb057d7ce5791f9c20d0ca5af5bbd35c1777da6e807ab3aa58713c51eeed2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.4.2 requests/2.22.0 setuptools/45.2.0 requests-toolbelt/0.8.0 tqdm/4.30.0 CPython/3.8.10
|
Security for pyComtrade 0.3.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.
