Draft
Conversation
Nearest neighbor for time, interpolation in depth. No extrapolation in depth > nan
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
#close 603
Step 3 of 4 in implementation of vertical skills
General idea of vertical skill is to store data for model and obs in 1d (see below). Depth information is stored in auxilary coordinate z. Befinit of this compared to storing in 2d:
Steps:
Matching strategy
Step 1: Find bracketing model times that contains t_obs
Step 2: Interpolate the two model profiles to obs_depth
Step 3: Interpolate the two model profiles to obs_time
Support vertical mod per commit
Fix missing factory for verticalModel results
Missed during previous PR
Aligning vertical model to vertical obs
Most code in model/vertical.py
Testdata
Tests