Opening SimVascular on Mac error

[Paulina Wyszkiewicz]

Hello,
I've downloaded the SimVascular for mac but when I click to open it, it tries to do it and then closes immediately. The icon like jiggles on the bottom of the screen like it's trying to open it and then it just disappears. I've tried to delete and re-download it but the same thing happens. Has this happened to anyone or does anyone know what the problem is?
Thank you

[David Parker]

Hi Paulina,

What version of MacOS are you using?

In a terminal run the following command

Code: Select all

/Applications/SimVascular.app/Contents/MacOS/SimVascular

and post what is output to the terminal. It might be that you are missing a system library that SV needs to run.

Cheers,
Dave

[Paulina Wyszkiewicz]

Hi David,
I'm using the newest version, macOS Catalina.

I ran the command and this is what I got.

Screen Shot 2019-11-14 at 5.09.57 PM.png (32.52 KiB) Viewed 842 times

Thank you

[David Parker]

Hi Paulina,

MacOS Catalina has a more strict security policy so it is not letting you execute the command from a terminal.

To allow any executable to run from the Terminal : select System Preferences -> Security & Privacy, and in the Privacy tab, scroll to the list for Developer Tools, check the Terminal app. Then restart the Terminal App and re-run the command.

Cheers,
Dave

[Paulina Wyszkiewicz]

Ok, I have done that and this is what I get when I run the command line again.

Screen Shot 2019-11-14 at 5.55.34 PM.png (528.08 KiB) Viewed 821 times

Screen Shot 2019-11-14 at 5.56.07 PM.png (570.06 KiB) Viewed 821 times

Screen Shot 2019-11-14 at 5.56.20 PM.png (306.94 KiB) Viewed 821 times

[Paulina Wyszkiewicz]

UPDATE: It opens now!!

[Paulina Wyszkiewicz]

Well actually, this is what opens up:

Screen Shot 2019-11-14 at 6.05.04 PM.png (205.16 KiB) Viewed 810 times

But the website says that this is what I am supposed to see:

Screen Shot 2019-11-14 at 6.05.11 PM.png (424.67 KiB) Viewed 810 times

[David Parker]

The error you were seeing before is related to the software used to display the SV Welcome page. This is a known issue on MacOS.

Curious that SV is now opening ...

We have not built SV on Catalina so there may be other issues. Please let me know if you have any other problems.

Cheers,
Dave

[Ryan Pewowaruk]

Hi David,

I'm also similar problems getting SimVascular to run on Mac (10.11.6 El Capitan) where the simvascular immediately crashes when the icon is clicked on.

When trying to run from terminal the following messages occur

Code: Select all

BUNDLE: Applications/SimVascular.app
RESOURCES: Applications/SimVascular.app/Contents/Resources
Check for non-core plugins in /usr/local/sv/svplugins/2019-08-09
No non-core plugins installed for current SimVascular installed version.
ln: /Applications/SimVascular.app/Contents/Resources/../MacOS/simvascular.exe: File exists
Note: Not using the provisioning file. To use a provisioning file, provide --use-pro flag

Reading custom plugins SV_CUSTOM_PLUGINS environment variable...


dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
  Referenced from: /Applications/SimVascular.app/Contents/Resources/svExternals/lib/libpython3.5m.dylib (which was built for Mac OS X 10.13)
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _clock_gettime
  Referenced from: /Applications/SimVascular.app/Contents/Resources/svExternals/lib/libpython3.5m.dylib (which was built for Mac OS X 10.13)
  Expected in: /usr/lib/libSystem.B.dylib

Applications/SimVascular.app/Contents/Resources/simvascular: line 128: 14794 Trace/BPT trap: 5       ${svexe} $*
r-francoisimac:/ localadmin$ Applications/SimVascular.app/Contents/MacOS/simvascular.exe 
dyld: Library not loaded: @rpath/lib_simvascular_post.dylib
  Referenced from: //Applications/SimVascular.app/Contents/MacOS/simvascular.exe
  Reason: image not found
Trace/BPT trap: 5

Thank you,
Ryan

[David Parker]

Hi Ryan,

It looks like the Python library SV uses was built on MacOS 10.13 and is looking for a symbol that is not defined in MacOS 10.11. I will open an Issue on this.

You can upgrade your MacOS to 10.12 or later to solve this problem.

Cheers,
Dave