PyEDAA.Reports
Proposal to define an XML-based logging format for outputs from EDA tools and logging libraries.
Install / Use
/learn @edaa-org/PyEDAA.ReportsREADME
Proposal to define an abstract model for outputs from EDA tools and logging libraries.
The main intended use case of pyEDAA.Reports is to import multiple log/report formats (raw logs, CSVs, YAML, JSON, etc.) and provide a unified model that can generate reports using popular formats such as XUnit or Cobertura. Since most vendors, CI services and monitoring tools support XML, the internals of pyEDAA.Reports are to be based on XML transformations.
As an abstract model, the main capability of pyEDAA.Reports is handling messages using an structured format. The readers categorize messages by IDs and append attributes such as the severity, which allow complex filtering and fancy coloring for better human readability.
<p align="center"> <a title="edaa-org.github.io/pyEDAA.Reports" href="https://edaa-org.github.io/pyEDAA.Reports"><img height="275px" src="doc/_static/work-in-progress.png"/></a> </p>Report Kinds
Test Report Summary
- Test Suite
- Test Case
- Test Parameter
Code Coverage Report
- Line Coverage
- Statement Coverage
- Branch Coverage
- Expression Coverage
- State Coverage
- Transition Coverage
Functional Coverage
- Coverage Model
- Dimension
- Bin
- Item
- Range
Synthesis
- Area/resources
- Timing
Implementation
- Area/resources
- Timing
Target input logs/formats
- ActiveHDL
- CoCoTb
- Diamond
- GHDL
- Icarus Verilog
- ISE
- ModelSim/QuestaSim
- nextpnr
- OSVVM
- RivieraPRO
- SymbiYosys
- Synplify
- Quartus
- Verilator
- Verilog-to-Routing
- Vivado
- VUnit
- Xcelium
- Yosys
- ...
References
- olofk/edalize (see
edalize.reporting,edalize.vivado_reporting,edalize.quartus_reporting,edalize.ise_reporting, ...) - librecores/eda-log-parser
- SymbiFlow/fpga-tool-perf
- mattvenn/logLUTs
- tiagolascasas/Vivado-HLS-Report-Parser
- cuelang.org/
Related Skills
node-connect
349.2kDiagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps
claude-opus-4-5-migration
109.5kMigrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5
frontend-design
109.5kCreate distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
model-usage
349.2kUse CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON.
