You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some questions that have come up, that would be nice to get Sanna's feedback on. Feel free to comment or add to the list (tagging everyone in case you want to comment).
select all rows per page
in the metadata and video tables with checkboxes, is it more practical to select all videos per page?
thickness of ROIs
Do we want the user to be able to define a thickness of the ROI boundary? This thought was brought to you by this SO answer ✨
Right now this parameter is user-editable. To set this value the user sets the buffer_around_ROIs_boundaries parameter in the project config. It is not a mandatory parameter, so if it's not defined then no buffer/thickness is set (we can also set 1e-9 as default if none is set).
Do we want to keep this parameter accessible to the user, or should it be set to a fixed value (e.g. 1e-9) and not editable by the user?
The text was updated successfully, but these errors were encountered:
yes, the input to the shapely.buffer function is a distance that would be in pixels. the meaning would relate to machine precision (see second part of the answer)
As for the buffer, I do like it as-is (ability to change it in the input_config.yaml). With the variability in zoo enclosures, including the width of certain metal bars for some species, it's nice to have this feature flexible.
Some questions that have come up, that would be nice to get Sanna's feedback on. Feel free to comment or add to the list (tagging everyone in case you want to comment).
select all rows per page
in the metadata and video tables with checkboxes, is it more practical to select all videos per page?
thickness of ROIs
Do we want the user to be able to define a thickness of the ROI boundary?
This thought was brought to you by this SO answer ✨
Right now this parameter is user-editable. To set this value the user sets the
buffer_around_ROIs_boundaries
parameter in the project config. It is not a mandatory parameter, so if it's not defined then no buffer/thickness is set (we can also set 1e-9 as default if none is set).Do we want to keep this parameter accessible to the user, or should it be set to a fixed value (e.g. 1e-9) and not editable by the user?
The text was updated successfully, but these errors were encountered: