MeteoSwiss / MeteoSwiss/dvas

Where is the tropopause ?

Open
#224 2 comments 0 reactions 0 assignees View on GitHub
help !!! wontfix
Dominant language
Python
Stars
4
Forks
0
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
We need to clarify/settle on the equation/algorithm for the tropopause. Currently, dvas supports 3 algorithms (`wmo1957`, `mch`, `gruan`) that all follow the 1957 WMO definition, but with the latter two adding some custom tweaks to better handle high-resolution sounding profiles.

We should agree which is best, possibly devising a new (better) option, and clearly describe it in the docs.

For reference, here is the (current) description of the three options in dvas:
```
'wmo1957':
"The first tropopause is defined as the lowest level at which the lapse rate decreases to 2degC/km or less,
provided also the average lapse rate between this level and all higher levels within 2 km does not exceed 2degC/km"

'mch':
The first tropopause is defined as the lowest level at which the lapse rate decreases to 2deg/km or less,
provided also ALL the lapse rateS between this level and all higher levels within 2km do not exceed 2deg/km.

'gruan':
The first tropopause is defined as the lowest level at which the lapse rate decreases to 2deg/km or less,
provided also ALL the MEAN lapse rateS (between this level and all higher levels, COMPUTED FROM ALL
SEQUENTIAL LEVEL PAIRS LOCATED WITHIN A GIVEN LEVEL INTERVAL) within 2 km do not exceed 2deg/km.

```

The `gruan` algorithm typically finds a tropopause level within 1s=~5m of the value quoted in the RS41 and iMS-100 GDPs. The difference may be related, at least in part, to the additional smoothing of the gph profile performed by GRUAN in their GDP assembly chain, which is not implemented in dvas.

Contributor guide

Open the contributing guide

Research direction

Start by comparing the existing `wmo1957`, `mch`, and `gruan` algorithms and their current documentation. Determine which definition should be adopted, whether smoothing or another option is needed, and document the agreed algorithm; completion requires a decided approach and updated docs.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data, documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.