Reconvergence handling improves metric quality in circuits with fanout branches that rejoin.
Algorithm selection
| Algorithm | Complexity | Use when |
|---|---|---|
basic |
O(n^2) |
quick checks and small circuits |
simple |
O(n^2 log n) |
default production choice |
advanced |
O(n^3) |
deep debug on complex pipelines |
CLI usage
Genus mode examples:
python3 opentest --genus cop -i designs/s27.v -r -a simple -j
python3 opentest --genus scoap -i designs/s27.v -r -a simple
Yosys mode example:
python3 opentest --yosys analyze_and_add_tp -i <design.json> --scoap -t 50 -m 10 -v
Practical recommendations
- Start with
simplefor normal runs. - Use
advancedonly when metric behavior looks suspicious around heavy fanout. - Keep verbose mode enabled while tuning thresholds and test-point count.
Parallel execution
Large circuits can automatically use parallel processing in analysis paths. Keep reconvergence enabled so observability adjustments remain correlation-aware.
Output usage
- feed reconvergence-aware COP/SCOAP results into TPI selection
- compare outputs between algorithms only when behavior needs investigation
- keep algorithm choice consistent inside a single benchmark campaign