MrGiovanni / MrGiovanni/ModelsGenesis

Are we loading the whole dataset in the memory?

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

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
791
Forks
141
PR merge metrics
No merged PRs in 30d

Description

Hi! I was trying to adapt the notebook of the downstream task of lung nodule segmentation (link) to brain tumor segmentation (BraTS). I noticed that the whole dataset is loaded in the memory and no pytorch dataloaders are used, nor custom dataloader classes are implemented. Is this the case? Because I am having trouble doing this for BraTS which is a large dataset. Could you perhaps provide the downstream task notebook for BraTS too, so that I can see how you managed to do this?

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.

Research direction

Start with keras/downstream_tasks/lung nodule segmentation.ipynb, the notebook linked in the issue, and inspect how its dataset is loaded. Check whether the full dataset is held in memory and how PyTorch dataloaders could apply to the BraTS adaptation. Done would require a documented loading approach or a BraTS downstream-task notebook that addresses large-dataset handling.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter-notebook, pytorch
Domain
data, machine-learning
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.