forked from open-mmlab/mmsegmentation
-
Notifications
You must be signed in to change notification settings - Fork 0
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Checking mergeability…
Don’t worry, you can still create the pull request.
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: czczup/mmsegmentation
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: open-mmlab/mmsegmentation
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: master
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 7 commits
- 29 files changed
- 7 contributors
Commits on Mar 17, 2023
-
Configuration menu - View commit details
-
Copy full SHA for d6079bc - Browse repository at this point
Copy the full SHA d6079bcView commit details
Commits on Mar 23, 2023
-
Configuration menu - View commit details
-
Copy full SHA for 49f2a71 - Browse repository at this point
Copy the full SHA 49f2a71View commit details -
[Feature] Support mmseg with NPU backend. (open-mmlab#2768)
## Motivation Added ascending device support in mmseg. ## Modification The main modification points are as follows: We added an NPU device in the DDP scenario and DP scenario when using the NPU. ## BC-breaking (Optional) None ## Use cases (Optional) We tested [fcn_unet_s5-d16_4x4_512x1024_160k_cityscapes.py](https://github.com/open-mmlab/mmsegmentation/blob/master/configs/unet/fcn_unet_s5-d16_4x4_512x1024_160k_cityscapes.py) .
Configuration menu - View commit details
-
Copy full SHA for ae78cb9 - Browse repository at this point
Copy the full SHA ae78cb9View commit details
Commits on Mar 26, 2023
-
[Doc] Fix inference doc (open-mmlab#2787)
## Motivation open-mmlab#2779
Configuration menu - View commit details
-
Copy full SHA for db09c54 - Browse repository at this point
Copy the full SHA db09c54View commit details
Commits on Mar 30, 2023
-
Configuration menu - View commit details
-
Copy full SHA for 83e7cc2 - Browse repository at this point
Copy the full SHA 83e7cc2View commit details
Commits on May 9, 2023
-
Created KITTI dataset for segmentation in autonomous driving scenario (…
…open-mmlab#2730) Note that this PR is a modified version of the withdrawn PR open-mmlab#1748 ## Motivation In the last years, panoptic segmentation has become more into the focus in reseach. Weber et al. [[Link]](http://www.cvlibs.net/publications/Weber2021NEURIPSDATA.pdf) have published a quite nice dataset, which is in the same style like Cityscapes, but for KITTI sequences. Since Cityscapes and KITTI-STEP share the same classes and also a comparable domain (dashcam view), interesting investigations, e.g. about relations in the domain e.t.c. can be done. Note that KITTI-STEP provices panoptic segmentation annotations which are out of scope for mmsegmentation. ## Modification Mostly, I added the new dataset and dataset preparation file. To simplify the first usage of the new dataset, I also added configs for the dataset, segformer and deeplabv3plus. ## BC-breaking (Optional) No BC-breaking ## Use cases (Optional) Researchers want to test their new methods, e.g. for interpretable AI in the context of semantic segmentation. They want to show, that their method is reproducible on comparable datasets. Thus, they can compare Cityscapes and KITTI-STEP. --------- Co-authored-by: CSH <[email protected]> Co-authored-by: csatsurnh <[email protected]> Co-authored-by: 谢昕辰 <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for a85675c - Browse repository at this point
Copy the full SHA a85675cView commit details
Commits on May 12, 2023
-
[Feature] Add support for the focal Tversky loss (open-mmlab#2791)
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers. ## Motivation The focal Tversky loss was proposed in https://arxiv.org/abs/1810.07842. It has nearly 600 citations and has been shown to be extremely useful for highly imbalanced (medical) datasets. To add support for the focal Tversky loss, only few lines of changes are needed for the Tversky loss. ## Modification Add `gamma` as (optional) argument in the constructor of `TverskyLoss`. This parameter is then passed to `tversky_loss` to compute the focal Tversky loss. ## BC-breaking (Optional) Does the modification introduce changes that break the backward-compatibility of the downstream repos? If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR. ## Use cases (Optional) If this PR introduces a new feature, it is better to list some use cases here, and update the documentation. ## Checklist 1. Pre-commit or other linting tools are used to fix the potential lint issues. 2. The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness. 3. If the modification has potential influence on downstream projects, this PR should be tested with downstream projects, like MMDet or MMDet3D. 4. The documentation has been modified accordingly, like docstring or example tutorials. Reopening of previous [PR](open-mmlab#2783).
Configuration menu - View commit details
-
Copy full SHA for 38900d5 - Browse repository at this point
Copy the full SHA 38900d5View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff master...master