-
Notifications
You must be signed in to change notification settings - Fork 24
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
Discussion on the role of some classes #4
Comments
Hi, thanks for reaching out. here is an overview and please feel free to ask me any follow-up questions if you want to go into details about any of those: The The network compression itself is split up into multiple parts:
|
Hi, Thanks for the explanation. I was going through the code with the info you provided above and it helped me get a better understanding of how things works. I just need a bit more explanation on how base classes for allocator and pruner work. I have hard time to understand the base logic behind these two classes, just by reading the code. Any help will be appreciated. |
Also another question. I'm interested to play around with the structured sparsification of the model. Does the code remove the sparsed filters from the model? I would like to be able to get real performance boost on the hardware, after performing the sparsification. Thanks, |
This is currently not supported and/or I don't have plans to support it. If you are interested in inference time speed-ups, then I would recommend writing some type of post-processing tool that takes the network graph as input and outputs the slimmed model. Alternatively, you can also hardcode the slimmed version for a particular architecture. If you want to implement something like this, I would be happy to take PRs as well. |
Hi,
I'm trying to understand the structure of the core pruning classes. I wanted to start this thread, and see if you can provide some explanation on the roles of the below classes, and how they generally interact with the main net class:
Any other extra information is also much appreciated.
The text was updated successfully, but these errors were encountered: