NatLabRockies / NatLabRockies/windwatts
Uncertainty communication
Open
Nobody has claimed this yet.
question
Results
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 10
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 6
Description
The uncertainty analysis result feature:
- provide some warning about data with high risk
need clarification from the team on requirements
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 reviewing the uncertainty analysis result feature and obtain the missing requirements from the team. Clarify how high-risk data is identified, where the warning should appear, and what behavior confirms the feature is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100