SimVascular Crashes during ML segmenting

Provides a system for patient-specific cardiovascular modeling and simulation.
POST REPLY
User avatar
Srihari Menon
Posts: 4
Joined: Mon Aug 05, 2019 2:25 pm

SimVascular Crashes during ML segmenting

Post by Srihari Menon » Sat Aug 31, 2019 3:41 pm

Hello,
I'm trying to segment using the multi-vessel path approach. Every time I press the 'Segment using Machine Learning' button, SV starts processing, then gives out an error and crashes. Attached is a snapshot of the terminal shortly before crashing. The last error displayed is "error SVWrapper not loaded" and "Error setting image, sv_wrapper returned null".

Any ideas on what may be wrong?
Attachments
sv_problem_2.png
sv_problem_2.png (109.77 KiB) Viewed 884 times

User avatar
Gabriel Maher
Posts: 32
Joined: Tue Feb 09, 2016 9:17 am

Re: SimVascular Crashes during ML segmenting

Post by Gabriel Maher » Mon Sep 02, 2019 12:10 pm

Hi Srihari,

Thanks for letting us know about this. Could you let me know the following information:

* What kind of image data are you using?
* What file format is the image?
* How are you loading in the image?

Then could you also let me know

* What operating system are using?
* What version of SimVascular are you using, is it the latest one?

Best,

Gabriel

User avatar
Srihari Menon
Posts: 4
Joined: Mon Aug 05, 2019 2:25 pm

Re: SimVascular Crashes during ML segmenting

Post by Srihari Menon » Sat Sep 07, 2019 4:22 pm

Hey Gabriel,

1. I'm studying MRI scans (not sure if thats what you're exactly asking)
2 and 3. I import them initially as .dcm files, but save them in SV collectively as one .vti file. Then once i fire up the SVproj file I think the .vti files are loaded (but i don't actually know where SV is loading the image files from subsequent to the initial import).

I'm operating SimVascular Version 2019.07.10 on windows 10.

User avatar
Nathan Wilson
Posts: 46
Joined: Tue Jun 20, 2006 9:19 am

Re: SimVascular Crashes during ML segmenting

Post by Nathan Wilson » Sat Sep 07, 2019 4:30 pm

Hi,

Please upgrade to the latest Windows release (August 9) as there is a fixed issue related to ML.

Nathan

POST REPLY