Hi Pat,<br><br>Usually, the most like cause of crash is memory shortage. The second cause is the mismatch between the number of images and the supplied b-table. You should avoid receiving the warning of the size mismatch. If you could load the data, please go over all the loaded images listed in the pull-down menu and make sure that the image size is right (for example, if you read 50-slice images as 49-slice image, you can see that the last slice of the first slice is included in the second image and last two slices of the second images are included in the third image, and so on). Also the total number of 3D images should match the number of b-orientations. For example, if you do 1 b0 + 12 DWIs, you should see 13 image listed. If these are not correctly read, it could crash the program.<br>
<br>If you are not sure about your data, you can always send us the data so that we can take a look. Please contact Zhipeng if you want to do so.<br><br>Susumu<br><br><div class="gmail_quote">On Thu, Aug 20, 2009 at 1:43 PM, Patrick Rizzuto <span dir="ltr"><<a href="mailto:prizzut2@jhu.edu">prizzut2@jhu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi all,<br>
<br>
I am attempting to use the DTIStudio component of MRIStudio in order to perform the standard tensor calculations on a .dpf file (post image-registration); however, about a second or so after it asks me about automatic outlier rejection, the program (in particular, the MFC application, according to the popup) invariably crashes, citing an exception at location "0x73ed2659". I have used this same procedure successfully on four other similar AIR-.dpf files, and yet I cannot avoid this problem on this particular .dpf file, even after restarting the computer.<br>
<br>
This same .dpf file is unusual in another way. When first loading it in, it gives me warnings that the (three) .rec file sizes are smaller than the DW-image size. I occasionally received similar warnings for the other .dpf files, but these were easily resolved by tinkering with the number of slices specified in the .dpf file. In this case, though, there does not appear to be a correct number of slices - while it gives me a message that the .rec files are small with 52 slices, it also warns me that the .rec files are too BIG with 51 slices. Let me emphasize that in both cases, the .dpf file successfully loads if the warnings are dismissed, and the brain images look normal - a problem is only revealed once I attempt to perform the calculations.<br>
<br>
The .par files for these .rec files are also different - a few of the parameters that were mentioned in the other .par files are not specified in these 3. In particular, there is no mention of the recon. scan resolution or of the slice thickness. If anyone has any tips on how to resolve this, I would greatly appreciate it.<br>
<br>
Thanks!<br>
Pat Rizzuto<br>
Johns Hopkins Center for Imaging Science<br>
_______________________________________________<br>
Mristudio-users mailing list<br>
<a href="mailto:Mristudio-users@mristudio.org">Mristudio-users@mristudio.org</a><br>
<a href="http://lists.mristudio.org/mailman/listinfo/" target="_blank">http://lists.mristudio.org/mailman/listinfo/</a><br>
Unsubscribe, send a blank email to: <a href="mailto:Mristudio-users-unsubscribe@mristudio.org">Mristudio-users-unsubscribe@mristudio.org</a><br>
</blockquote></div><br>