cornell-brg/pymtl3-net

Fixed naming convention?

Opened this issue · 0 comments

yo96 commented

We should figure out a way to name all our components and network modules. Sometimes the description is like a prefix (for example, DORYMeshRouteUnitRTL, which is ugly and less readable) and sometimes the description is a suffix (InputUnitCreditRTL).

I think we should use suffix as in this way the components of the same type get sorted together, which is more readable. For example, we should rename DORYMeshRouteUnitRTL to something like MeshRouteUnitYXRTL.