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.

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

Possible better data storage? #16

Open
nmarchuk opened this issue Jul 16, 2021 · 2 comments
Open

Possible better data storage? #16

nmarchuk opened this issue Jul 16, 2021 · 2 comments

Comments

@nmarchuk
Copy link

I was messing around with making the file size of my dataset as small as possible, and realized that signed integers (-128 to 127) are ideal for storing the optical flow data. I don't know exactly how your saving scheme works but in my own testing, an NPY file containing a single channel was around 4 MB and after converting to signed ints it ended up being 500 KB.

Of course this may not be useful to you at all but wanted to share!

@nmarchuk
Copy link
Author

OK I actually may have been mistaken here. Think i had a wrong assumption

@Cartucho
Copy link
Owner

Cartucho commented Aug 2, 2021

That's a great idea! I need to further investigate it.

I am just wondering what would happen if an object moved more that 127 pixels from one frame to the next frame. But I could still use a signed int, just with a max value higher than the resolution of the image to be rendered. Do you agree with this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants