search

Shared-Reality-Lab / IMAGE-HAPI

This repository contains both the java and JS/TS versions of the HAPI (Haply's API)
0 stars 0 forks source link

Speed up Haply when tracing a segment #27

Closed Cybernide closed 2 years ago

Cybernide commented 2 years ago

These suggestions were with the consultation of @rayanisran

Tried out semantic segmentation on the Haply demo: tracing takes waaaay too long. Suggest speeding up the tracing.

Can we also reduce the number of points visited? Users probably won't be able to feel all that detail anyways, and personally, I think that knowing every single small flick of the segment is less important than having a crude gestalt of all the segments and knowing their positions relative to the rest of the image.

jeffbl commented 2 years ago

Agree faster would be better, but please make sure to emphasize stability even at expense of speed. I think it is easier to tell people "we're working on speeding it up" than "it doesn't work very well overall, but we're working on that".

rayanisran commented 2 years ago

I set the tracing "speed" (i.e., the time taken to move from one point to the next in the contour) to 6 ms (was previously 15 ms). Seems to still maintain stability, but the speed can still be adjusted. Perhaps we can make this a setting in the options eventually as end users will likely have their own preference.

Reducing the number of points is something that can either be done on the preprocessor or handler side. Probably the latter if you mean just having slightly fewer equally spaced points. But as stated during the informal demo last week, a smoothening filter might help to provide a better interpretation of the general shape of the segment.

rayanisran commented 2 years ago

BTW, and I know you mentioned this @Cybernide: this should be on the browser repo. ;)