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
The logs produced by VPR when building the RRGraph include information on the different types of edge counts. This is a bit verbose, and most users would not need this information:
The number of nodes and edges in the RRGraph itself should remain, since this information is general enough.
Instead of VTR_LOG, they should use VTR_LOGV; however, this may require some work since a "verbosity" variable will need to be passed into this method somehow.
The text was updated successfully, but these errors were encountered:
Hi @AlexandreSinger , I wanted to clarify whether the specific log messages you mentioned are those that detail edge counts for types like SOURCE->OPIN, OPIN->CHANX/CHANY, CHAN->CHAN, and Dedicated clock network edges? Additionally, are these the only logs that should be controlled by verbosity in the alloc_and_load_rr_graph function, or are there others we should consider?
The logs produced by VPR when building the RRGraph include information on the different types of edge counts. This is a bit verbose, and most users would not need this information:

The number of nodes and edges in the RRGraph itself should remain, since this information is general enough.
These log messages are printed here:
vtr-verilog-to-routing/vpr/src/route/rr_graph.cpp
Lines 1975 to 2179 in 21d0150
Instead of VTR_LOG, they should use VTR_LOGV; however, this may require some work since a "verbosity" variable will need to be passed into this method somehow.
The text was updated successfully, but these errors were encountered: