Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trajectory calculations for the boundary layer #27

Open
lars2015 opened this issue Nov 13, 2023 · 0 comments
Open

Trajectory calculations for the boundary layer #27

lars2015 opened this issue Nov 13, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@lars2015
Copy link
Contributor

Is your feature request related to a problem?

  • MPTRAC may have limited capabilities for calculating trajectories in the boundary layer due to using pressure as vertical coordinate. Meteo data are converted from model level to pressure levels for usage with MPTRAC, which is causing interpolation errors. The pressure coordinate is not terrain-following.
  • More recently, Jan added the option to calculate diabatic trajectories, which provides the option to use meteo data on model levels rather than pressure levels

Describe the solution you'd like

  • Conduct a comparison of trajectory calculations for the boundary layer (model level versus pressure level meteo data) so that we can get an idea of how large the deviations are.
  • Conduct a comparison with HYSPLIT online trajectories (or other models such as FLEXPART or CLaMS) as a reference.
  • Assess what would be needed to make MPTRAC suitable for boundary layer applications.
@lars2015 lars2015 added the enhancement New feature or request label Nov 13, 2023
@lars2015 lars2015 self-assigned this Nov 13, 2023
@lars2015 lars2015 changed the title MPTRAC trajectory calculations for the boundary layer Trajectory calculations for the boundary layer Nov 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant