-
Notifications
You must be signed in to change notification settings - Fork 19
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
No able to split the dataset Using HW2GRAPH and getting nx_graphs as empty #21
Comments
Did you figure it out? I have the similar issue. |
yes, you have to make changes in config.py file: https://github.com/AICPS/hw2vec/blob/master/hw2vec/config.py unzip the dataset from assets folder and give the path of toy dataset |
Thanks for your reply. I have figured this problem out and I can run hw2vec now, but when I try to generate a SDF from a RISC-V design that contain multipple .v files. The TopModule file may lose some module, or some module lose some input or output, resulting in a empty of SDF graph. Did your have the same problem?
Best regards
Peng
…________________________________
发件人: Al -Hussain Shaikh ***@***.***>
发送时间: 2024年6月7日 2:11
收件人: AICPS/hw2vec ***@***.***>
抄送: PWang0220 ***@***.***>; Comment ***@***.***>
主题: Re: [AICPS/hw2vec] No able to split the dataset Using HW2GRAPH and getting nx_graphs as empty (Issue #21)
Did you figure it out? I have the similar issue.
yes, you have to make changes in config.py file:
https://github.com/AICPS/hw2vec/blob/master/hw2vec/config.py
unzip the dataset from assets folder and give the path of toy dataset
―
Reply to this email directly, view it on GitHub<#21 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BAC4O4VCVHP5TVRUQ4ZR6UDZGCQ5XAVCNFSM6AAAAABAI6AERSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJTGEZDAOBVGQ>.
You are receiving this because you commented.Message ID: ***@***.***>
|
No, I didn't get that problem. |
If you are getting the problem you can check my repo: https://github.com/alhussain-shaikh/HardwareTrojanDetection- |
The text was updated successfully, but these errors were encountered: