force selected pipeline stages in throughput mode
Validate Operations / validate-operations (push) Has been cancelled
Validate Operations / validate-operations (push) Has been cancelled
increase throughput scheduler budget add experimental throughput auto mode
This commit is contained in:
@@ -112,6 +112,12 @@ The regular validator uses these paths beside each model:
|
||||
| `artifacts/raptor/throughput/pim/` | Pipeline-4 throughput artifacts. |
|
||||
| `artifacts/simulation/{latency,throughput}/` | Functional simulator outputs. |
|
||||
|
||||
`--throughput-pipeline=N` selects an exact throughput depth; `auto` requests
|
||||
automatic depth selection. The default remains 4. Compiler logs report the
|
||||
selected depth when a selection report is available. Small operation graphs can
|
||||
reject exact depth 4. Use `--throughput-pipeline=auto` to test their feasible
|
||||
throughput depth without weakening explicit-depth constraints.
|
||||
|
||||
The [comparison runner](tools/pim/pimcomp/compare/README.md) has separate
|
||||
architecture/pipeline directories and shared `artifacts/common/` references.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user