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

Navigation algos should accept non-uint8_t images as inputs #347

Open
alexdewar opened this issue Jun 21, 2022 · 2 comments
Open

Navigation algos should accept non-uint8_t images as inputs #347

alexdewar opened this issue Jun 21, 2022 · 2 comments

Comments

@alexdewar
Copy link
Collaborator

I'm not suggesting that we should use anything other than uint8_t matrices internally, but it would be good if the train/test methods transparently converted other image types rather than throwing an error. I'm currently hitting errors resulting from this in using the Python module and while I could easily do the conversion on the Python side, it would be cleaner (and maybe faster?) to do it on the C++ side.

@alexdewar
Copy link
Collaborator Author

This will also require changes to the Python wrapper code.

@alexdewar
Copy link
Collaborator Author

See: BrainsOnBoard/navbench#22

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

Successfully merging a pull request may close this issue.

1 participant