-
|
I'm working with videos, and the indexing and match finding parts are reasonably well documented, but then the GUI opens and there's no documentation I can find other than pointing out where I can change keyboard shortcuts. While I found the context menu, and that has helped me explore a bit, I don't know how to make good use of the GUI. There are some things that are not defined as far as I can tell, so I don't actually know what they do. Some of the things that stand out most as mysteries are in the tagging section. What is "good" and "bad" match tagging, and what is negative match tagging? I've tried experimenting with them, but I can't see anything happening, other than moving to the next match set. What am I tagging -- the match set, or a particular video? And what can I do after they're tagged in these ways? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Yes, there is no documentation yet for the GUi part. I guess things have stabilized enough to write some documentation on it. Perhaps you would like to contribute?
All available actions are in the context menu.
This is mostly useless. It creates a csv file for testing cbird; e.g. you can go through a bunch of results and mark each one as good or bad and it saves that to a csv file. Later that file can be used to test cbird or for whatever external program.
This is for marking false matches so they don't keep showing. You use this in conjunction with For commands that use pairs of items (like negative tagging, template match, compare videos etc), the selected item and first item makeup the pair. The first image is (by default) the needle of the search query, though this can change by rotating the view or deleting files. |
Beta Was this translation helpful? Give feedback.
Yes, there is no documentation yet for the GUi part. I guess things have stabilized enough to write some documentation on it. Perhaps you would like to contribute?
All available actions are in the context menu.
This is mostly useless. It creates a csv file for testing cbird; e.g. you can go through a bunch of results and mark each one as good or bad and it saves that to a csv file. Later that file can be used to test cbird or for whatever external program.
This is for marking false matches so they don't keep showing. You use this in conjunction …