You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should have an option for detailed NoC reports that give output like all violated latency constraints (or maybe all traffic flow latency
Proposed Behaviour
Add a new --noc_report_detail {summary | failing | all} (at least that's my suggestion!).
Summary prints what we currently do: aggregate statistics. Make sure they are nicely organized and look like a report.
Failing prints traffic flows that fail their latency constraint
All prints the achieved vs. constraint latency for all flows (and maybe more in the future if there are other useful things).
Current Behaviour
We just print summary statistics like aggregate bandwidth and number of flows failing latency.
Possible Solution
Write code to implement the above and add documentation for the command-line option.
I suggest looking at the timing report and trying to format in a similar way.
The text was updated successfully, but these errors were encountered:
We should have an option for detailed NoC reports that give output like all violated latency constraints (or maybe all traffic flow latency
Proposed Behaviour
Add a new --noc_report_detail {summary | failing | all} (at least that's my suggestion!).
Summary prints what we currently do: aggregate statistics. Make sure they are nicely organized and look like a report.
Failing prints traffic flows that fail their latency constraint
All prints the achieved vs. constraint latency for all flows (and maybe more in the future if there are other useful things).
Current Behaviour
We just print summary statistics like aggregate bandwidth and number of flows failing latency.
Possible Solution
Write code to implement the above and add documentation for the command-line option.
I suggest looking at the timing report and trying to format in a similar way.
The text was updated successfully, but these errors were encountered: