Thanks Dan, I'll see if I can save those images and put them up tomorrow when I get back to school. I really do hope it's something I'm doing wrong and not a problem with the program.<br><br><div><span class="gmail_quote">
On 9/27/07, <b class="gmail_sendername">Dan Mueller</b> <<a href="mailto:dan.muel@gmail.com">dan.muel@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 28/09/2007, Charlotte Curtis <<a href="mailto:curtisc@uoguelph.ca">curtisc@uoguelph.ca</a>> wrote:<br>> I'm using ITK filters through MeVisLab, it comes with nearly all of them<br>> implemented as modules.
<br><br>Okay.<br><br>> It was my understanding that the stopping value should be somewhere around<br>> the values of the voxels at the edge of the region, which for me is<br>> somewhere between 200 and 1000 HU. I've tried using very large numbers, but
<br>> I still get nothing output.<br><br>The stopping value has nothing to do with the intensity range of the<br>input image -- it tells the algorithm at what *arrival value* the<br>processing should stop. If you are not sure, make the value large or
<br>use the default (which will force the algorithm to take longer to<br>execute, but guarantee you a result).<br><br>> I posted a screenshot from the program showing (left to right): the input<br>> image, the FastMarching dialogue box, and the speed image. It can be found
<br>> at <a href="http://www.uoguelph.ca/~curtisc/MeVisScreenshot.png">http://www.uoguelph.ca/~curtisc/MeVisScreenshot.png</a>.<br><br>Unfortunately a screenshot doesn't help very much. It is best to<br>inspect the raw data (especially the speed function to ensure it is in
<br>the correct range). Can you temporarily save the speed function you<br>are using and post this? Also, the initial trial seed/region would be<br>helpful.<br><br>Cheers, Dan<br></blockquote></div><br>