<HTML>
<HEAD>
<TITLE>Re: [Insight-users] ITK Dicom Pixeldata</TITLE>
</HEAD>
<BODY>
<FONT SIZE="2"><FONT FACE="Consolas, Courier New, Courier"><SPAN STYLE='font-size:10pt'>Andy,
> The problem is, that its a little bit slow, because with a dicom
> with 400 slices on the ipad, it costs me 50-52seconds to create
> UIImages(ipad image format) out of the dicom slice pixeldata. But I think
> the ipad is probably to slow for that.
<BR>
The iPad isn’t slow at all. In our experience, the iPad is mainly I/O bound. Apple has a good example of how to populate UIImages a background thread (see below). This has worked very well for us. While our performance is the same as yours (worse, because we bring them across the network), from the user’s perspective we are able to load a 600 slice CT series instantaneously using background threads.<BR>
<BR>
If you desire to run on the iPhone, you will need to do this! It’s performance is much less than the iPad.<BR>
<BR>
Have a look at these two Stack Overflow questions:<BR>
<BR>
<a href="http://stackoverflow.com/questions/3356080/how-to-manage-memory-on-iphone-when-handling-many-images/3356776#3356776">http://stackoverflow.com/questions/3356080/how-to-manage-memory-on-iphone-when-handling-many-images/3356776#3356776</a><BR>
<a href="http://stackoverflow.com/questions/2782454/can-i-load-a-uiimage-from-a-url/2782491#2782491">http://stackoverflow.com/questions/2782454/can-i-load-a-uiimage-from-a-url/2782491#2782491</a><BR>
<BR>
Apple’s LazyTableImages is very helpful:<BR>
<BR>
<a href="http://developer.apple.com/library/ios/#samplecode/LazyTableImages/Introduction/Intro.html">http://developer.apple.com/library/ios/#samplecode/LazyTableImages/Introduction/Intro.html</a><BR>
<BR>
And I would highly recommend this article:<BR>
<BR>
<a href="http://davidgolightly.blogspot.com/2009/02/asynchronous-image-caching-with-iphone.html">http://davidgolightly.blogspot.com/2009/02/asynchronous-image-caching-with-iphone.html</a><BR>
<BR>
Best,<BR>
-dan
<BR>
</SPAN></FONT></FONT>
</BODY>
</HTML>