microsoft / microsoft/SkillOpt
A Confusion Regarding s_cur and s_best
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17.3k
- Forks
- 1.6k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 17
Description
In the algorithm description of the paper (page 22), $s_\text{cur}$ is globally initialized only once and updated exclusively when the score improves. This causes $s_\text{cur}$ to increase monotonically and always equal $s_\text{best}$. Is this an intentional design choice?
Algorithm 1 SkillOpt skill optimization
1: scur ← s0, sbest ← s0, C ← ∅, B ← [ ], mmeta ← ∅
...
20: if scorecand > scorecur then
21: scur ← s˜; scorecur ← scorecand
22: if scorecand > scorebest then
23: sbest ← s˜; scorebest ← scorecand
24: end if
...
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 with page 22 and Algorithm 1 in the paper, focusing on the initialization and update conditions for s_cur, s_best, score_cur, and score_best. Confirm whether the described behavior is intentional and clarify the algorithm description so the relationship between the two states and scores is unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100