# Exporting Curvature Data

**URL:** <https://discourse.slicer.org/t/exporting-curvature-data/23181>\
**Category:** Support\
**Tags:** vmtk, centerlines\
**Created:** [April 28, 2022, 4:47pm UTC](https://discourse.slicer.org/t/exporting-curvature-data/23181 "2022-04-28T16:47:17Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![smoudour](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/smoudour/32/18451_2.png) [@smoudour](https://discourse.slicer.org/u/smoudour)\
**Post date:** [October 31, 2023, 8:52am UTC](https://discourse.slicer.org/t/exporting-curvature-data/23181/22 "2023-10-31T08:52:27Z")

</div>

I’m using version 5.4.0. Considering vessel thickness, I think this is the best I can do after processing the CCTA scans with Vesselness Filtering and Segment Editor to isolate the vessels. If I decrease the threshold (to capture more detail) I get a lot of artifacts.

---

<div class="post-metadata">

**Author:** ![bserrano](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/bserrano/32/17034_2.png) [@bserrano](https://discourse.slicer.org/u/bserrano)\
**Post date:** [October 31, 2023, 8:59am UTC](https://discourse.slicer.org/t/exporting-curvature-data/23181/23 "2023-10-31T08:59:24Z")

</div>

Have you tried local threshold in segment editor? It requires a bit of manual post processing anyway but depending on the image you can achieve good results

---

<div class="post-metadata">

**Author:** ![smoudour](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/smoudour/32/18451_2.png) [@smoudour](https://discourse.slicer.org/u/smoudour)\
**Post date:** [October 31, 2023, 9:00am UTC](https://discourse.slicer.org/t/exporting-curvature-data/23181/24 "2023-10-31T09:00:48Z")

</div>

I used generic threshold functionality and then isolated segmnes using the islands tool. Do you think local threshold does a better job? I will give it a try, thanks!

---

<div class="post-metadata">

**Author:** ![bserrano](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/bserrano/32/17034_2.png) [@bserrano](https://discourse.slicer.org/u/bserrano)\
**Post date:** [October 31, 2023, 9:26am UTC](https://discourse.slicer.org/t/exporting-curvature-data/23181/25 "2023-10-31T09:26:48Z")

</div>

Maybe it’s just a visualization thing but try to turn off smoothing  
 ![imagen](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/d/4/d4e625086b24af69e4ce9f6c22019c1620e6d3f6.png)

---

<div class="post-metadata">

**Author:** ![mssm](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/mssm/32/76622_2.png) [@mssm](https://discourse.slicer.org/u/mssm)\
**Post date:** [August 6, 2024, 6:03am UTC](https://discourse.slicer.org/t/exporting-curvature-data/23181/26 "2024-08-06T06:03:47Z")

</div>

Thanks everyone.

This thread was very helpful to me.  
Thanks to you, I was able to print the list of curvature values ​​in the Python console.  
But it would have been nice to be able to export it as a CSV or xlxs file. It’s kind of tedious to copy the listed numbers from the Python console and put carriage returns between the numbers.  
Does anyone have a good idea to export the curvature list in an Excel compatible format?

Regards,

[Previous page](https://discourse.slicer.org/t/exporting-curvature-data/23181.md?page=1)