BRODEN dataset, scene number 0

Open
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
32/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
data, machine-learning

Research direction

Start by inspecting BRODEN scene metadata in c_scene.csv and the scene-number reference in sync.txt, then trace how images such as ade20k/ADE_train_00015917.jpg are handled when their scene number is 0. Reproduce the HTML summary with those images; done means the dataset interpretation is resolved and the summary no longer produces missing scene labels.

Written by the indexing model from the issue text.

Description

Hey,

While using your method and BRODEN dataset, I've seen that some images have an associated scene number of 0. This scene number is not defined in c_scene.csv. When checking some images, e.g., "ade20k/ADE_train_00015917.jpg", "ade20k/ADE_train_00008543.jpg", "ade20k/ADE_train_00002038.jpg", I couldn't see any common scene description.

The only reference I've found to a scene number 0 would be in sync.txt but I don't know what this means.

Could it be possible that the scene number 0 is a mistake? I just found it because this lead to issues later on in the code, e.g., generating a HTML summary with missing labels.

Thanks :)

Dominant language
Python
Stars
221
Forks
53
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from CSAILVision/NetDissect-Lite

All issues in CSAILVision/NetDissect-Lite

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.