-
Notifications
You must be signed in to change notification settings - Fork 35
Avoiding unnecessary casting #17
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
base: master
Are you sure you want to change the base?
Conversation
Q - value is overwritten |
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.
Have you compared the performance?
Good morning, |
Typo fix just changes cateorical to categorical : ) |
Now it is possible to set render in your config. |
I'm sorry, but I meant about the speed test. I have compared the speed performance of "cast into uint8 -> transfer to GPU -> cast into float32"(master branch) with "cast into float32 -> transfer"(yours), but I also included here. I haven't had time to check the issues so far, but I really appreciate your contribution ;) |
Thank You for Your fast answer. The problem is that with such casting it could ruin floating points for some non-image data. So, maybe it could be better to add a flag, so the user would be able to choose from these two options. |
I have tested the performance, it is the same, results are in issue #22. |
@VCasecnikovs I really appreciate your supports. |
@ku2482, |
No description provided.