-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Documentation of spatial shape constraints for the networks #6771
Comments
Hi @wyli , I'd like to work on this issue, can you suggest me some related resources that you think is helpful? |
sure, that's great @nhhung1810, please see:
|
Hi @wyli , I think that you refer to all networks under Also, if the number of networks need to be done is a lot, I'll split up into small PRs for each networks, do you fine with that? |
Yes @nhhung1810, separate PRs would be great, high priority ones are
please feel free to start with simple PRs.. we can use this ticket to track the progress (cc @vikashg for any further comments) |
Sure, I will start with UNET++ first |
Hi @wyli I have create a PR here Project-MONAI/tutorials#1476, mentioned in the above Issue Project-MONAI/tutorials#1475. It's not completed, I'm definitely need more advise on this |
Good job @nhhung1810 |
@nhhung1810 is it completed? |
Is your feature request related to a problem? Please describe.
follow up of discussion #6641
would be great to add input spatial size vs model configuration analysis for all the networks such as
swinunetr and dints.
the form of analysis could be detailed tutorials (example https://github.com/Project-MONAI/tutorials/blob/main/modules/UNet_input_size_constrains.ipynb) and/or actual code logic to check the compatibility of the input shape and model configuration.
The text was updated successfully, but these errors were encountered: