Skip to content
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

Align instance placement and node attributes #11

Closed
choltz95 opened this issue Jan 20, 2023 · 2 comments
Closed

Align instance placement and node attributes #11

choltz95 opened this issue Jan 20, 2023 · 2 comments

Comments

@choltz95
Copy link

choltz95 commented Jan 20, 2023

Hi! Maybe a dumb question, but the docs mention that there is one-to-one correspondence between the node name from the node attribute array and the keys in the instance placement dictionary.

However, when I check examples, it does not look one to one. For example if I run

nodeattr = np.load('node_attr/RISCY-a-1-c2_node_attr.npy', allow_pickle=True)
instance_placement = np.load('instance_placement/9-RISCY-a-1-c2-u0.7-m2-p1-f0',allow_pickle=True).item()
len(nodeattr[1]), len(instance_placement)

I get (53587, 50052), different sizes and I see that different instance placements for the same design also have different number of standard cell placements. Do you have any guidance for this or an example of the node attribute alignments with instance placement?

@choltz95 choltz95 changed the title Struggling to align instance placement and node attributes Align instance placement and node attributes Jan 20, 2023
@apri0426
Copy link
Contributor

Yeah, the node attribute always has more values than instance placement, because the node attribute array is directly from netlist and the instance placement array is from DEF after placement, which has been processed and reduced by Innovus.
In our own experiment, we take the intersection of two arrays and this part has one-to-one correspondence.

@choltz95
Copy link
Author

That's great- thanks! I am doing the same thing: taking the intersection. I just wanted to verify to make sure it's standard.

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

No branches or pull requests

2 participants