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

[Enhancement] Allowing possibility to convert raw image to uint16 #762

Open
jacopoabramo opened this issue Apr 19, 2024 · 0 comments
Open

Comments

@jacopoabramo
Copy link

jacopoabramo commented Apr 19, 2024

I'm currently using trackpy with floating point images that are normalized in post-processing between [0, 1]. I did not at this time make a proper benchmark but I'm afraid that the conversion from floating point to uint8 may impact the localization accuracy. I was thinking that it would be nice to add an optional parameter in the trackpy.locate function to set the data type of the converted image to be able to accomodate either uint8 or uint16. I can make the PR myself, I don't think it would be a big change, but I wanted to make sure to first get an opinion if this makes sense and - if it does - which APIs would be affected by this change so to accomodate them all.

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

1 participant