-
Notifications
You must be signed in to change notification settings - Fork 63
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
Allow Shortcutting Min-max Observer #887
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Kyle Sayers <[email protected]>
Signed-off-by: Kyle Sayers <[email protected]>
👋 Hi! Thank you for contributing to llm-compressor. Please add the ready label when the PR is ready for review. |
Signed-off-by: Kyle Sayers <[email protected]>
Signed-off-by: Kyle Sayers <[email protected]>
observer = Observer.load_from_registry( | ||
observer, quantization_args=quantization_args | ||
quantization_args.observer, quantization_args=quantization_args |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should be consistent in how we're fetching the observer - either use the get_observer method or remove it and do it how you're doing it here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Personally in favor of removing the get_observer
now that observer refactor work is done
Purpose
Changes
MovingAverageMinMaxObserver
->MinMaxObserver
since moving average is not required to use itself.averaging_constant == 1.0
Testing
examples/quantization_w4a16/llama3_example.py
to completion