This topic contains 2 replies, has 2 voices, and was last updated by 
-
Posts
-
In paper of “Interactive Training System for InterventionalElectrocardiology Procedures”,it says the BVH of blood vessel needs to be recomputed at each navigation step since the heart is beating.
But as far as I know,the computation of BVH is very time consuming, it will cost even a few seconds.So when the recomputation is done,the blood vessel probably has changed a lot. So how to solve this problem? I suppose there should be something I have missed.
One way I can think is that precompute all the BVHs corresponding to animate frames of the heart, then store them. When perform collision detection, just read the BVHs’ data corrsponding to current animate frame.As a result,this method avoids recomputing the BVH during navigation step which saves time.
Hi @charles,
I see you are still digging in the papers.
The collision in SOFA works in three steps: broad detection check (using coarse BVH), narrow detection (several options here, by default using discrete intersection) and response.
In the paper we are following this process with:
– broad phase using BVH
– narrow phase using discrete geometries
– Lagrange multipliers resolution of the contacts (as constraints) including friction.One of the perpective of the paper is the last option you mentioned: precomputing information for the collision (BVH or other). This was not implemented for the paper. If I remember properly a distance map was finally precomputed and used for the endocardium.
Does this answer your question?
Best,Hugo
Yes,totally! Thanks a lot!
You must be logged in to reply to this topic.
