Project-MONAI / Project-MONAI/MONAI
Support for pre-activation residual blocks in SwinUNETR
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.7k
- Forks
- 1.6k
- Avg merge
- 5d 1h
- Merged PRs (30d)
- 20
Description
Is your feature request related to a problem? Please describe.
SwinUNETR v2 (https://rdcu.be/dnwDO) suggest the use of pre-activation residual blocks. As it stands, the MONAI implementation of SwinUNETR only accommodates post-activation residual blocks (setting res_block = True when calling UnetrBasicBlock).
Describe the solution you'd like
An option to specify whether pre- or post-activation should be used when initializing UnetrBasicBlock.
UnetrBasicBlock calls monai.networks.blocks.dynunet_block.UnetResBlock during init; the latter can be easily changed to accept an additional str input specifying the type of residual block required.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read UnetrBasicBlock and monai.networks.blocks.dynunet_block.UnetResBlock first, focusing on how the current post-activation residual block is selected during initialization. Define an option that selects pre- or post-activation behavior while preserving the existing default, then verify both choices through the relevant block and SwinUNETR tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100