[slicer-users] map model to volume

András Jakab MD jakaba at med.unideb.hu
Wed Feb 23 05:04:08 EST 2011


Dear Steve / Slicer Users!

I have tried that module, but without much success. Either it gives a
"completed with errors" message instantly after pressing the run button
(log: failed to allocate memory), or it runs for a couple of minutes giving
a bad result, i.e., a volume filled entirely with 255, without any
structures.

I am attaching one model. Space is standard MNI152 space, I wish to map it
to a high resolution T1 template (converted to 0.25 x 0.25 x 0.5 mm voxel
size for this purpose). If the size of data remains a problem (10.000s of
vertices and 500Mb volume files) then please suggest me a CLI-based method
or any custom codes to resolve this.

Thank you very much
András Jakab
----------------------
University of Debrecen / ETH Zürich

On Tue, Feb 22, 2011 at 2:42 PM, Steve Pieper <pieper at bwh.harvard.edu>wrote:

> Hi Andras -
>
> Did you try the PolyData to Label Map module?  It's similar, but it does
> try to fill in the interiors for you.  The two modules were written for
> different purposes and probably should be merged into a single interface at
> some point.
>
> HTH,
> Steve
>
>
> On 02/22/2011 04:12 AM, András Jakab MD wrote:
>
>> Dear Slicer users,
>>
>> Recent Slicer binaries have the feature of "ModelIntoLabelvolume" which
>> is exactly what I needed, as the subject of this message implies.
>>
>> Albeit the application of this module seems to be problematic in my
>> case. I would like to inquire if any of you know a better solution for
>> the following problems.
>>
>> When mapping a model into a volume of high resolution (very high indeed
>> - I need this for thalamus nuclei, 0.25 x 0.25 x 0.5mm) unexpected
>> crashes occur, without any error messages. This is even more pronounced
>> when trying to modify the labelmap with Editor rendering it impossible
>> to modify the results of the ModelIntoLAbelvolume. This must be a memory
>> issue. (Linux binary, latest ones)
>>
>> It would be even better if the algorithm would not exclusively map the
>> vertices into the volume, as this gives a "hollow" result which is very
>> hard to convert to "filled" labelmaps. This is especially true in the Z
>> axis, I have a couple of slices which are more or less empty.
>>
>> Is there a possibility (maybe outside Slicer) to "fill" a .vtk mesh and
>> map what is inside onto a high res image without running into severee
>> memory problems?
>>
>> Thank you very much
>> András Jakab
>>
>>
>>
>> _______________________________________________
>> slicer-users mailing list
>> slicer-users at bwh.harvard.edu
>> http://massmail.spl.harvard.edu/mailman/listinfo/slicer-users
>> To unsubscribe: send email to
>> slicer-users-request at massmail.spl.harvard.edu with unsubscribe as the
>> subject
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://massmail.spl.harvard.edu/pipermail/slicer-users/attachments/20110223/5e789a48/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: VLa.vtk
Type: application/octet-stream
Size: 65893 bytes
Desc: not available
URL: <http://massmail.spl.harvard.edu/pipermail/slicer-users/attachments/20110223/5e789a48/attachment.obj>


More information about the slicer-users mailing list