Problem About Bone Microstructural Analysis on a MicroCt Data

I am trying to perform trabecular separation, trabecular thickness, trabecular number and bone volume/tissue volume analyses on an irregularly shaped segmented area on the microct dataset. While I am getting normal values ​​on the CBCT data, the program does not give any results on the microct data. Do you think there is a problem with my dataset or am I doing something wrong? Can anyone help? Thank you

You need to give more information. What extension are you using to calculate those values? And what do you mean by “program does not give any results on the microct data”? What program?

I am using 3D Slicer V. 5.8.1 with BoneTexture extension. First of all, I create a segment, then go to segment editor and select the area of bone between the roots of rats 1st molar. I create a threshold to select the mineralized area of bone. Then go to segmentations section and exporting a new label map. After that go to BoneTexture extension and select input volume and input labelmap. Then choice the GLCM, GLRLM and BM features. Clicking populate parameters based on inputs and last of it click the compute texture feature set.The results coming for the GLCM features and , GLRLM features but even after a long wait no values for the BM features (Bone Volume Dentisty, Trabecular Thickness, Trabecular Seperation, Trabecular Number) which i want to calculate. The percentage of the load area stuck at %66.
Sorry I am new to this type of bone analysis on micro ct, what I am doing wrong or what I am missing? Is there any other steps?

Murat Maga via 3D Slicer Community <notifications@slicer.discoursemail.com>, 12 Haz 2025 Per, 07:54 tarihinde şunu yazdı:

So steps you describe workflow works for a CBCT, but not a microCT? Is that correct?

MicroCT datasets are often much higher resolution than CBCT. Maybe you are hitting memory limitation. Perhaps downsample your original volume (using Crop Volume) and start fresh.

Also if you hit CTRL+0 (CMD in mac) you can get the log file, and see if there are any errors reported.