2015-03-06 01:58:10 -06:00
|
|
|
#FIG 3.2 Produced by xfig version 3.2.5c
|
Make the Python interface closely mirroring the C++ one.
* Change: In Isobar, the Python interface was not exactly mirroring the
C++ one, now it is the case. The Python code should look likes almost
exactly like the C++ one, the only differences remaining being due
to the languages respective syntaxes. Note that in the case of
constructor functions, it leads to a slightly longer notation in
Python that it could have been (mimic the ".create()" static
member). Main modifications:
1. Mirror the static constructor syntax with create():
Cell( ... ) ==> Cell.create( ... )
2. Correct hierarchy for constants in Instance, Net, Pin
& Transformation. For example:
Hurricane.PlacementStatusFIXED
==> Hurricane.Instance.PlacementStatus.FIXED
Hurricane.OrientationID
==> Hurricane.Transformation.Orientation.ID
Hurricane.TypeLOGICAL ==> Hurricane.Net.Type.LOGICAL
Hurricane.DirectionIN ==> Hurricane.Net.Direction.IN
* Change: In CRL Core, correction to match the improved Python API
in the configutation helpers.
* Change: In Cumulus, correction to match the improved Python API.
* Change: In Stratus, correction to match the improved Python API.
* Change: In Documenation, update for the new Python interface
(both user's guide & examples).
* Note: We must port those changes into Chams for it to continue
to run.
* Change: In Documenation, update the Python script support part.
2014-06-28 10:37:59 -05:00
|
|
|
Landscape
|
|
|
|
Center
|
|
|
|
Inches
|
|
|
|
Letter
|
Add NetRoutingState (Property) on Nets to tell Kite what to do.
* New: In Katabatic, add the ability to decorate some (i.e. few) nets
with a state that indicate to Katabatic & Kite what to do with it.
The possible states are:
1. Fixed : all the wire are in fixed positions. The router cannot
move them and account them as obstacles.
2. ManualGlobalRoute : a user-defined topology is supplied. The
wires still have to be detailed route in "Detailed Pre-Route"
but will be skipped for the global routing and fixed for the
general Detailed route.
3. AutomaticGlobalRoute : ordinary nets, to be global routed then
detail routed.
4. Excluded : do not try to global or detail route thoses nets.
5. MixedPreRoute : mask combining Fixed and ManualGlobalRoute.
Not all nets have this property, only those that needs a special
processing.
To ease the access to the state, it is nested inside a
PrivateProperty in the net (NetRoutingProperty), with an extension
access class (NetRoutingExtension).
* New: In Kite, take account of NetRoutingState. Pointers to the
net's states are strored inside an internal map for faster access.
The property is *not* deleted when Kite is destroyed. The property
will remains until the Net itself is destroyed.
As a consequence, the lists that where passed to high level
function are removed as the information can now be accessed directly
through the net NetRoutingProperty.
* New: In Unicorn, in CgtMain, comply with the update interface.
* New: In documentation, update the User's Guide to explain the Pre-routed
step of Kite.
2014-07-02 07:36:58 -05:00
|
|
|
70.00
|
Make the Python interface closely mirroring the C++ one.
* Change: In Isobar, the Python interface was not exactly mirroring the
C++ one, now it is the case. The Python code should look likes almost
exactly like the C++ one, the only differences remaining being due
to the languages respective syntaxes. Note that in the case of
constructor functions, it leads to a slightly longer notation in
Python that it could have been (mimic the ".create()" static
member). Main modifications:
1. Mirror the static constructor syntax with create():
Cell( ... ) ==> Cell.create( ... )
2. Correct hierarchy for constants in Instance, Net, Pin
& Transformation. For example:
Hurricane.PlacementStatusFIXED
==> Hurricane.Instance.PlacementStatus.FIXED
Hurricane.OrientationID
==> Hurricane.Transformation.Orientation.ID
Hurricane.TypeLOGICAL ==> Hurricane.Net.Type.LOGICAL
Hurricane.DirectionIN ==> Hurricane.Net.Direction.IN
* Change: In CRL Core, correction to match the improved Python API
in the configutation helpers.
* Change: In Cumulus, correction to match the improved Python API.
* Change: In Stratus, correction to match the improved Python API.
* Change: In Documenation, update for the new Python interface
(both user's guide & examples).
* Note: We must port those changes into Chams for it to continue
to run.
* Change: In Documenation, update the Python script support part.
2014-06-28 10:37:59 -05:00
|
|
|
Single
|
|
|
|
-2
|
|
|
|
1200 2
|
Add NetRoutingState (Property) on Nets to tell Kite what to do.
* New: In Katabatic, add the ability to decorate some (i.e. few) nets
with a state that indicate to Katabatic & Kite what to do with it.
The possible states are:
1. Fixed : all the wire are in fixed positions. The router cannot
move them and account them as obstacles.
2. ManualGlobalRoute : a user-defined topology is supplied. The
wires still have to be detailed route in "Detailed Pre-Route"
but will be skipped for the global routing and fixed for the
general Detailed route.
3. AutomaticGlobalRoute : ordinary nets, to be global routed then
detail routed.
4. Excluded : do not try to global or detail route thoses nets.
5. MixedPreRoute : mask combining Fixed and ManualGlobalRoute.
Not all nets have this property, only those that needs a special
processing.
To ease the access to the state, it is nested inside a
PrivateProperty in the net (NetRoutingProperty), with an extension
access class (NetRoutingExtension).
* New: In Kite, take account of NetRoutingState. Pointers to the
net's states are strored inside an internal map for faster access.
The property is *not* deleted when Kite is destroyed. The property
will remains until the Net itself is destroyed.
As a consequence, the lists that where passed to high level
function are removed as the information can now be accessed directly
through the net NetRoutingProperty.
* New: In Unicorn, in CgtMain, comply with the update interface.
* New: In documentation, update the User's Guide to explain the Pre-routed
step of Kite.
2014-07-02 07:36:58 -05:00
|
|
|
2 2 0 4 8 8 60 -1 41 0.000 0 0 -1 0 0 5
|
Make the Python interface closely mirroring the C++ one.
* Change: In Isobar, the Python interface was not exactly mirroring the
C++ one, now it is the case. The Python code should look likes almost
exactly like the C++ one, the only differences remaining being due
to the languages respective syntaxes. Note that in the case of
constructor functions, it leads to a slightly longer notation in
Python that it could have been (mimic the ".create()" static
member). Main modifications:
1. Mirror the static constructor syntax with create():
Cell( ... ) ==> Cell.create( ... )
2. Correct hierarchy for constants in Instance, Net, Pin
& Transformation. For example:
Hurricane.PlacementStatusFIXED
==> Hurricane.Instance.PlacementStatus.FIXED
Hurricane.OrientationID
==> Hurricane.Transformation.Orientation.ID
Hurricane.TypeLOGICAL ==> Hurricane.Net.Type.LOGICAL
Hurricane.DirectionIN ==> Hurricane.Net.Direction.IN
* Change: In CRL Core, correction to match the improved Python API
in the configutation helpers.
* Change: In Cumulus, correction to match the improved Python API.
* Change: In Stratus, correction to match the improved Python API.
* Change: In Documenation, update for the new Python interface
(both user's guide & examples).
* Note: We must port those changes into Chams for it to continue
to run.
* Change: In Documenation, update the Python script support part.
2014-06-28 10:37:59 -05:00
|
|
|
9000 6000 10800 6000 10800 6900 9000 6900 9000 6000
|
Add NetRoutingState (Property) on Nets to tell Kite what to do.
* New: In Katabatic, add the ability to decorate some (i.e. few) nets
with a state that indicate to Katabatic & Kite what to do with it.
The possible states are:
1. Fixed : all the wire are in fixed positions. The router cannot
move them and account them as obstacles.
2. ManualGlobalRoute : a user-defined topology is supplied. The
wires still have to be detailed route in "Detailed Pre-Route"
but will be skipped for the global routing and fixed for the
general Detailed route.
3. AutomaticGlobalRoute : ordinary nets, to be global routed then
detail routed.
4. Excluded : do not try to global or detail route thoses nets.
5. MixedPreRoute : mask combining Fixed and ManualGlobalRoute.
Not all nets have this property, only those that needs a special
processing.
To ease the access to the state, it is nested inside a
PrivateProperty in the net (NetRoutingProperty), with an extension
access class (NetRoutingExtension).
* New: In Kite, take account of NetRoutingState. Pointers to the
net's states are strored inside an internal map for faster access.
The property is *not* deleted when Kite is destroyed. The property
will remains until the Net itself is destroyed.
As a consequence, the lists that where passed to high level
function are removed as the information can now be accessed directly
through the net NetRoutingProperty.
* New: In Unicorn, in CgtMain, comply with the update interface.
* New: In documentation, update the User's Guide to explain the Pre-routed
step of Kite.
2014-07-02 07:36:58 -05:00
|
|
|
2 2 0 4 8 7 60 -1 20 0.000 0 0 -1 0 0 5
|
Make the Python interface closely mirroring the C++ one.
* Change: In Isobar, the Python interface was not exactly mirroring the
C++ one, now it is the case. The Python code should look likes almost
exactly like the C++ one, the only differences remaining being due
to the languages respective syntaxes. Note that in the case of
constructor functions, it leads to a slightly longer notation in
Python that it could have been (mimic the ".create()" static
member). Main modifications:
1. Mirror the static constructor syntax with create():
Cell( ... ) ==> Cell.create( ... )
2. Correct hierarchy for constants in Instance, Net, Pin
& Transformation. For example:
Hurricane.PlacementStatusFIXED
==> Hurricane.Instance.PlacementStatus.FIXED
Hurricane.OrientationID
==> Hurricane.Transformation.Orientation.ID
Hurricane.TypeLOGICAL ==> Hurricane.Net.Type.LOGICAL
Hurricane.DirectionIN ==> Hurricane.Net.Direction.IN
* Change: In CRL Core, correction to match the improved Python API
in the configutation helpers.
* Change: In Cumulus, correction to match the improved Python API.
* Change: In Stratus, correction to match the improved Python API.
* Change: In Documenation, update for the new Python interface
(both user's guide & examples).
* Note: We must port those changes into Chams for it to continue
to run.
* Change: In Documenation, update the Python script support part.
2014-06-28 10:37:59 -05:00
|
|
|
4200 6000 9000 6000 9000 6900 4200 6900 4200 6000
|
|
|
|
2 1 0 2 21 7 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
4500 4200 4500 -300
|
|
|
|
2 1 0 2 21 7 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
5100 600 5100 -300
|
|
|
|
2 1 0 2 8 7 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
5400 6000 5400 5100
|
|
|
|
2 1 0 2 8 7 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
5550 6000 5550 3300
|
|
|
|
2 1 0 2 0 7 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
4800 7800 4800 5100
|
|
|
|
2 1 0 2 0 7 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
4650 7800 4650 6900
|
|
|
|
2 1 0 2 18 5 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
10800 8250 11700 8250
|
|
|
|
2 1 0 2 18 5 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
10800 6450 11700 6450
|
|
|
|
2 1 0 2 18 5 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
7800 4650 11700 4650
|
|
|
|
2 1 0 2 18 5 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
8400 2850 11700 2850
|
|
|
|
2 1 0 2 18 5 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
8400 1050 11700 1050
|
|
|
|
2 1 0 2 18 5 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
10800 -750 11700 -750
|
|
|
|
2 1 0 2 18 5 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
12600 5700 13800 5700
|
|
|
|
2 1 0 2 18 5 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
12600 2700 13200 2700
|
|
|
|
2 1 0 2 18 5 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
13500 1800 13500 600
|
|
|
|
2 1 0 2 18 5 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
14100 4800 14100 600
|
Add NetRoutingState (Property) on Nets to tell Kite what to do.
* New: In Katabatic, add the ability to decorate some (i.e. few) nets
with a state that indicate to Katabatic & Kite what to do with it.
The possible states are:
1. Fixed : all the wire are in fixed positions. The router cannot
move them and account them as obstacles.
2. ManualGlobalRoute : a user-defined topology is supplied. The
wires still have to be detailed route in "Detailed Pre-Route"
but will be skipped for the global routing and fixed for the
general Detailed route.
3. AutomaticGlobalRoute : ordinary nets, to be global routed then
detail routed.
4. Excluded : do not try to global or detail route thoses nets.
5. MixedPreRoute : mask combining Fixed and ManualGlobalRoute.
Not all nets have this property, only those that needs a special
processing.
To ease the access to the state, it is nested inside a
PrivateProperty in the net (NetRoutingProperty), with an extension
access class (NetRoutingExtension).
* New: In Kite, take account of NetRoutingState. Pointers to the
net's states are strored inside an internal map for faster access.
The property is *not* deleted when Kite is destroyed. The property
will remains until the Net itself is destroyed.
As a consequence, the lists that where passed to high level
function are removed as the information can now be accessed directly
through the net NetRoutingProperty.
* New: In Unicorn, in CgtMain, comply with the update interface.
* New: In documentation, update the User's Guide to explain the Pre-routed
step of Kite.
2014-07-02 07:36:58 -05:00
|
|
|
2 2 0 4 21 21 60 -1 41 0.000 0 0 -1 0 0 5
|
|
|
|
9000 -1200 10800 -1200 10800 -300 9000 -300 9000 -1200
|
|
|
|
2 2 0 4 21 7 60 -1 20 0.000 0 0 -1 0 0 5
|
|
|
|
4200 -1200 9000 -1200 9000 -300 4200 -300 4200 -1200
|
|
|
|
2 2 0 4 21 7 60 -1 20 0.000 0 0 -1 0 0 5
|
|
|
|
4800 600 6600 600 6600 1500 4800 1500 4800 600
|
|
|
|
2 2 0 4 21 21 60 -1 41 0.000 0 0 -1 0 0 5
|
|
|
|
6600 600 8400 600 8400 1500 6600 1500 6600 600
|
|
|
|
2 2 0 4 21 7 60 -1 20 0.000 0 0 -1 0 0 5
|
|
|
|
4800 2400 6600 2400 6600 3300 4800 3300 4800 2400
|
|
|
|
2 2 0 4 21 21 60 -1 41 0.000 0 0 -1 0 0 5
|
|
|
|
6600 2400 8400 2400 8400 3300 6600 3300 6600 2400
|
|
|
|
2 2 0 4 21 7 60 -1 20 0.000 0 0 -1 0 0 5
|
|
|
|
4200 4200 6000 4200 6000 5100 4200 5100 4200 4200
|
|
|
|
2 2 0 4 21 21 60 -1 41 0.000 0 0 -1 0 0 5
|
|
|
|
6000 4200 7800 4200 7800 5100 6000 5100 6000 4200
|
|
|
|
2 2 0 4 0 7 60 -1 20 0.000 0 0 -1 0 0 5
|
|
|
|
4200 7800 9000 7800 9000 8700 4200 8700 4200 7800
|
|
|
|
2 2 0 4 0 7 60 -1 0 0.000 0 0 -1 0 0 5
|
|
|
|
9000 7800 10800 7800 10800 8700 9000 8700 9000 7800
|
|
|
|
2 2 0 4 18 18 60 -1 20 0.000 0 0 -1 0 0 5
|
|
|
|
11700 -1200 12600 -1200 12600 8700 11700 8700 11700 -1200
|
|
|
|
2 2 0 4 18 18 70 -1 30 0.000 0 0 -1 0 0 5
|
|
|
|
13800 4800 14400 4800 14400 6600 13800 6600 13800 4800
|
|
|
|
2 1 0 2 8 7 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
5850 6000 5850 -300
|
|
|
|
2 2 0 4 18 18 70 -1 30 0.000 0 0 -1 0 0 5
|
|
|
|
13200 1800 13800 1800 13800 3600 13200 3600 13200 1800
|
|
|
|
2 1 0 2 8 7 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
5700 6000 5700 1500
|
|
|
|
2 1 0 2 0 7 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
4950 7800 4950 3300
|
|
|
|
2 2 0 4 18 18 70 -1 30 0.000 0 0 -1 0 0 5
|
|
|
|
12600 -1200 14400 -1200 14400 600 12600 600 12600 -1200
|
2015-03-06 01:58:10 -06:00
|
|
|
2 1 0 2 0 7 70 -1 -1 0.000 0 0 -1 1 0 2
|
|
|
|
1 1 2.00 120.00 240.00
|
|
|
|
5100 7800 5100 1500
|
Add NetRoutingState (Property) on Nets to tell Kite what to do.
* New: In Katabatic, add the ability to decorate some (i.e. few) nets
with a state that indicate to Katabatic & Kite what to do with it.
The possible states are:
1. Fixed : all the wire are in fixed positions. The router cannot
move them and account them as obstacles.
2. ManualGlobalRoute : a user-defined topology is supplied. The
wires still have to be detailed route in "Detailed Pre-Route"
but will be skipped for the global routing and fixed for the
general Detailed route.
3. AutomaticGlobalRoute : ordinary nets, to be global routed then
detail routed.
4. Excluded : do not try to global or detail route thoses nets.
5. MixedPreRoute : mask combining Fixed and ManualGlobalRoute.
Not all nets have this property, only those that needs a special
processing.
To ease the access to the state, it is nested inside a
PrivateProperty in the net (NetRoutingProperty), with an extension
access class (NetRoutingExtension).
* New: In Kite, take account of NetRoutingState. Pointers to the
net's states are strored inside an internal map for faster access.
The property is *not* deleted when Kite is destroyed. The property
will remains until the Net itself is destroyed.
As a consequence, the lists that where passed to high level
function are removed as the information can now be accessed directly
through the net NetRoutingProperty.
* New: In Unicorn, in CgtMain, comply with the update interface.
* New: In documentation, update the User's Guide to explain the Pre-routed
step of Kite.
2014-07-02 07:36:58 -05:00
|
|
|
4 1 8 50 -1 18 24 0.0000 4 300 1920 6600 6600 CRL Core\001
|
|
|
|
4 1 7 50 -1 18 18 0.0000 4 285 990 9975 6600 PyCRL\001
|
|
|
|
4 1 7 50 -1 18 32 1.5708 4 480 810 13650 -300 cgt\001
|
|
|
|
4 1 7 50 -1 18 18 0.0000 4 285 1500 9900 -600 PyUnicorn\001
|
|
|
|
4 1 21 50 -1 18 24 0.0000 4 300 1575 6600 -600 Unicorn\001
|
|
|
|
4 1 21 50 -1 18 24 0.0000 4 300 780 5700 1200 Kite\001
|
|
|
|
4 1 7 50 -1 18 18 0.0000 4 285 945 7500 1200 PyKite\001
|
|
|
|
4 1 21 50 -1 18 24 0.0000 4 300 900 5700 3000 Knik\001
|
|
|
|
4 1 7 50 -1 18 18 0.0000 4 285 1020 7500 3000 PyKnik\001
|
2015-03-06 01:58:10 -06:00
|
|
|
4 1 7 50 -1 18 18 0.0000 4 285 1425 6900 4800 PyEtesian\001
|
|
|
|
4 1 21 50 -1 18 24 0.0000 4 300 1455 5100 4800 Etesian\001
|
Add NetRoutingState (Property) on Nets to tell Kite what to do.
* New: In Katabatic, add the ability to decorate some (i.e. few) nets
with a state that indicate to Katabatic & Kite what to do with it.
The possible states are:
1. Fixed : all the wire are in fixed positions. The router cannot
move them and account them as obstacles.
2. ManualGlobalRoute : a user-defined topology is supplied. The
wires still have to be detailed route in "Detailed Pre-Route"
but will be skipped for the global routing and fixed for the
general Detailed route.
3. AutomaticGlobalRoute : ordinary nets, to be global routed then
detail routed.
4. Excluded : do not try to global or detail route thoses nets.
5. MixedPreRoute : mask combining Fixed and ManualGlobalRoute.
Not all nets have this property, only those that needs a special
processing.
To ease the access to the state, it is nested inside a
PrivateProperty in the net (NetRoutingProperty), with an extension
access class (NetRoutingExtension).
* New: In Kite, take account of NetRoutingState. Pointers to the
net's states are strored inside an internal map for faster access.
The property is *not* deleted when Kite is destroyed. The property
will remains until the Net itself is destroyed.
As a consequence, the lists that where passed to high level
function are removed as the information can now be accessed directly
through the net NetRoutingProperty.
* New: In Unicorn, in CgtMain, comply with the update interface.
* New: In documentation, update the User's Guide to explain the Pre-routed
step of Kite.
2014-07-02 07:36:58 -05:00
|
|
|
4 1 7 50 -1 18 32 1.5708 4 510 1830 12375 3600 Python\001
|
|
|
|
4 1 7 50 -1 18 24 1.5708 4 300 1410 13650 2700 Stratus\001
|
|
|
|
4 1 7 50 -1 18 24 1.5708 4 390 1275 14250 5700 Plugin\001
|
|
|
|
4 1 0 50 -1 18 24 0.0000 4 300 1935 6600 8400 Hurricane\001
|
|
|
|
4 1 7 50 -1 18 18 0.0000 4 225 900 9900 8400 Isobar\001
|