vtr-verilog-to-routing icon indicating copy to clipboard operation
vtr-verilog-to-routing copied to clipboard

Published 20 hours ago • verified publisher icon verilog-to-routing

Specify available moves explicitly

Open soheilshahrouz opened this issue 10 months ago • 1 comments

Currently, we pass the number of available moves to the KArmedBanditAgent's constructor to specify which moves are available. This interface assumes that move types have a specific order. This PR changes the interface so that available moves can be specified explicitly.

The main motivation for this PR is to add NoC-specific move types that are disabled for conventional architectures.

Types of changes

  • [ ] Bug fix (change which fixes an issue)
  • [ ] New feature (change which adds functionality)
  • [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • [ ] My change requires a change to the documentation
  • [ ] I have updated the documentation accordingly
  • [ ] I have added tests to cover my changes
  • [x] All new and existing tests passed

soheilshahrouz avatar Apr 20 '24 19:04 soheilshahrouz

@vaughnbetz

I applied your comments. Here is the link to QoR for Titan that shows the new interface for specifying availale move types does not degraged the runtime.

soheilshahrouz avatar May 08 '24 18:05 soheilshahrouz