Skip to content

Conversation

@eszpotanski
Copy link
Contributor

This PR adds new variables for max number of repairs per iteration in rsz::repairSetup, introduced in The-OpenROAD-Project/OpenROAD#6244. It also sets the best found values for a few designs.

It adds:

  • FP_REPAIR_TIMING_MAX_PASSES_PER_ITER - max number of repairs per iteration during floorplan,
  • CTS_REPAIR_TIMING_MAX_PASSES_PER_ITER - max number of repairs per iteration during CTS,
  • GRT_REPAIR_TIMING_MAX_PASSES_PER_ITER - max number of repairs per iteration during GRT.

@eszpotanski eszpotanski force-pushed the eszpot/max-passes-per-iter-params branch from ac28d08 to 286e8c2 Compare November 26, 2024 10:23
@eszpotanski eszpotanski marked this pull request as draft November 26, 2024 10:46
}

repair_timing_helper
repair_timing_helper "cts"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove quotes, not needed in .tcl

- place
FP_REPAIR_TIMING_MAX_PASSES_PER_ITER:
description: >
Maximum number of repairs per iteration during repair_timing, called from floorplan.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

more magic values? Every option makes a feature twice as hard to use.

Maximum number of repairs per iteration during repair_timing, called from CTS.
default: 20
stages:
- cts
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A proliferation of the same variable for the same operation. This multiplies the number of variables... Not ideal...

Copy link
Collaborator

@oharboe oharboe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

each magic variable makes the feature twice as hard to use...

Can we make some better automatic policy here?

@eszpotanski eszpotanski force-pushed the eszpot/max-passes-per-iter-params branch from 286e8c2 to 63a054f Compare November 28, 2024 16:49
@eszpotanski eszpotanski force-pushed the eszpot/max-passes-per-iter-params branch from 63a054f to ca642ca Compare January 2, 2025 14:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants