Add GridDataInterpolator.
Fixes 2D interpolation for uneven grids.
Closes #29 (closed).
Merge request reports
Activity
requested review from @mfackeld
assigned to @mrieger
I would say the choices for the interpolation kind (for the
GridDataInterpolator
) is already more than enough for a user to make (maybe even via a Parameter if that's not yet possible). As far as I can see only thequintic
interpolation kind is not supported then, but I doubt that anyone ever used that one (or will use it in the future).What do you think?
In addition, one could now end up by choosing
quintic
interpolation via CLI while using unstructured data (now an Error is/has to be raise). You have to know in advance which interpolation kind is a valid choice, which not everyone knows. Personally, I'd prefer interpolation choices which work with any set of points (unstructured and structured).Fully agree on making things easier for the user, but there's an additional complication I didn't mention ... The unordered interpolator really just can interpolate, while the others (including the currently used
InterExtrapolator
) can also extrapolate.I removed the "quintic" one and added an internal switch that picks the GridData interpolator in case the grid is uneven, and the (still better) InterExtrapolator otherwise (+ a better task parameter description). Sounds good?
mentioned in commit ef3c5d8a