Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add FP16 support to ptq_evaluate.py and update README argument list #1174
Add FP16 support to ptq_evaluate.py and update README argument list #1174
Changes from 1 commit
26412f8
ebe901b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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
half
andfloat16
are equivalent, and for consistency reasons I think I preferfloat16
.If I am missing something, let me know please.
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.
Yes, they are functionally equivalent. My initial thought was that using half could help prevent typos, as the only difference is the letter b.
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.
Now, I am trying to save custom-bit-width models, for example
FP16
withmantissa 9 bits
,exponent 6 bits
etc, but seems like not possible given the available PyTorchdtypes
.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.
Unfortunately I'm not sure I can fully help with the second issue, since we mostly focus on minifloat quantization with 8 bits of fewer.
In the meantime, would you mind changing
half
tofloat16
? I understand the potential for typos but I still prefer trying to be consistent across the codebase, and we never (or rarely) use half instead of float16.Thanks!
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 can simulate for now, so I have a working workaround which is something. I have done all the requested changes as requested. Many thanks again.