AIM-Harvard / pyradiomics

Open-source python package for the extraction of Radiomics features from 2D and 3D images and binary masks. Support: https://discourse.slicer.org/c/community/radiomics
http://pyradiomics.readthedocs.io/
BSD 3-Clause "New" or "Revised" License
1.11k stars 485 forks source link

Subject: Processing Character Features #851

Open skgtohn opened 7 months ago

skgtohn commented 7 months ago

Dear Community,

I am working on a project to predict the IDH status in glioma using features extracted via Pyradiomics. I've encountered a challenge with certain shape features that are extracted as character strings or tuples rather than single numeric values in the listed features (Elongation, Maximum 2DDiameterColumn,Maximum 2DDiameterRow,Maximum 2DDiameterSlice,Maximum 3DDiameter,Sphericity,Surface Area,Surface Volume Ratio, Voxel Volume,Firstorder Entropy ,Interquartile Range, Kurtosis, Mean, Median). The documentation describes these features as single scalar values, but the output I'm getting includes tuples and even hash strings. For example, the 'original_shape_Elongation' feature should represent the relationship between the two largest principal components, but I am seeing values like "(192, 256, 256)".

Here are some examples of the features and their current formats:

original_shape_Elongation: "(192, 256, 256)" original_shape_Maximum2DDiameterRow: "(0.9000000357627869, 0.8984375, 0.8984375)" original_shape_Maximum3DDiameter: "(27, 103, 91, 57, 60, 47)" original_shape_Sphericity: "(56.54839034712076, 136.01947201370345, 114.27520278099652)" And others with similar issues. My initial thought is to extract meaningful single values from these tuples, possibly considering the maximum value, mean, or even recalculating the feature where possible. How to interpret these tuples and character strings correctly for each feature.

PyRadiomics configuration Add any customization you applied here (i.e. the content of the parameter file used)

PyRadiomics log file image

Version (please complete the following information):

Additional context Add any other context about your question here.

skgtohn commented 7 months ago

I fixed by extracting features separately for each image modality works instead of extracting for multiple modalities together