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

ResNet encoder difference #2312

Closed
Malitha123 opened this issue Jun 22, 2024 · 3 comments
Closed

ResNet encoder difference #2312

Malitha123 opened this issue Jun 22, 2024 · 3 comments
Assignees

Comments

@Malitha123
Copy link

Hi,

Just out of curiosity, what is the fundamental difference between the ResEnc M, ResEnc L and ResEnc XL in architecture wise? Does it change the depth of the network?

@GregorKoehler
Copy link

Hi,

unfortunately, I can't give a concise answer to this, but in this file you can follow the algorithm for how the plans are set for a given configuration:
https://github.com/MIC-DKFZ/nnUNet/blob/master/nnunetv2/experiment_planning/experiment_planners/residual_unets/residual_encoder_unet_planners.py

Look at the get_plans_for_configuration method and what changes for the M / L / XL configurations (hint: UNet_reference_val_2d / UNet_reference_val_3d).

If that doesn't help, I'd propose creating plans for the individual configurations (M / L / XL) in your case (dataset) and looking at the plans differences.

A rough overview would be:
For determining the network topology, this function is used:
https://github.com/MIC-DKFZ/nnUNet/blob/master/nnunetv2/experiment_planning/experiment_planners/network_topology.py#L30

The above-mentioned get_plans_for_configuration progressively reduces the patch size to match the target GPU memory estimate and adapts the topology following get_pool_and_conv_props.

I hope this helps!

@Malitha123
Copy link
Author

Thank you for your response. I will take a look

@GregorKoehler
Copy link

In order to not have this issue stale for a while, I'll close it for now. Feel free to re-open if questions arise which can't be answered from the documentation.

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

2 participants