Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Training and inference on new data for lung nodule detection in ct #578

Open
Thibescobar opened this issue Apr 3, 2024 · 6 comments
Open

Comments

@Thibescobar
Copy link

Hello, I followed the tutorial and model zoo readme to reproduce lung nodule detection on the lunal dataset but i find the bundle to be specific to this dataset.

Is there a way to train and infer on new data easily ?

@longchingkwok331
Copy link

Similar question here
Are you using 3D slicer to do the inference and training ?
I want to know how to to submit the labels to the server, when I am doing the deep edit mode, we can just submit the segmentation for training, but now seems that submitting the .JSON markups is not working

@junxiant
Copy link

junxiant commented Jun 4, 2024

Hello, I followed the tutorial and model zoo readme to reproduce lung nodule detection on the lunal dataset but i find the bundle to be specific to this dataset.

Is there a way to train and infer on new data easily ?

Have you figured this out?

@ericspod
Copy link
Member

ericspod commented Jun 4, 2024

@Can-Zhao @yiheng-wang-nv I think you were both involved with putting this bundle together, would you have some insights here? Thanks!

@yiheng-wang-nv
Copy link
Collaborator

@Can-Zhao @yiheng-wang-nv I think you were both involved with putting this bundle together, would you have some insights here? Thanks!

Hi @Can-Zhao , could you give some suggestions?

@junxiant
Copy link

I have tried training on new data, maybe I can share some?

If we follow the detection tutorial and make some changes:

  1. Data needs to be in .nii.gz format, spacing has to be consistent across all data
  2. Under the config json file, modify the parameters as required. Reduce the patch_size or batch_size if GPU is a constraint.
  3. New dataset's labelling json file needs to follow the original dataset json file format.
  4. In luna16_prepare_env_files.py change the raw_data_base_dir, resampled_data_base_dir to the new data folder location, downloaded_datasplit_dir should be changed to the new dataset's labelling json file. modify the for loop depending if using cross validation folds or not. modify the output names as requried
  5. In luna16_training.py you need to modify the COCOMetric classes parameter to suit the new dataset class

Actually i think there are a lot of things to be changed if training on a new dataset that is not luna16.

If following the model zoo's readme you need to modify all the files in the config folder,

@Can-Zhao
Copy link
Collaborator

Can-Zhao commented Jul 18, 2024

I have tried training on new data, maybe I can share some?

If we follow the detection tutorial and make some changes:

  1. Data needs to be in .nii.gz format, spacing has to be consistent across all data
  2. Under the config json file, modify the parameters as required. Reduce the patch_size or batch_size if GPU is a constraint.
  3. New dataset's labelling json file needs to follow the original dataset json file format.
  4. In luna16_prepare_env_files.py change the raw_data_base_dir, resampled_data_base_dir to the new data folder location, downloaded_datasplit_dir should be changed to the new dataset's labelling json file. modify the for loop depending if using cross validation folds or not. modify the output names as requried
  5. In luna16_training.py you need to modify the COCOMetric classes parameter to suit the new dataset class

Actually i think there are a lot of things to be changed if training on a new dataset that is not luna16.

If following the model zoo's readme you need to modify all the files in the config folder,

That's very helpful! Thank you! I think we should add these to readme file. @yiheng-wang-nv What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants