NaturalIntelligence / NaturalIntelligence/imglab

Clickable labels instead of typing; others

Open
#158 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
1k
Forks
613
PR merge metrics
No merged PRs in 30d

Description

I've been playing around with this code (and trying to learn riot js).

Much of the UI mechanics of the program is exactly what I want.

But there are a number of issues that I would like have addressed before it can be used for my company's purposes.

I do recognize this is volunteer effort. I think I can get my boss to help fund this project to get what we want in this program, which is to make it more industrial strength. That is, a high volume (1000's) of labeling and review/fixing that needs to be done.

  1. display a choice of labels or feature point names from a predetermined set for the current selected bounding box OR selected feature point. Currently, the list of bounding boxes or feature points is shown AND you have to type the label or feature point name. Typing is time consuming and error prone. Being able to click on the label you want is faster and less error prone. (Also, to output the feature point name instead of a number. I have fixed that in my own version.) Of course, we need a way of pre-defining the labels and later modifying those labels.
  2. an easy way to import/export the data into whatever format is being used. The issues are, we will want to change the different types of objects we can recognize. We may also want to remove/add feature points names as we change the model and/or change what we want to recognize. (I don't fully understand how Nimn or the project file works...)
  3. store the images within the tree structure of the web app, so that relative path names can be managed and output to the XML file. This is because dlib XML needs to have the relative path names. (If you're managing thousands of image files, putting them all in one directory is untenable.) . The files need to be in the web server's directory structure because of limitations of web servers (due to security). This issue isn't that important to me, as I wrote a python program to patch the imglab generated XML file to fix the relative path names.
  4. minor feature: being able to color-code the points by type. This helps the labeler see potential errors. Right now, all the feature points are red dots.
  5. minor feature: show list of points (the way it is now) and modify the label or feature name via a popup menu. (I'm trying implement that now, but my ignorance of riot js is slowing me down...)

Watch for changes, or Bookmark for easy discovery.
Fund this project for new features and maintenance.
[Showcase] your project with us by raising an issue


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files, tests, or entry points are named. First clarify which of the five requested features is in scope, then inspect the current label, feature-point, import/export, and image-path workflows; done requires an agreed subset implemented with verification for its stated labeling behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
html, javascript, python
Domain
data, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.