ParaToSPHARMMesh completed with errors on win10

(Lxgwd1983) #1

Operating system:win 10
version:SlicerSALT 1.1.0-2018-10-25

I use the example data download from the web. The output of step1 and step2 are correct. but I meet an error on step3. there isn’t any more debug information about this error. is there anybody meets the same problem?
The flowing is the running information and the example data name.

debug imformation
D:/Program Files/SlicerSALT/bin/…/lib/SlicerSALT-4.9/cli-modules/ParaToSPHARMMeshCLP.exe --subdivLevel 10 --spharmDegree 15 --thetaIteration 100 --phiIteration 100 --paraOut --FinalFlip 0 C:/Users/X711/AppData/Local/Temp/SlicerSALT/GAEI_vtkMRMLModelNodeG.vtp C:/Users/X711/AppData/Local/Temp/SlicerSALT/GAEI_vtkMRMLModelNodeH.vtp D:/Program Files/SlicerSALT/data/OutData/Step3_ParaToSPHARMMesh/InputImage_pp_surf
ParaToSPHARMMesh terminated with an unknown exception.

data name
Aim 2.0. SPHARM-PDM00

(Beatriz Paniagua) #2


We have uploaded new nightly packages to our SlicerSALT repository.
Could you please try this one and let us know how it goes?

Thank you,

(Marcellus Augustine) #3

Hi Beatriz,

I was having the same problem. I downloaded the nightly packages using the link you posted, but the ParaToSPHARMMesh step was once again completed with errors.
I have attached the screenshot of the error (the file names do not correspond to patient data as this project does not involve any):

Steps SegPostProcess and GenParaMesh completed without any errors.

Thank you very much.

(Beatriz Paniagua) #4

Dear Marcellus,

Sorry for the delay in responding. Thank you for reporting this problem. The names do not match patient data because commandline reports the names of the nodes in the Slicer MRML scene.

In order to diagnose the problem, could you please let us know the contents of the three subfolders in the output folder?


(Oskars) #5

Dear Beatriz,

I will just chime in on the conversation as I have had the same issue since I tried using the module. I’ve attached an image from the error log showing the saved files, once the ParaToSPHARMMesh fails, as in the last step does not generate any new files whatsoever. As Marcellus mentioned, SegPostProcess and GenParaMesh runs flawlessly. Just to add, I used the available tutorial data for this example, but attempting the process with my own data leads to the same results.


(Beatriz Paniagua) #6

Hi @Maugust and @oradzins

I see, that is weird. Oskars, does your problem also happen in Windows 10?
The problem might be coming from the module or from the ParaToSPHARMMesh executable itself. Could one of you please send the *para.vtk and the *surf.vtk files that produce the problem? I will try to diagnose on my end.

Thank you,

(Oskars) #7

Dear Beatriz,
I’ve added a zip file containing the generated output data from the tutorial example I mentioned previously below (should eb available for the next 30 days):

It ran through about 20 iterations or so, just to create a quick example, but am fairly certain more iterations just prolonged the process and ran into the same error anyway.

I do indeed run windows 10 (Version 1803, OS build 17134.471 if that is of any help). Also the problem has persisted in both SlicerSalt versions 1.0.0 and 1.1.0.

Let me know if there is anything else I can help with.


(Marcellus Augustine) #8

Dear @bpaniagua,

Here are the links to the outputs from steps 1 and 2 (step 3 just produced an empty output folder):

Kind regards,

(Beatriz Paniagua) #9

Hi Marcellus and Oskars

ParaToSPHARMMesh completes in Linux.
See results here:


It seems to be a problem with the executable itself.
It is possible to do

Slicer --launch ParaToSPHARMMeshCLP in Linux, but not on windows.

$ ./SlicerSALT.exe --launch ParaToSPHARMMeshCLP
error: [C:/Program Files/SlicerSALT 1.1.0-2018-12-13/bin/…/lib/SlicerSALT-4.11/cli-modules/./ParaToSPHARMMeshCLP.exe] exit abnormally - Report the problem.

In the meantime, could you try to use the SPHARM-PDM extension in the latest Slicer release? I have been able to run it through Slicer in windows without problems.

$ ./Slicer.exe --launch ParaToSPHARMMeshCLP
One or more required arguments missing!

Brief USAGE:
std::string] [–xml] [–echo]
[–deserialize std::string]
[–serialize std::string]
[–FinalFlip ]
] [–regParaPoints std::string]
[–regParaTemplate std::string]
[–regParaTemplateFileOn] [–verb]
[–medialMesh] [–NoParaAlign]
[–paraOut] [–regTemplate
[–flipTemplate std::string]
[–flipTemplateOn] [–phiIteration
] [–thetaIteration ]
[–spharmDegree ]
[–subdivLevel ] [–]
[–version] [-h] std::string
std::string std::string

We are looking into it here:

We will keep you posted.
Thank you for reporting the bug!