Eric Hofesmann

Can you post your code? Training and relevant loss and model files. A github link would work.

I definitely agree that rotated bounding boxes would be valuable to have in FiftyOne. While it shouldn't be too much of a lift to add, it will require updates to...

If you are using the FiftyOne integration with CVAT, then you need to make sure to [load the annotation back into FiftyOne](https://voxel51.com/docs/fiftyone/integrations/cvat.html#loading-annotations) first before exporting them to disk. Also note...

Another look and feel customization that has been requested is to be able to specify the width of bounding box lines. This can be useful depending on the clutter of...

@Yaoxingtian GitHub occasionally has a hard time displaying the notebooks. If that is the issue, then click on the Jupyter Nbviewer shortcut for the examples you are interested in and...

@bsekachev Ah yeah, that is similar! What I'm specifically looking for is not an attribute on an object annotation, but just a video-level attribute directly that is immutable and cannot...

Hey @NicDionne @brimoor Yes! Sorry, I got wrapped up in some things I will give this another pass soon. The ffmpeg build errors are something that we are aware of...

What you're seeing is standard practice throughout the codebase. Whenever a single label field is being loaded through an importer, the default field name is `ground_truth`, which we agree is...

> So at this stage, can you confirm that there could only be 1 subfield for each field ? @ehofesmann Yes, each field can only have one "subfield". Though to...

> This behavior might also be caused by addition of another field `"coco_id"`. I mean it may still assume to load detections only; however, since there are more than one...