Hi everyone.  If you have tried using the meshing software and been unsuccesful please report it here.  So far we know of two reasons that cause the software to crash:

1.  The time step is too big

2.  There is not enough RAM on the computer running the software.

But the code is very much in a beta version right now, so if you find other reasons that might be causing the software to crash please report it here.  Hopefully it will be something we can fix.  But if not, we at least want to make users aware of the software's limitations. 

I am very busy finishin up my PhD dissertation at the moment, but hope to have some time to clean up the code in the next few months.

Hi everyone. There are two issues that people have contacted me about over the last few months.

1.  The data types for the .img and .hdr files that are supported are:   SIGNED SHORT, SIGNED INT AND SIGNED FLOAT. (so for example, double is not supported).  So before using this software you will simply need to convert the image to one of the supported types.

2.  If the size of the image is too big, the computer you are using may run out of memory.  ( For reference, about 10 million voxels worked OK with 8 GB of RAM).   If the objects within the image, ie the non-zero voxels, do not push right up against all edges of the image, one simple solution would be to crop off some of the 0-labeled voxels.  After the mesh is created the nodes could simply be moved in the x, y, or z directions to match the corrodinates of the mesh with the original image.

So, unfortantely I am working full time in another area right now and I may not be able to make a comprehensive update to the code.  But, thankfully, a number of people have been able to successful run the existing 'beta' code by following the one page instructions on this site.  And I am still willing to make some future modifications based on the level of need and interest.

Carl