pyDigitalWaveTools
python library for operations with VCD and other digital wave files
Feature list
- parse VCD (std 2009) files to intermediate format
- write VCD files, user specified formatters for user types, predefined formatters for vectors, bits and enum values
- dump intermediate format as simple json
Hello pyDigitalWaveTools
Here is a simple example how to use the VCD parser:
#!/usr/bin/env python3
import json
import sys
from pyDigitalWaveTools.vcd.parser import VcdParser
if len(sys.argv) > 1:
fname = sys.argv[1]
else:
print('Give me a vcd file to parse')
sys.exit(-1)
with open(fname) as vcd_file:
vcd = VcdParser()
vcd.parse(vcd_file)
data = vcd.scope.toJson()
print(json.dumps(data, indent=4, sort_keys=True))
Output json format
scope
{ "name": "<scope name>"
"children" : {"<children name>" : child}
}
child can be scope or signal record
signal record
{ "name": "<signal name>"
"type": {"sigType": "<vcd signal type>",
"width": <bit width of signal (integer)>},
"data": [<data records>],
}
data record format
[<time (number)>, <value (string, format dependent on datatype)>]
Related open source
- verilog-vcd-parser - Python, A parser for Value Change Dump (VCD) files as specified in the IEEE System Verilog 1800-2012 standard.
- pyvcd - Python, vcd writer, GTKWave config writer
- vcdvcd - Python, vcd parser, dump pretty printer
Metadata
Release files for pyDigitalWaveTools 1.2
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 |
|---|---|---|---|---|
| pyDigitalWaveTools-1.2.tar.gz | 11.1 kB | Without provenance | Details for pyDigitalWaveTools-1.2.tar.gz |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyDigitalWaveTools-1.2-py3.10.egg | Legacy Egg format | - | - | Details for pyDigitalWaveTools-1.2-py3.10.egg |
| pyDigitalWaveTools-1.2-py3-none-any.whl | Python 3 | none | any | Details for pyDigitalWaveTools-1.2-py3-none-any.whl |
Total release size: 52.6 kB
Release files / pyDigitalWaveTools-1.2.tar.gz
| Download URL | pyDigitalWaveTools-1.2.tar.gz |
|---|---|
| Size | 11.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b09c1edad4ebe974341f20f1e8fae07166932a70071bdb9430765146e0e15ce1
|
|
BLAKE2b-256 checksum How to use checksums |
ab6e89fb3afa3e53b5955b68f14f2ab731199c89f7b7fd4a247b195cea023218
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.1
|
Release files / pyDigitalWaveTools-1.2-py3.10.egg
| Download URL | pyDigitalWaveTools-1.2-py3.10.egg |
|---|---|
| Size | 28.2 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
4462ad692340f7401a3e49bfdbb24c50ea904e114c644ece0eb246ecb4ce95e3
|
|
BLAKE2b-256 checksum How to use checksums |
63af33f02152258a50e2d23c835d006f12a7a2bc5a2a9c84f11dfbd30c299dc0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.1
|
Release files / pyDigitalWaveTools-1.2-py3-none-any.whl
| Download URL | pyDigitalWaveTools-1.2-py3-none-any.whl |
|---|---|
| Size | 13.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a1a093d4101a59c6030b2d9bd7debeb8c55e13bb06992f8f49447147292e5fc5
|
|
BLAKE2b-256 checksum How to use checksums |
881b6e424a6853cd9023bafbc92cc97a6b0cd36ecf4c665843601b3631b7fb5f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.1
|
Security for pyDigitalWaveTools 1.2
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.