FireDynamics / FireDynamics/propti
Check if sampling limits make sense
Open
- Dominant language
- Python
- Stars
- 17
- Forks
- 127
- PR merge metrics
- No merged PRs in 30d
Description
Implement a check to determine if the upper parameter sampling limit is actually larger than the lower one - for catching typos and improve debugging.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Python entry point that accepts or processes the upper and lower sampling limits, then inspect how those parameters are currently validated. Done means an upper limit that is not larger than the lower limit is detected with a useful debugging error; no file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100