深度学习论文: U-Net and its variants for Medical Image Segmentation : A short review

深度学习论文: U-Net and its variants for Medical Image Segmentation : A short review
U-Net and its variants for Medical Image Segmentation : A short review
PDF: https://arxiv.org/pdf/2204.08470v1.pdf
PyTorch代码: https://github.com/shanglianlm0525/CvPytorch
PyTorch代码: https://github.com/shanglianlm0525/PyTorch-Networks

1 U-Net 2015

U-Net适用于医学图像处理的主要原因是在训练数据较少的情况下还能取得不错的性能。

U-Net网络的关键结构就是以下三个部分:

  • 下采样
  • 上采样
  • skip-connection

在这里插入图片描述

Unet: Convolutional networks for biomedical image segmentation

2 U-Net++ 2019

U-NET++网络是为了解决医学图像分割的精确性问题,从而提出的一种新的基于嵌套密集跳跃连接的分割体系结构。改变了原始U-Net网络层数,重新设计原网络中的跳跃连接,添加深度监督对不同分割任务剪枝到合适的网络,达到很好的分割效果。
在这里插入图片描述

UNet++: A Nested U-Net Architecture for Medical Image Segmentation

3 R2U-Net 2018

R2U-Net把RNN和ResNet的结构整合到了encoder-decoder结构里,实验效果很好。
在这里插入图片描述

Recurrent Residual Convolutional Neural Network based on U-Net (R2U-Net) for Medical Image Segmentation

4 Attention U-Net 2018

Attention U-Net将注意力机制应用于UNet分割网络中,可以比较好的实现对显著性区域的关注,以及对无关背景区域的抑制。
在这里插入图片描述
Attention U-Net: Learning Where to Look for the Pancreas

5 Trans U-Net 2021

Trans U-Net在encoder结构上运用 了transformer可以提取更好的特征。
在这里插入图片描述
TransUNet: Transformers Make Strong Encoders for Medical Image Segmentation

  • 0
    点赞
  • 8
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
This error message indicates that there is a conflict between different variants of the `org.jetbrains.kotlin:kotlin-gradle-plugin:1.7.0` dependency that your project is trying to use. The consumer was configured to find a runtime of a component compatible with Java 11, packaged as a jar, and its dependencies declared externally, but it cannot choose between the available variants of the dependency. To resolve this issue, you can try the following steps: - Check if your project is explicitly declaring a version of the `org.jetbrains.kotlin:kotlin-gradle-plugin` dependency that conflicts with the version required by the consumer (in this case, Java 11). If so, try updating the project to use the correct version of the dependency. - If the above step does not work, you can try adding a resolution strategy to your build script to force Gradle to choose the correct variant of the dependency. For example, you can add the following code to your `build.gradle` file: ``` configurations.all { resolutionStrategy { eachDependency { DependencyResolveDetails details -> if (details.requested.group == 'org.jetbrains.kotlin' && details.requested.name == 'kotlin-gradle-plugin' && details.requested.version == '1.7.0') { details.useVersion('1.7.0') } } } } ``` This code tells Gradle to use version `1.7.0` of the `org.jetbrains.kotlin:kotlin-gradle-plugin` dependency whenever it is required, regardless of any conflicting versions that may be present. If neither of these steps work, you may need to investigate further to find the root cause of the conflict.

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值