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

Struggling with Registering Two VEDO Volume Data #1204

Open
skhwhu opened this issue Nov 26, 2024 · 1 comment
Open

Struggling with Registering Two VEDO Volume Data #1204

skhwhu opened this issue Nov 26, 2024 · 1 comment

Comments

@skhwhu
Copy link

skhwhu commented Nov 26, 2024

Struggling with Registering Two VEDO Volume Data

I'm currently engaged in a task where I need to register two volume data from VEDO. I've been attempting to utilize various libraries like SimpleITK with its Elastix registration capabilities to get this done.

I know that accurate registration of volume data is essential for further analysis and understanding, especially when it comes to dealing with the complex 3D data that VEDO offers. However, despite my numerous tries and adjustments of parameters according to the library documentation, I just can't seem to make it work.

I've explored different aspects such as setting up the initial transforms, choosing appropriate similarity metrics, and tweaking the optimization algorithms, but still, no success.

So, I'm really hoping that there are some good examples out there that can demonstrate how to effectively register these two VEDO volume data using libraries like SimpleITK's Elastic or other relevant ones. Any guidance or references to such examples would be extremely helpful and would surely save me a great deal of time and headache in this rather frustrating process.

Thanks a lot in advance for any kind of assistance!

@marcomusy
Copy link
Owner

marcomusy commented Nov 28, 2024

Hi @skhwhu I can only offer support for vedo and indeed you may find other tools that offers registration capabilities...
I see basically 2 options.

  • doing it directly at the level of Volume needs assuming you know e few corresponding points that are supposed to match
  • use a preliminary step by creating an isosurface to determine such points more easily.

If the registration is meant to be automatic then it becomes an optimization problem.
you may want to share some image of your specific task to have a better intuition of your objectives.

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

No branches or pull requests

2 participants