Add searchableSurface single point getVolumeType
For #921 (closed) we need to cycle over potentially several surfaces and faces. It is too slow and costly to use the getVolumeType for the list of points - need the lowest level single point query.
Site will likely be offline for maintenance 23/24 April - more details soon
For #921 (closed) we need to cycle over potentially several surfaces and faces. It is too slow and costly to use the getVolumeType for the list of points - need the lowest level single point query.
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Link issues together to show that they're related. Learn more.
all searchableSurface api uses list of points/vectors since there might be a lot of overhead doing it on a point by point basis. E.g. distributedTriSurfaceMesh which builds send/receive map and sends over lots of data.
I figured that we probably need both, In most cases, the detailed acceptance method can be a file inline static to minimize code duplication and maximize efficiency.
It used to have a single point API. We scrapped it since it hardly ever was worth the saving in overhead (only for trivial shapes) and excluded a lot of potential optimisations (e.g. distributeTriSurfaceMesh). Instead we rely on the caller to pre-collect queries.
Probably was a premature optimization on my part. I wanted to avoid unnecessary looping over points (when there is a list of searchable surfaces), but this use is probably fairly rare and then we have a number of other issues as you pointed out. I'll close this out.
closed
mentioned in issue #929 (closed)