CAPE and WETBULB Fortran routines not fully thread safe
Open
Nobody has claimed this yet.
bug
support
- Dominant language
- Python
- Stars
- 498
- Forks
- 178
- PR merge metrics
- No merged PRs in 30d
Description
The reading of the lookup tables might be causing some race conditions when working with dask. Now that WRF-Python's functionality has been ported back to NCL, and NCL is in maintenance mode, the lookup tables should be loaded upon import and passed to the CAPE routines rather than keeping the NCL behavior of reading the file.
Contributor guide
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
Start by locating the CAPE and WETBULB Fortran routines and the lookup-table loading path described in the issue. Reproduce the behavior with dask and inspect how tables are read during concurrent work; done means the tables are loaded on import, passed to the routines, and no race occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran, python
- Domain
- backend, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100