openradar / openradar/PyDDA

Support for point observations (wind profilers, rawinsondes as point obs)

Open
#24 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted
Dominant language
Jupyter Notebook
Stars
112
Forks
49
Avg merge
12h 52m
Merged PRs (30d)
2

Description

I eventually wish to see a way of constraining against point observations. This may have to be done with a separate cost function that weighs in how far certain points deviate from the point observations. This would be useful for integrating in data points from wind profilers, surface based observations (METARs, etc.), uninterpolated radar gates, and from rawinsonde data whose horizontal displacement varies throughout the launch.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue identifies no files, tests, or entry points. Begin by locating the existing cost-function and observation-handling paths, then clarify how point observations from wind profilers, METARs, radar gates, and rawinsondes should be represented and weighted. Done requires an agreed implementation scope and validation for these point-observation sources.

Written by the indexing model from the issue text.

Assessment

Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.