Skip to content

vertical_matching#611

Draft
otzi5300 wants to merge 5 commits intovertical-skillfrom
vertical_matching
Draft

vertical_matching#611
otzi5300 wants to merge 5 commits intovertical-skillfrom
vertical_matching

Conversation

@otzi5300
Copy link
Contributor

@otzi5300 otzi5300 commented Mar 17, 2026

#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:

  • Similar to current data structures and current matching workflow can be used
  • Allowing varying z coordinates for obs and sigma layered models

Steps:

  1. BRANCHED FROM Support vertical obs
  2. *BRANCHED FROM Support vertical model items
  3. Matching to get comparer
  4. plotting/skill etc on vertical

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

  • vertical_from_matched.csv (or something

Tests

  • test_match.py: added test for vertical matching in class

@otzi5300 otzi5300 linked an issue Mar 18, 2026 that may be closed by this pull request
@otzi5300 otzi5300 changed the title initial ideas vertical_matching Mar 25, 2026
Nearest neighbor for time, interpolation in depth. No extrapolation in depth > nan
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Matching VerticalObservation and ColumnModelResults

1 participant