Skip to content

Conversation

@YIYANGCAI
Copy link
Contributor

Signed-off-by: YIYANGCAI [email protected]

Type of Change

Merge two pruning APIs to one.
API changed

Description

will be linked to PR#144

WeiweiZhang1 and others added 17 commits December 5, 2022 13:23
Signed-off-by: Zhang, Weiwei1 <[email protected]>
Signed-off-by: Zhang, Weiwei1 <[email protected]>
Signed-off-by: Zhang, Weiwei1 <[email protected]>
Signed-off-by: Zhang, Weiwei1 <[email protected]>
Signed-off-by: Zhang, Weiwei1 <[email protected]>
Signed-off-by: Zhang, Weiwei1 <[email protected]>
Signed-off-by: Zhang, Weiwei1 <[email protected]>
Signed-off-by: Zhang, Weiwei1 <[email protected]>
Signed-off-by: Zhang, Weiwei1 <[email protected]>
Signed-off-by: wenhuach <dd>
@ftian1
Copy link
Contributor

ftian1 commented Dec 7, 2022

this title is not suitable as a commit message. you don't need mention merge things. you can mentioned new pruning algo or something else

@YIYANGCAI YIYANGCAI changed the title Merged new-developed pruning API to old one. Integrate new-developed pruning API with old one. Dec 7, 2022
end_step=int(total_iterations)) ##iterative
else:
pruner.update_items_for_all_pruners(start_step=total_iterations+1, end_step=total_iterations+1) ## remove the pruner
pruner.update_items_for_all_pruners(start_step=total_iterations + 1,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shall this func get exposed to external user? is it possible to hide this part?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some configs like start_step and end_step are affected by the training hyperparameters, which users should usually tune. This function eases users to change these configs. I suggest keeping it, but of course, removing it does not affect the functionality

YIYANGCAI and others added 3 commits December 7, 2022 17:29
Signed-off-by: YIYANGCAI <[email protected]>
Signed-off-by: Zhang, Weiwei1 <[email protected]>
Signed-off-by: Zhang, Weiwei1 <[email protected]>
Signed-off-by: Zhang, Weiwei1 <[email protected]>
@chensuyue
Copy link
Contributor

Do we need this PR: #144

@ftian1
Copy link
Contributor

ftian1 commented Dec 9, 2022

@wenhuach21 there is conflict to be solved. and I saw the neural_compressor/conf/config.py is modified? this will impact backward compatibility. you should only modify neural_compressor/config.py which is newly introduce for inc 2.0.

@ftian1
Copy link
Contributor

ftian1 commented Dec 9, 2022

as I mentioned before, we have 3 sets of API due to historical reason.

  1. API in top name space of v1.x, which should be totally removed
  2. experimental API, which is yaml based and should keep unchanged for backward compatibility. it used yaml file and neural_compressor/conf/.
  3. API 2.0, which discard yaml. so your changes shouldn't touch neural_compressor/conf/ folder at all. and all examples should be without yaml and is pure python code.

Signed-off-by: Lu, Yintong <[email protected]>
@wenhuach21 wenhuach21 closed this Dec 12, 2022
VincyZhang pushed a commit that referenced this pull request Feb 12, 2023
@chensuyue chensuyue deleted the cyy/pruning-api-merge branch June 15, 2023 05:50
yiliu30 pushed a commit that referenced this pull request Apr 30, 2025
xin3he pushed a commit that referenced this pull request Jul 15, 2025
XuehaoSun pushed a commit that referenced this pull request Jul 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants