Adding XLinear_Velocity interpolator #2461
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds an explicit XLinear_Velocity interpolator, effectively moving the code from inside field.py. This improves transparency what is being done in interpolation.
Parcels/src/parcels/_core/field.py
Lines 307 to 315 in eeedce8
First of all, do you agree this would be a good change?
A few more more things to do
Grid_VelcoityandXLinear_Velocitywould be based on grid metadata, in FieldSet creation. @VeckoTheGecko, could you help?_vector_interp_method=None