The ultimate setup harness for OpenClaw. Deploy in minutes. Stay running for months. No CLI required.
Key parameters and specifications
Key parameters and specifications
Parameter
Value
Language
Python
Category
Infrastructure
Subcategory
Model optimization
Stars
1,513
Forks
286
Contributors
4
Created date
2018-10-11
Updated date
2026-10-10
Stars in 1 day
0
Stars in 7 days
1
Rank
10,122
Previous rank
10,135
Rank change
13
7-day stars rank
9,784
Previous 7-day stars rank
9,845
7-day stars rank change
61
Total stars rank
8,040
Previous total stars rank
8,028
Total stars rank change
-12
Country
USA
README summary
Rethinking the Value of Network Pruning This repository contains the code for reproducing the results, and trained ImageNet models, in the following paper: Rethinking the Value of Network Pruning. [[arXiv]]( [[OpenReview]]( Zhuang Liu\*, Mingjie Sun\*, Tinghui Zhou, Gao Huang, Trevor Darrell (\* equal contribution). Also Best Paper Award at NIPS 2018 Workshop on Compact Deep Neural Networks. Several pruning methods' implementations contained in this repo can also be readily used for other research purposes. Paper Summary Fig 1: A typical three
-stage network pruning pipeline. Our paper shows that for **structured** pruning, **training the pruned model from scratch can almost always achieve comparable or higher level of accuracy than the model obtained from the typical "training, pruning and fine-tuning" (Fig. We conclude that for those pruning methods: 1. Training a large, over-parameterized model is often not necessary to obtain an efficient final model. Learned “important” weights of the large model are typically not useful for the small pruned model
. The pruned architecture itself, rather than a set of inherited “important” weights, is more crucial to the efficiency in the final model, which suggests that in some cases pruning can be useful as an architecture search paradigm. Our results suggest the need for more careful baseline evaluations in future research on structured pruning methods. Fig 2: Difference between predefined and automatically discovered target architectures, in channel pruning. The pruning ratio x is user-specified, while a, b, c, d are
determined by the pruning algorithm. Unstructured sparse pruning can also be viewed as automatic. Our finding has different implications for predefined and automatic methods: for a predefined method, it is possible to skip the traditional "training, pruning and fine-tuning" pipeline and directly train the pruned model; for automatic methods, the pruning can be seen as a form of architecture learning. We also compare with the "Lottery Ticket Hypothesis" (Frankle & Carbin 2019), and find that with optimal learning rate, the
"winning ticket" initialization as used in Frankle & Carbin (2019) does not bring improvement over random initialization. For more details please refer to our paper. Implementation We evaluated the following seven pruning methods. Regression based feature reconstruction 4. Unstructured weight-level pruning The first six is structured while the last one is unstructured (or sparse). For CIFAR, our code is based on pytorch-classification and network-slimming. For ImageNet, we use the official Pytorch ImageNet training code. The instructions and models
are in each subfolder. For experiments on The Lottery Ticket Hypothesis, please refer to the folder cifar/lottery-ticket. Contact Feel free to discuss papers/code with us through issues/emails! com Citation If you use our code in your research, please cite:
Frequently asked questions
How many stars and forks are recorded?
Eric-mingjie/rethinking-network-pruning has 1,513 stars and 286 forks.
What is the repository rank?
Eric-mingjie/rethinking-network-pruning is ranked 10,122.
What language and category are recorded?
Eric-mingjie/rethinking-network-pruning has 1,513 stars, uses Python and belongs to Infrastructure.
Which repository is closest in rank?
Eric-mingjie/rethinking-network-pruning is compared with o19s/elasticsearch-learning-to-rank, ranked 10,106 with 1,520 stars.
README
Rethinking the Value of Network Pruning
This repository contains the code for reproducing the results, and trained ImageNet models, in the following paper:
ICLR 2019. Also Best Paper Award at NIPS 2018 Workshop on Compact Deep Neural Networks.
Several pruning methods' implementations contained in this repo can also be readily used for other research purposes.
Paper Summary
Fig 1: A typical three-stage network pruning
pipeline.
Our paper shows that for structured pruning, training the pruned model from scratch can almost always achieve comparable or higher level of accuracy than the model obtained from the typical "training, pruning and fine-tuning" (Fig. 1) procedure. We conclude that for those pruning methods:
Training a large, over-parameterized model is often not necessary to obtain an efficient final model.
Learned “important” weights of the large model are typically not useful for the small pruned model.
The pruned architecture itself, rather than a set of inherited “important” weights, is more crucial to the efficiency in the final model, which suggests that in some cases pruning can be useful as an architecture search paradigm.
Our results suggest the need for more careful baseline evaluations in future research on structured pruning methods.
Fig 2: Difference between predefined and automatically discovered target architectures, in channel pruning. The pruning ratio x is user-specified, while a, b, c, d are determined by the pruning algorithm. Unstructured sparse pruning can also be viewed as automatic. Our finding has different implications for predefined and automatic methods: for a predefined method, it is possible to skip the traditional "training, pruning and fine-tuning" pipeline and directly train the pruned model; for automatic methods, the pruning can be seen as a form of architecture learning.
We also compare with the "Lottery Ticket Hypothesis" (Frankle & Carbin 2019), and find that with optimal learning rate, the "winning ticket" initialization as used in Frankle & Carbin (2019) does not bring improvement over random initialization. For more details please refer to our paper.
If you use our code in your research, please cite:
@inproceedings{liu2018rethinking,
title={Rethinking the Value of Network Pruning},
author={Liu, Zhuang and Sun, Mingjie and Zhou, Tinghui and Huang, Gao and Darrell, Trevor},
booktitle={ICLR},
year={2019}
}