-
Updated
Feb 26, 2021 - Jupyter Notebook
pruning
Here are 257 public repositories matching this topic...
-
Updated
Oct 6, 2021 - Python
-
Updated
Oct 31, 2021
-
Updated
Nov 12, 2021 - Python
-
Updated
Nov 12, 2021 - Python
-
Updated
Jul 12, 2019 - Python
-
Updated
Nov 11, 2021 - Python
-
Updated
Sep 19, 2021
-
Updated
Jul 10, 2021 - Jupyter Notebook
-
Updated
Jun 17, 2021 - Python
-
Updated
Nov 1, 2021 - Python
-
Updated
Oct 25, 2021 - Python
-
Updated
Nov 3, 2021 - Python
-
Updated
Nov 12, 2021 - Python
-
Updated
Nov 11, 2021 - Python
-
Updated
Nov 7, 2021 - Go
-
Updated
Oct 2, 2019 - Python
We also need to benchmark the Lottery-tickets Pruning algorithm and the Quantization algorithms. The models used for this would be the student networks discussed in #105 (ResNet18, MobileNet v2, Quantization v2).
Pruning (benchmark upto 40, 50 and 60 % pruned weights)
- Lottery Tickets
Quantization
- Static
- QAT
Benchmarking KD
Update README.rst
-
Updated
Jul 23, 2020 - Python
-
Updated
May 24, 2019
-
Updated
Nov 5, 2021 - Python
-
Updated
Jun 29, 2021
-
Updated
Oct 27, 2019 - Jupyter Notebook
-
Updated
Nov 11, 2021 - Python
-
Updated
May 6, 2021 - Python
-
Updated
Feb 11, 2021 - Python
A good testing regime could include the following:
- Perform an initial backup
- Verify volume
- Perform an incremental backup
- Verify volume
- Prune first backup
- Verify volume
- Diff volume (cross-check with source vol data)
Changing program_name in the code could allow the test data set to be created under a different base folder name without interfering with real-life back
Improve this page
Add a description, image, and links to the pruning topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the pruning topic, visit your repo's landing page and select "manage topics."
If you are interested in working on this issue - please indicate via a comment on this issue. It should be possible for us to pair you up with an existing contributor to help you get started.
From a complexity perspective, this ticket is at an easy level.