roboflow / roboflow/notebooks

Incompatibility of Kaggle Notebooks for Segment Anything V2

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

Nobody has claimed this yet.

bug
Dominant language
Jupyter Notebook
Stars
9.7k
Forks
1.5k
PR merge metrics
No merged PRs in 30d

Description

Search before asking
  • I have searched the Roboflow Notebooks issues and found no similar bug report.
Notebook name

Segment Anything V2 on Custom Data

Bug

[rank0]: Traceback (most recent call last):
[rank0]: File "/usr/local/lib/python3.10/dist-packages/hydra/_internal/instantiate/_instantiate2.py", line 92, in _call_target
[rank0]: return target(*args, **kwargs)
[rank0]: File "/kaggle/working/content/sam2/training/dataset/vos_raw_dataset.py", line 170, in init
[rank0]: subset = os.listdir(self.img_folder)
[rank0]: FileNotFoundError: [Errno 2] No such file or directory: '/content/data/train'

The code in train is hardcoded for content data train, despite renaming the files, the issue still persists.

Environment
  • Kaggle
  • Ubuntu
  • Python 3.11
Minimal Reproducible Example

No response

Additional

No response

Are you willing to submit a PR?
  • Yes I'd like to help by submitting a PR!

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

Start with the “Segment Anything V2 on Custom Data” notebook and trace its training setup against the traceback in sam2/training/dataset/vos_raw_dataset.py. Run the notebook on Kaggle, identify where /content/data/train is selected, and verify that training uses the configured dataset path without the FileNotFoundError.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter-notebook, python, pytorch
Domain
computer-vision, machine-learning
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.