version 1.11 - Dec 3 2017 - by Yuyin Zhou and Lingxi Xie
Please note: an improved version of OrganSegC2F named OrganSegRSTN is available: https://github.com/198808xc/OrganSegRSTN
It outperforms OrganSegC2F by 84.50% vs. 82.37% on the NIH pancreas segmentation dataset.
Also NOTE: some functions have been optimized in the repository OrganSegRSTN, but not yet been transferred here.
I will do these things in the near future - they do not impact performance, but will make the testing process MUCH faster.
Yuyin Zhou proposed the algorithm, created the framework and implemented main functions. Lingxi Xie later wrapped up these codes for release.
Yuyin Zhou, Lingxi Xie, Wei Shen, Yan Wang, Elliot K. Fishman, Alan L. Yuille, "A Fixed-Point Model for Pancreas Segmentation in Abdominal CT Scans", in International Conference on MICCAI, Quebec City, Quebec, Canada, 2017.
https://arxiv.org/abs/1612.08230
http://lingxixie.com/Projects/OrganSegC2F.html
All the materials released in this library can ONLY be used for RESEARCH purposes.
The authors and their institution (JHU/JHMI) preserve the copyright and all legal rights of these codes.
Before you start, please note that there is a LAZY MODE, which allows you to run the entire framework with ONE click. Check the contents before Section 4.3 for details.
OrganSegC2F is a code package for our paper: Yuyin Zhou, Lingxi Xie, Wei Shen, Yan Wang, Elliot K. Fishman, Alan L. Yuille, "A Fixed-Point Model for Pancreas Segmentation in Abdominal CT Scans", in International Conference on MICCAI, Quebec City, Quebec, 2017.
OrganSegC2F is a segmentation framework designed for 3D volumes. It was originally designed for segmenting abdominal organs in CT scans, but we believe that it can also be used for other purposes, such as brain tissue segmentation in fMRI-scanned images.
OrganSegC2F is based on the state-of-the-art deep learning techniques. This code package is to be used with CAFFE, a deep learning library. We make use of the python interface of CAFFE, named pyCAFFE.
It is highly recommended to use one or more modern GPUs for computation. Using CPUs will take at least 50x more time in computation.
| Folder/File | Description |
|---|---|
README.txt |
the README file |
| DATA2NPY/ | codes to transfer the NIH dataset into NPY format |
dicom2npy.py |
transferring image data (DICOM) into NPY format |
nii2npy.py |
transferring label data (NII) into NPY format |
| DiceLossLayer/ | CPU implementation of the Dice loss layer |
dice_loss_layer.hpp |
the header file |
dice_loss_layer.cpp |
the CPU implementation |
| OrganSegC2F/ | primary codes of OrganSegC2F |
coarse2fine_testing.py |
the coarse-to-fine testing process |
coarse_fusion.py |
the coarse-scaled fusion process |
coarse_surgery.py |
the surgery function for coarse-scaled training |
coarse_testing.py |
the coarse-scaled testing process |
coarse_training.py |
the coarse-scaled training process |
DataC.py |
the data layer in the coarse-scaled training |
DataF.py |
the data layer in the fine-scaled training |
fine_surgery.py |
the surgery function for fine-scaled training |
fine_training.py |
the fine-scaled training process |
init.py |
the initialization functions |
oracle_fusion.py |
the fusion process with oracle information |
oracle_testing.py |
the testing process with oracle information |
run.sh |
the main program to be called in bash shell |
utils.py |
the common functions |
| OrganSegC2F/prototxts | primary codes of OrganSegC2F |
deploy_1.prototxt |
the prototxt file for 1-slice testing |
deploy_3.prototxt |
the prototxt file for 3-slice testing |
training_C1.prototxt |
the prototxt file for 1-slice coarse-scaled training |
training_C3.prototxt |
the prototxt file for 3-slice coarse-scaled training |
training_F1.prototxt |
the prototxt file for 1-slice fine-scaled training |
training_F3.prototxt |
the prototxt file for 3-slice fine-scaled training |
Without them, you will need 50x more time in both training and testing stages.
3.2.1 Download a CAFFE library from http://caffe.berkeleyvision.org/ .
Suppose your CAFFE root directory is $CAFFE_PATH.
dice_loss_layer.hpp -> $CAFFE_PATH/include/caffe/layers/
dice_loss_layer.cpp -> $CAFFE_PATH/src/caffe/layers/
Please follow these steps to reproduce our results on the NIH pancreas segmentation dataset.
NOTE: Here we only provide basic steps to run our codes on the NIH dataset. For more detailed analysis and empirical guidelines for parameter setting (this is very important especially when you are using our codes on other datasets), please refer to our technical report (check our webpage for updates).
4.1.1 Download NIH data from https://wiki.cancerimagingarchive.net/display/Public/Pancreas-CT .
You should be able to download image and label data individually.
Suppose your data directory is $RAW_PATH:
The image data are organized as $RAW_PATH/DOI/PANCREAS_00XX/A_LONG_CODE/A_LONG_CODE/ .
The label data are organized as $RAW_PATH/TCIA_pancreas_labels-TIMESTAMP/label00XX.nii.gz .
Put dicom2npy.py under $RAW_PATH, and run: python dicom2npy.py .
The transferred data should be put under $RAW_PATH/images/
Put nii2npy.py under $RAW_PATH, and run: python nii2npy.py .
The transferred data should be put under $RAW_PATH/labels/
Put $CAFFE_PATH under $DATA_PATH/libs/
Put images/ under $DATA_PATH/
Put labels/ under $DATA_PATH/
NOTE: If you use other path(s), please modify the variable(s) in run.sh accordingly.
Several folders will be created under $DATA_PATH:
$DATA_PATH/images_X|Y|Z: the sliced image data (data are sliced for faster I/O).
$DATA_PATH/labels_X|Y|Z: the sliced label data (data are sliced for faster I/O).
$DATA_PATH/lists: used for storing training, testing and slice lists.
$DATA_PATH/logs: used for storing log files during the training process.
$DATA_PATH/models: used for storing models (snapshots) during the training process.
$DATA_PATH/prototxts: used for storing prototxts (called by training and testing nets).
$DATA_PATH/results: used for storing testing results (volumes and text results).
According to the I/O speed of your hard drive, the time cost may vary.
For a typical HDD, around 20 seconds are required for a 512x512x300 volume.
This process needs to be executed only once.
NOTE: if you are using another dataset which contains multiple targets,
you can modify the variables "ORGAN_NUMBER" and "ORGAN_ID" in run.sh,
as well as the "is_organ" function in utils.py to define your mapping function flexibly.
LAZY MODE!
You can run all the following modules with one execution!
- a) Enable everything (except initialization) in the beginning part.
- b) Set all the "PLANE" variables as "A" (4 in total) in the following part.
- c) Run this manuscript!
You need to run X|Y|Z planes individually, so you can use 3 GPUs in parallel.
You can also set COARSE_TRAINING_PLANE=A, so that three planes are trained orderly in one GPU.
The following folders/files will be created:
Under $DATA_PATH/logs/, a log file named by training information.
Under $DATA_PATH/models/snapshots/, a folder named by training information.
Snapshots and solver-states will be stored in this folder.
The log file will also be copied into this folder after the entire training process.
On the axial view (training image size is 512x512, small input images make training faster),
each 20 iterations cost ~8s on a Titan-X Maxwell GPU, or ~5s on a Titan-X Pascal GPU.
As described in the paper, we need ~80K iterations, which take less than 10 GPU-hours.
After the training process, the log file will be copied to the snapshot directory.
You need to run X|Y|Z planes individually, so you can use 3 GPUs in parallel.
You can also set COARSE_TESTING_PLANE=A, so that three planes are tested orderly in one GPU.
The following folder will be created:
Under $DATA_PATH/results/, a folder named by training information.
Testing each volume costs ~20 seconds on a Titan-X Maxwell GPU, or ~13s on a Titan-X Pascal GPU.
The following folder will be created:
Under $DATA_PATH/results/, a folder named by fusion information.
The main cost in fusion includes I/O and post-processing (removing non-maximum components).
In our future release, we will implement post-processing in C for acceleration.
You need to run X|Y|Z planes individually, so you can use 3 GPUs in parallel.
You can also set FINE_TRAINING_PLANE=A, so that three planes are trained orderly in one GPU.
The following folders/files will be created:
Under $DATA_PATH/logs/, a log file named by training information.
Under $DATA_PATH/models/snapshots/, a folder named by training information.
Snapshots and solver-states will be stored in this folder.
The log file will also be copied into this folder after the entire training process.
On the axial view (training image size is ~150x150, small input images make training faster),
each 20 iterations cost ~5s on a Titan-X Maxwell GPU, or ~3s on a Titan-X Pascal GPU.
As described in the paper, we need 60K iterations, which take less than 5 GPU-hours.
After the training process, the log file will be copied to the snapshot directory.
NOTE: Without this step, you can also run the coarse-to-fine testing process. This stage is still recommended, so that you can check the quality of the fine-scaled models.
You need to run X|Y|Z planes individually, so you can use 3 GPUs in parallel.
You can also set ORACLE_TESTING_PLANE=A, so that three planes are tested orderly in one GPU.
The following folder will be created:
Under $DATA_PATH/results/, a folder named by training information.
Testing each volume costs ~5 seconds on a Titan-X Maxwell GPU, or ~3s on a Titan-X Pascal GPU.
NOTE: Without this step, you can also run the coarse-to-fine testing process. This stage is still recommended, so that you can check the quality of the fine-scaled models.
The following folder will be created:
Under $DATA_PATH/results/, a folder named by fusion information.
The main cost in fusion includes I/O and post-processing (removing non-maximum components).
In our future release, we will implement post-processing in C for acceleration.
Fusion is performed on CPU and all X|Y|Z planes are combined.
Currently X|Y|Z testing processes are executed with one GPU, but it is not time-comsuming.
The following folder will be created:
Under $DATA_PATH/results/, a folder named by coarse-to-fine information (very long).
This function calls both fine-scaled testing and fusion codes, so both GPU and CPU are used.
In our future release, we will implement post-processing in C for acceleration.
NOTE: currently we set the maximal rounds of iteration to be 10 in order to observe the convergence. Most often, it reaches an inter-DSC of >95% after 2-3 iterations. If you hope to save time, you can slight modify the codes in coarse2fine_testing.py. Each iteration takes ~20 seconds on a Titan-X Maxwell GPU, or ~15s on a Titan-X Pascal GPU. If you set the threshold to be 95%, this stage will be done within 1 minute (in average).
Congratulations! You have finished the entire process. Check your results now!
NOTE: all these models were trained following our default settings.
The 82 cases in the NIH dataset are split into 4 folds:
- Fold #0: testing on Cases 01, 02, ..., 20;
- Fold #1: testing on Cases 21, 22, ..., 40;
- Fold #2: testing on Cases 41, 42, ..., 61;
- Fold #3: testing on Cases 62, 63, ..., 82.
We provided the coarse-scaled and fine-scaled models on each plane of each fold, in total 24 files.
Each of these models is around 512MB, the same size as the pre-trained FCN model.
- Fold #0: Coarse [X] [Y] [Z] Fine [X] [Y] [Z] (Accuracy: coarse 75.27%, oracle 84.97%, coarse-to-fine 83.65%)
- Fold #1: Coarse [X] [Y] [Z] Fine [X] [Y] [Z] (Accuracy: coarse 75.20%, oracle 82.85%, coarse-to-fine 80.93%)
- Fold #2: Coarse [X] [Y] [Z] Fine [X] [Y] [Z] (Accuracy: coarse 76.06%, oracle 84.00%, coarse-to-fine 82.20%)
- Fold #3: Coarse [X] [Y] [Z] Fine [X] [Y] [Z] (Accuracy: coarse 75.72%, oracle 84.26%, coarse-to-fine 82.91%)
If you encounter any problems in downloading these files, please contact Lingxi Xie ([email protected]).
The current version is v1.11.
To access old versions, please visit our project page: http://lingxixie.com/Projects/OrganSegC2F.html.
You can also view CHANGE_LOG.txt for the history of versions.
If you encounter any problems in using these codes, please open an issue in this repository. You may also contact Yuyin Zhou ([email protected]) or Lingxi Xie ([email protected]).
Thanks for your interest! Have fun!