The static methods _project_and_slide, _seg_intersect_2D, and (probably) _seg_intersect_3D_triangles are about as fast as they are going to be in Python/NumPy, but are still a major bottleneck. One only needs to run an FTLE solve with and without the immersed boundary structures to see the huge difference it makes.
Parallelization will likely do much to solve this problem, since these methods are typically called in a loop over all agents. This would need to be implemented in apply_boundary_conditions, where the loop is.
Another thing that may be considered: since all the action is in static methods, these methods could (relatively) easily be written in C to speed up each calculation to some degree.
The static methods _project_and_slide, _seg_intersect_2D, and (probably) _seg_intersect_3D_triangles are about as fast as they are going to be in Python/NumPy, but are still a major bottleneck. One only needs to run an FTLE solve with and without the immersed boundary structures to see the huge difference it makes.
Parallelization will likely do much to solve this problem, since these methods are typically called in a loop over all agents. This would need to be implemented in apply_boundary_conditions, where the loop is.
Another thing that may be considered: since all the action is in static methods, these methods could (relatively) easily be written in C to speed up each calculation to some degree.