dwave-examples / dwave-examples/resource-constrained-project-scheduling
Add a description of "OK Runs" versus "Runs"
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Mathematical Programming System
- Stars
- 1
- Forks
- 0
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
I don't see an explanation of "OK Runs" that is shown in the Results page. Otherwise the rest is intuitive, just this one was unclear to me.
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 at the Results page and locate the existing explanation for the “Runs” and “OK Runs” values. Add a clear description of how “OK Runs” differs from “Runs,” then verify the wording is visible and understandable alongside the displayed results.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100