You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<add_regionx_low="3"y_low="3"x_high="7"y_high="7"subtile="0"> <!-- One specific location is specified -->
26
-
<add_atomname_pattern="n4917">
27
-
<add_atomname_pattern="n6010">
25
+
<add_regionx_low="3"y_low="3"x_high="7"y_high="7"subtile="0"/> <!-- One specific location is specified -->
26
+
<add_atomname_pattern="n4917"/>
27
+
<add_atomname_pattern="n6010"/>
28
28
</partition>
29
29
</partition_list>
30
30
</vpr_constraints>
@@ -41,7 +41,7 @@ VPR has a specific XML format which must be used when creating a placement const
41
41
42
42
The file is passed as an input to VPR when running with placement constraints. When the file is read in, its information is used during the packing and placement stages of VPR. The hierarchy of the file is set up as follows.
43
43
44
-
.. note:: Use the VPR :option:`--read_vpr_constraints` to specify the VPR placement constraints file that is to be loaded.
44
+
.. note:: Use the VPR option :vpr:option:`--read_vpr_constraints` to specify the VPR placement constraints file that is to be loaded.
45
45
46
46
The top level tag is the ``<vpr_constraints>`` tag. This tag contains one ``<partition_list>`` tag. The ``<partition_list>`` tag can be made up of an unbounded number of ``<partition>`` tags. The ``<partition>`` tags contains all of the detailed information of the placement constraints, and is described in detail below.
0 commit comments