Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Why use the 8-bit floating numbers to compute the original cost? #16

Open
shiyuetianqiang opened this issue Oct 29, 2020 · 1 comment
Open

Why use the 8-bit floating numbers to compute the original cost? #16

shiyuetianqiang opened this issue Oct 29, 2020 · 1 comment

Comments

@shiyuetianqiang
Copy link

Hi,
The work is amazing.
When I looked through the code, I foud that you employed the 8-bit floating numbers to compute the original cost and store
it as a lookup table. I wondered why not use the 32-bit floating(not use the flag "--half" in the pretraining process) or use the 16-bit floating (use the flag "--half" in the pretraining process)? Could you please clarify that?
Thanks a lot!
@shiyuetianqiang
Copy link
Author

Sorry, I got it.
It seems that you employed the 8-bit as the baseline

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@shiyuetianqiang