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
Is your feature request related to a problem? Please describe.
Hey folks, I have annotation feature usability question. I added auto annotation helper and it kinda broke my workflow. All starts with a 20 images task, each shows ~70 board game cards in a "matrix" arrangement (6 rows, 12 columns).
Before auto annotation my flow would be like this:
I would create the boxes in order (i.e. first row left-to-right, second row left-to-right etc). The N key is super helpful here!
sort the boxes in objects sidebar by id
click on the first one's label text, find needed label by typing a part of it, press Enter, press Tab
...
click on the 70th one's label text...
press F to pay respe to proceed to the next image and repeat
The crucial part is "press Tab". It takes me to the next box's label field, and I know where to look for the next box on the picture because I remember the order in which I drew the boxes. Now with auto annotation my flow is like this:
automatic annotation draws ~70 rectangles over each image in the dataset and labels these with a generic "card"
I manually change the labels from "card" to proper ones
Now, the second step is very painful, because the id's on the boxes are all randomly numbered. I tried to order the labels in my nuclio function before sending them to cvat, but it does not seem to help with ordering of the boxes.
I saw other issues mention that the id's are generated on cvat side because they are used as primary keys in the db. Of course, I still hope that the order of the list can be preserved when cvat adds annotations.
So currently I do this:
right-click a box
left-click the label in the "floating dialog"
type the label, press Enter
repeat
Is there a way to get rid of the mouse action in my case? Thanks in advance!
Describe the solution you'd like
No mouse use at all in the described flow. Alternatively, no mouse clicks, only hovering to "activate" a box.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
I think this issue could be closed as there is a satisfactory alternative flow, and I could have spent a bit more time researching first. It is not perfect though :)
There is an "Attribute annotation" mode that makes me do the following:
(open a job, switch to the mode, it will focus on one of the boxes)
click on the label dropdown to the right, type the one you need, press enter
press Tab twice to go to the next box
I "worked around" the clicking action with Talon Voice, Bitfocus Companion and a Stream Deck Pedal :)
As a minor complaint, there are some hotkeys that will navigate between frames like crazy (not d or f) and I will need to press Undo to return to my frame (but not the box, which I have to find manually, and this sucks). Not sure what these hotkeys are, but they sure are annoying. It all happens when I occasionally fail to click on the dropdown and start typing the label text.
Actions before raising this issue
Is your feature request related to a problem? Please describe.
Hey folks, I have annotation feature usability question. I added auto annotation helper and it kinda broke my workflow. All starts with a 20 images task, each shows ~70 board game cards in a "matrix" arrangement (6 rows, 12 columns).
Before auto annotation my flow would be like this:
to pay respeto proceed to the next image and repeatThe crucial part is "press Tab". It takes me to the next box's label field, and I know where to look for the next box on the picture because I remember the order in which I drew the boxes. Now with auto annotation my flow is like this:
Now, the second step is very painful, because the id's on the boxes are all randomly numbered. I tried to order the labels in my
nuclio
function before sending them tocvat
, but it does not seem to help with ordering of the boxes.I saw other issues mention that the id's are generated on
cvat
side because they are used as primary keys in the db. Of course, I still hope that the order of the list can be preserved whencvat
adds annotations.So currently I do this:
Is there a way to get rid of the mouse action in my case? Thanks in advance!
Describe the solution you'd like
No mouse use at all in the described flow. Alternatively, no mouse clicks, only hovering to "activate" a box.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: