-
Notifications
You must be signed in to change notification settings - Fork 416
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
Mono8 support #165
Mono8 support #165
Conversation
Co-Authored-By: Jacob Bandes-Storch <[email protected]>
Co-Authored-By: Jacob Bandes-Storch <[email protected]>
let outIdx = 0; | ||
|
||
for (let i = 0; i < width * height; i++) { | ||
const val = !is_bigendian ? mono16[inIdx] : mono16[inIdx - 1]; |
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.
Did you try ... : mono16[inIdx + 1]
instead? I think inIdx - 1
is wrong because at the beginning, it will be mono16[-1]
.
Co-Authored-By: Jacob Bandes-Storch <[email protected]>
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.
Looks great! I think the next steps will be to make this PR against the internal repo, add some screenshot tests, then once we merge it there it will be included the next time we push out updates to the open source code.
@@ -15,27 +15,27 @@ | |||
"regenerator-runtime": { |
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.
Would be nice to revert these changes since they aren't relevant to the PR.
Merging PR to internal repo, will be out to open source repo in a future push |
Image panel support for mono8, details can be found in this convo: #161 (comment)
source of sample bag: https://www.cse.unr.edu/~kalexis/datasets/thermal-inertial/
Btw encountered some weirdness with /packages/@cruise-automation not being found. Assuming it was an issue with my fork/local npm but flagging just in case