Skip to content

Slightly clarified description of --place_delay_model simple in the docs #2738

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 21, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/src/vpr/command_line_usage.rst
Original file line number Diff line number Diff line change
Expand Up @@ -983,7 +983,7 @@ The following options are only valid when the placement engine is in timing-driv

Controls how the timing-driven placer estimates delays.

* ``simple`` The placement delay estimator is built from the router lookahead. This is more CPU-efficient and still as accurate as the ``delta` model.
* ``simple`` The placement delay estimator is built from the router lookahead. This takes less CPU time to build and it and still as accurate as the ``delta` model.
* ``delta`` The router is used to profile delay from various locations in the grid for various differences in position.
* ``delta_override`` Like ``delta`` but also includes special overrides to ensure effects of direct connects between blocks are accounted for.
This is potentially more accurate but is more complex and depending on the architecture (e.g. number of direct connects) may increase place run-time.
Expand Down