Store the optimal information in the history file
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 270
- Forks
- 123
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 3
Description
Description of feature
The optimal design is stored in the solution object, but not in the history file (remember that the final iteration may not be the optimal solution). Similar to the last key, we should have an optimal key or something that stores the callCounter corresponding to the optimal solution.
Potential solution
This may require stepping through the solution to try and match a callCounter, maybe that's a bit hacky?
Contributor guide
No contributing guide indexed for this repository
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 code that writes the history file and inspect how the solution object and existing last key are represented. Trace how the optimal solution's callCounter is available, then define completion as the history file exposing an optimal entry that identifies that solution reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100