Hi Ben,
is this happening just for this DICOM set?
The fact that you get a crash both in the old VTK-based way (-f) and the
ITK-based one (-ifile)
could be symptomatic of the fact that there's something odd going on with the
DICOMs, although
typically you shouldn't get a crash but an error message.
Are you sure you have enough memory to open the DICOM? I've experienced memory
allocation
limitations on older Windows systems in the past, so if your DICOM series is
very large that might
be it (you should get an "Unable to allocate [something something]" as an error
before the crash).
Hope this helps.
Luca
On Jun 18, 2013, at 5:05 PM, Berkowitz, Benjamin M wrote:
> I'm having problems reading in a DICOM set in the Windows binary. I've tried
> importing using vmtkimagereader with the -f parameter as well as the -ifile
> parameter. I've also just tried using vmtkimageviewer directly. Each time,
> python crashes and it won't open the DICOMs. Is it more likely a problem
> with the files themselves or a bug in VMTK?
>
> Thanks,
>
> Ben
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev_______________________________________________
> vmtk-users mailing list
> vmtk-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/vmtk-users
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
vmtk-users mailing list
vmtk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vmtk-users
