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

When is plan_inference.pkl generated? #238

Closed
dzeego opened this issue Apr 1, 2024 · 3 comments
Closed

When is plan_inference.pkl generated? #238

dzeego opened this issue Apr 1, 2024 · 3 comments
Labels
stale Issue without activity, will be closed soon

Comments

@dzeego
Copy link

dzeego commented Apr 1, 2024

Hello @mibaumgartner,

After finishing the training (multiprocessing error at the last epoch persists) I am trying to run nndet_predict on my test set which is located in the raw_splitted folder in imagesTs.
However, when i launch nndet_predict 0003 RetinaUNetV001_D3V001_3d --fold 0 I get:
FileNotFoundError: [Errno 2] No such file or directory: '/datadrive/nndetection_data/nndetection_models/Task0003_LesionDetection/RetinaUNetV001_D3V001_3d/fold0/plan_inference.pkl'

At what stage does the nndetection generate this file? and how can I mitigate this issue moving forward?

Also for some reason the val_analysis, val_analysis_preprocessed, val_predictions, val_predictions_preprocessed, val_results, and val_results_preprocessed folders were not generated. Is that normal?

Thank you in advance,
Best regards !

@mibaumgartner
Copy link
Collaborator

Dear @dzeego ,

did you run the training command with the --sweep option? - that should generate the plan and results
nndet_sweep can be used to perform this manually -> it will predict the validaiton cases and derive the best set of postprocessing paramters for the validation set (those are the inference parameters which are saved into the plan_inference.pkl.

Copy link

github-actions bot commented May 3, 2024

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale Issue without activity, will be closed soon label May 3, 2024
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issue without activity, will be closed soon
Projects
None yet
Development

No branches or pull requests

2 participants