Background
After running the calculate_iaa function, the resulting IAA values appear as fields in the sidebar UI (example shown in the screenshot).
Problem
- Current behavior: Each IoU value (e.g.,
0.5, 0.55, ..., 0.95) results in a separate field (e.g., bbox_iaa_iou_0,5, bbox_iaa_iou_0,55, etc.).
- This approach can pollute the UI when users calculate multiple IAA values, cluttering the sidebar.
- Alternative: Storing these values in a dictionary would be cleaner, but it would limit users' ability to easily filter the values using the UI sliders.
Open Questions
- Should we prioritize UI clarity (e.g., using a dictionary) or filtering functionality (separate fields for each IoU value)?
- Is there a way to implement a hybrid solution where:
- Values are stored in a dictionary for clarity,
- But still exposed in the UI for filtering?
Screenshot
Background
After running the
calculate_iaafunction, the resulting IAA values appear as fields in the sidebar UI (example shown in the screenshot).Problem
0.5,0.55, ...,0.95) results in a separate field (e.g.,bbox_iaa_iou_0,5,bbox_iaa_iou_0,55, etc.).Open Questions
Screenshot
