# kits19 **Repository Path**: joseph2017/kits19 ## Basic Information - **Project Name**: kits19 - **Description**: The official repository of the 2019 Kidney and Kidney Tumor Segmentation Challenge - **Primary Language**: Python - **License**: MIT - **Default Branch**: master - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 2 - **Created**: 2020-07-18 - **Last Updated**: 2024-06-16 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README # KiTS19 The official [2019 KiTS Challenge](https://kits19.grand-challenge.org) repository. ## Before Cloning This repository makes use of git-lfs. **Make sure to [install git-lfs](https://git-lfs.github.com/) before cloning!** It's very lightweight and works with Windows, Mac, and Linux. For Linux users, I'd recommend downloading and running the installer rather than using PackageCloud. You can verify the initialization by running ``` user@host~$ git lfs --version git-lfs/2.7.1 (GitHub; linux amd64; go 1.12; git 6b7fb6e3) ``` ## Usage To get the data for this challenge, please clone this repository (~20G). The `data/` directory is structured as follows ``` data ├── case_00000 | ├── imaging.nii.gz | └── segmentation.nii.gz ├── case_00001 | ├── imaging.nii.gz | └── segmentation.nii.gz ... ├── case_00209 | ├── imaging.nii.gz | └── segmentation.nii.gz └── kits.json ``` We've provided some basic Python scripts in `starter_code/` for loading and/or visualizing the data. They require the following: * Python >= 3.5.2 * [scipy](https://www.scipy.org/) * [numpy](http://www.numpy.org/) * [nibabel](https://nipy.org/nibabel/) ### Loading Data ```python from starter_code.utils import load_case volume, segmentation = load_case("case_00123") # or volume, segmentation = load_case(123) ``` Will give you two `Nifty1Image`s. Their shapes will be `(num_slices, height, width)`, and their pixel datatypes will be `np.float32` and `np.uint8` respectively. In the segmentation, a value of 0 represents background, 1 represents kidney, and 2 represents tumor. For information about using a `Nifty1Image`, see the [Nibabel Documentation](https://nipy.org/nibabel/manual.html#manual) ([Getting Started](https://nipy.org/nibabel/gettingstarted.html)) ### Visualizing Data The `visualize.py` file will dump a series of PNG files depicting a case's imaging with the segmentation label overlayed. By default, red represents kidney and blue represents tumor. From Bash: ```bash python3 starter_code/visualize.py -c case_00123 -d # or python3 starter_code/visualize.py -c 123 -d ``` From Python: ```python from starter_code.visualize import visualize visualize("case_00123", ) # or visualize(123, ) ``` ### Voxel Spacing Each `Nift1Image` object has an attribute called `affine`. This is a 4x4 matrix, and in our case, it takes the value ``` array([[0. , 0. , -1*captured_pixel_width , 0. ], [0. , -1*captured_pixel_width , 0. , 0. ], [-1*captured_slice_thickness , 0. , 0. , 0. ], [0. , 0. , 0. , 1. ]]) ``` This information is also available in `data/kits.json`. Since this data was collected during routine clinical practice from many centers, these values vary quite a bit. Since spatially inconsistent data might not be ideal for machine learning applications, we have created a branch called `interpolated` with the same data but with the same affine transformation for each patient. ``` array([[ 0. , 0. , -0.78162497, 0. ], [ 0. , -0.78162497, 0. , 0. ], [-3. , 0. , 0. , 0. ], [ 0. , 0. , 0. , 1. ]]) ``` If you have already cloned the repository and would like to download the interpolated data, use the following from your repository root: ``` git fetch git checkout origin/interpolated ``` If you have not yet cloned the repository, and you'd like to download the interpolated data only (~50GB), then you can use the following: ``` git clone -b interpolated --single-branch https://github.com/neheller/kits19 ``` ### Labeling Errors **The data is now frozen until the challenge deadline of July 29.** We've gone to great lengths to produce the best segmentation labels that we could. That said, *we're certainly not perfect*. In an attempt to strike a balance between quality and stability, we've decided on the following policy: If you find an problem with the data, please [submit an issue](https://github.com/neheller/kits19/issues/new) describing it. We will do our best to address all issues *submitted prior to April 5, 2019* by April 15. After that, the data and labels will be set in stone until the MICCAI deadline of July 29. You're welcome to keep submitting issues on this topic after April 5, but the fixes will not be made available until after the 2019 challenge. ### Reference If this data is useful to your research, please cite the following [manuscript](https://arxiv.org/abs/1904.00445) ``` @misc{1904.00445, Author = {Nicholas Heller and Niranjan Sathianathen and Arveen Kalapara and Edward Walczak and Keenan Moore and Heather Kaluzniak and Joel Rosenberg and Paul Blake and Zachary Rengel and Makinna Oestreich and Joshua Dean and Michael Tradewell and Aneri Shah and Resha Tejpaul and Zachary Edgerton and Matthew Peterson and Shaneabbas Raza and Subodh Regmi and Nikolaos Papanikolopoulos and Christopher Weight}, Title = {The KiTS19 Challenge Data: 300 Kidney Tumor Cases with Clinical Context, CT Semantic Segmentations, and Surgical Outcomes}, Year = {2019}, Eprint = {arXiv:1904.00445}, } ```