Skip to content
This repository has been archived by the owner on Mar 21, 2024. It is now read-only.

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Normalization of PET for head and neck tumor segmentation problem #728

Closed
davidkvcs opened this issue May 24, 2022 · 0 comments
Closed

Normalization of PET for head and neck tumor segmentation problem #728

davidkvcs opened this issue May 24, 2022 · 0 comments

Comments

@davidkvcs
Copy link

davidkvcs commented May 24, 2022

Hello.

I see that HeadAndNeckBase uses norm_method=PhotometricNormalizationMethod.CtWindow.
Which normalization do you recommend I use for a PET channel and how do I set this?
I imagine it is something like adding:
norm_method=[PhotometricNormalizationMethod.CtWindow,PhotometricNormalizationMethod.SimpleNorm ]?
to my HNC_tumor_dgk_HeadAndNeckBase class? (See below.)

You can see some more details about my problem and HNC_tumor_dgk_HeadAndNeckBase class below.


I am implemting InnerEye for tumor segmentation of head and neck cancer patients on PET-CT images.
The training data, which we cannot upload to Azure or other cloud services, consists of 835 annotated PET-CT cases.
I am implementing multiple major openly and freely available methods for my problem, and comparing the performance of these. Inner-Eye is one of them.

I have read your documentation and I have defined a new class for my problem:

from pathlib import Path
from InnerEye.ML.configs.segmentation.HeadAndNeckBase import HeadAndNeckBase

class HNC_tumor_dgk_HeadAndNeckBase(HeadAndNeckBase):
    def __init__(self) -> None:
        super().__init__(
            ground_truth_ids=["tumor"],
            image_channels=["ct", "pet"],
            local_dataset=Path("<my/local/path/to/the/data>"),
            enable_logging_outside_azure_ml=True,
            num_dataload_workers=24,
            max_num_gpus=1
            )

And correspondingly my dataset.csv looks like this:

subject,filePath,channel
1,path/to/case1_000_0000.nii.gz,ct
1,path/to/case1_000_0001.nii.gz,pet
1,path/to/case1_000.nii.gz,tumor
2,path/to/case2_001_0000.nii.gz,ct
2,path/to/case2_001_0001.nii.gz,pet
2,path/to/case2_001.nii.gz,tumor
...
835,path/to/case835_001_0000.nii.gz,ct
835,path/to/case835_001_0001.nii.gz,pet
835,path/to/case835_001.nii.gz,tumor

AB#6003

@microsoft microsoft locked and limited conversation to collaborators May 24, 2022
@ant0nsc ant0nsc converted this issue into discussion #731 May 24, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant