CSAILVision / CSAILVision/LabelMeAnnotationTool

Verification mode

Open
#23 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
JavaScript
Stars
1.5k
Forks
443
PR merge metrics
No merged PRs in 30d

Description

Hi,

We are working on a verification mode for LabelMe - please comment - in particular on the interpretation of the verified-element in the Label XML-format. Is there an XSD available?

---

When dealing with object recognition/classification, a way to fast and easily verify object classifications is often desirable.
A mode (‘v’) will be added to LabelMe in which it is possible to verify whether a given object is correctly classified or not.

![labelmeverificationmode](https://cloud.githubusercontent.com/assets/604815/10335952/415bc6c6-6cf5-11e5-8dd2-fdeaff37c035.png)

When mode=v:
The objects in the annotation will be examined one after the other. The object in question (e.g. a car) will be framed by a polygon on the canvas. Instead of the object list, a verification tool will be presented on the right.
The verification tool will show an image example of what the classified class looks like (e.g. an image of a car) and a description of how the given class should be labelled. It will then be possible to verify, skip or reject the classification by using three buttons - or keyboard shortcuts. Upon each action, the verification tool proceeds to the next object (or image).

A new folder will be added (in addition to Images and Annotations): Classes
The Classes folder will contain example images and corresponding descriptions (HTML-snippets wrapped in XML) - e.g.:
Classes/car.jpg
Classes/car.xml
Classes/bike.jpg
Classes/bike.xml

The verification tool will exploit the existing verified-element in the XML-format, with values:
0 = not-examined
1 = verified
2 = rejected
3 = skipped (examined, but neither verified nor rejected).

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the existing annotation XML handling and the current annotation UI entry points; the issue names no files or tests. Clarify the verified-element semantics and whether an XSD exists, then define the mode=v workflow, Classes/car.* layout, and completion checks before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
computer-vision
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.