Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Input boundary mesh format #1

Open
chenming-wu opened this issue Mar 23, 2017 · 1 comment
Open

Input boundary mesh format #1

chenming-wu opened this issue Mar 23, 2017 · 1 comment
Labels

Comments

@chenming-wu
Copy link

chenming-wu commented Mar 23, 2017

Hi! Thanks for providing such a good library to process medical images and volumes.

I have a question when I was trying to run the calculate-volume-map executable program, the input mesh should be piecewise linear complex or tetrahedral mesh generated from PLC accordingly. I tried both *.off and *.obj formats which are pretty common in mesh processing but failed. My question is what format of PLC should I use? Thanks.

@schuhschuh
Copy link
Member

Thanks, I use the VTK XML format usually (.vtp). However, the tools should be able to read surface meshes from .off or .obj files. Is the problem indeed of reading the meshes or the actual computation of a volumetric map? The Mapping module is still in a rather experimental stage. Computing harmonic maps worked fine in my tests, but that's a while back.

Can you be more clear what "failed" means? Do you get any error from the program?

If the error is this one, the problem might rather be that your input files don't specify the boundary (surface) map as expected. In this case it might be best to use VTK's file format which makes it easier to manage the additional point data. See also the convert-pointset and copy-pointset-attributes commands for preparing your input. Also, if you don't have boundary maps yet, maybe calculate-surface-map can help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants