searchbox in the overset is expected to move along the motion of the object, rather than fixed in the space
Functionality to add/problem to solve
(Brief scope)
In overset function, searchbox is set to narrow the search area and improve the hole-search efficiency. However, the searchbox is fixed in the mesh, other than moving along with the object.
Target audience
(Who will benefit from the changes?) (What type of cases?)
The efficiency of overset function can be benefited by setting the searchbox moving along the object.
Proposal
(How are we going to solve the problem?)
1 extract the mesh motion from Mesh class, 2 add the mesh motion to searchbox, which reduces the size of the searchbox and improve the efficiency of the overset mesh.
I find the motion is calculated from transformation and transformPoints. I would like to isolate the displacement for searchbox motion.
What does success look like, and how can we measure that?
(What are the success factors and acceptance criteria? e.g. test cases, error margins)
I think the tutorial case can be a test case.