Hi,

One sentence summary:
Instead of obtaining a _smo output for a parameterized mesh, I get the Visual Fortran run-time error:
forrtl:severe (38): error during write, unit -1, file CONOUT$. Stack trace terminated abnormally.

What works:
I am running  SPHARM-MAT on a Windows 7 x64 system with Matlab 2010b.
I compiled the two required mex files successfully.
I can successfully run TopologyFix on examples and also on my own data, and also view the data.

The problem:
When I run Parameterization wiith CALD (I haven't tried PDM yet), whether on a triangular mesh, or on binary blobs, whether on documentation examples or my own, a *_CALD_ini.mat file gets produced
in the initParamCALD directory (also the Logs directory gets produced), and then the above error pops up in a dialog box. Clicking ok resuts in Matlab closing.
An example log of what is happening when I click on "run" in order to parameterize:
----------------- matlab command window output ------------------
letterE_obj:   +4 = 147 (147) vertices * 2 - 290 faces; 435 edges
after pca min_max_number: 1 1
Solving simultaneous Linear Equations for latitude ...
Solving simultaneous Linear Equations for longitude ...
North Pole : 00039 (0.000000, -0.500000) pi
South Pole : 00121 (0.000000, 0.500000) pi
East Center: 00030 (-0.469237, 0.018061) pi
West Center: 00045 (0.459109, 0.076829) pi
Solving simultaneous Linear Equations for longitude ...
Solving simultaneous Linear Equations for longitude ...
Warning: The fourth output, VERSN, of FILEPARTS will be removed in a future
release.
> In fileparts at 35
In smootheCALD at 38
In SpharmMatParamTriaMesh at 54
In SpharmMatParameterization at 48
In SPHARM_MAT>RunTag_Callback at 601
In gui_mainfcn at 96
In SPHARM_MAT at 70
==> reduce 4692.812319, enlarge 336.834794, objmean 173.447663, prmmean 339.471099
--- letterE_CALD_ini:   +4 = 147 vertices * 2 - 290 faces
save param_vs, obj_vs, faces, extents, reso to infile ...
------------ end of matlab command window output -------------
I tried running matlab as administrator, same result. Same result with any of the provided examples.
I googled this error, and found one entry where someone had a similar problem, a matlab support person said that one should consult with the provider of the mex files.

Any help with this would be appreciated.
Khaled Khairy

Hi all,

Update:

I updated the Matlab version that I was using from 2010b to 2012b, and it seems to run normally now.
To make it work under 2012b however, a two minor tweaks are necessary due to incompatibility of the new matlab functions with the old ones.
1] It will always complain about fileparts. All you need to do is delete the last output variable "ver" from all calls to fileparts that you encounter.
2] the call to the function "union". The original call to union was in the form:
output = union(a, b, c);
it does not accept this form anymore,
So I edited it to
output = union(a,b);
output = union(output,c);

It works now, and I hope I didn't break the code by doing this.
All the best wishes
Khaled Khairy

Hi Khaled,

Thanks very much for your helpful information.

Best,

Li

Thank you very much!
Originally posted by Khaled Khairy: