Segmentation fault about dicomtomesh

[eidelen]

Hi,
Sorry for the late reply. You mentioned that you wanted to open a series dicom. Are there multiple datasets in the same directory? If that is the case, you need to enable USE_VTK_DICOM and get the corresponding library (it is mentioned in the readme). In anyway, USE_VTK_DICOM allows you to handle way more DICOM formats. Me personally, I prefer to use Dicom2Mesh with this option on.
Please let me know if that fixed your issue.

[bo-wu]

That's exactly my case. The problem is solved by the way you described.
Thank you very much!

[eidelen]

Good to hear :-)

[eidelen]

Hi, Well I would not call it physical size. But in number they are the same, independent of the unit. For example, 2.5 mm and 2.5 inch are both 2.5 in mesh unit. About the spacing: I’m pretty convinced that the dicom loader is considering the spacing and gets the necessary parameters (w, h, slice thickness…) from the dicom image. In this project, Dicom2Mesh, we did not observer such problems. However, if these parameters are wrong, the mesh will be deformed. Moving the mesh to the origin happens after creating mesh from the dicom. This step does not introduce any deformation. It is a pure linear transformation.. in fact only a translation. Hope that helps you, Adrian Dr. Adrian Schneider Seefeldstrasse 10, CH-3600 Thun Tel: [phone] [email protected]

…

On 20 Nov 2019, at 13:16, Wu Bo ***@***.***> wrote: Hello Adrian @eidelen <https://github.com/eidelen> , I'm sorry to bother you again. I just have a puzzle and could not to figure it out: dose the reconstructed mesh has the same physical size (in mesh unit) with the ground truth? if not, and I move the mass of mesh to the origin and scale the mesh according the dicom spacing parameters. Will this deform the mesh slightly and make it different from the ground truth? Thanks in advance — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#19>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASJQ6KJKLYH4VNGGROVC4TQUUTDXANCNFSM4JOPEYQA>.

[bo-wu]

You're absolutely right. @eidelen
Using the spacing parameters in dicom file can solve my puzzle.
Thank you very much!