Support for complex terrain
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 112
- Forks
- 49
- Avg merge
- 12h 52m
- Merged PRs (30d)
- 2
Description
Milos Rompar has been using PyDDA to retrieve winds from a radar/lidar network where the domain includes a 1400 m hill where the radar is. Since we assume flat terrain in our retrieval, there would definitely be some inaccuracy in the winds since we do not consider the terrain.
I think adding a complex terrain constraint would be as simple as constraining the gradient of the cost function to be zero at and below the ground. I'm looking for people to work with on implementing such terrain maps so that we can test out such a feature.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named in the issue. Start by locating the wind-retrieval cost function and determine how terrain maps could be represented; the work is complete when complex-terrain constraints are implemented and tested for the radar/lidar network case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100