vyges-ifp — initialize the floorplan

Physical construction — opt-in, and not part of vyges install loom. These engines build the design database that the sign-off and verification engines read, so they install as their own group:

vyges install physical   # all six
vyges install ifp        # just this one

It is also a standalone vyges-ifp binary on your PATH, which is what the dispatch calls and what a flow author targets directly. Source: vyges-tools/ifp.

vyges-ifp turns an empty design into one with a shape: a die area, a core area inside it, and the rows of standard-cell sites that fill the core. Everything downstream — placement, the power grid, taps — is positioned against those rows, so this is the first thing that runs and the thing every later stage assumes.

Run it

vyges ifp run design.odb --die-area '0 0 200 200' --core-area '10 10 190 190' --site unithd

Rows tile the core at the site’s height. --additional-sites tiles hybrid rows for libraries with more than one row height; --row-parity trims the row count to an odd or even total; --flip-sites shifts the orientation phase for named sites.

Where it sits

Empty database in, floorplanned database out. It is the entry point of the construction group: no other engine here has anything to place against until the rows exist.

Known bounds

• Hybrid row patterns are tiled uniformly rather than from a row pattern. Row counts agree on the cases measured, but the construction differs — do not rely on it for hybrid libraries.
• UPF power domains are not inserted. The floorplan geometry matches; the instance census that follows from domain insertion does not.
• The -utilization form (derive the die from a target utilization) is not implemented; give the areas explicitly.

See the full CLI reference (generated from --help and --describe).