Ability to pass an existing `Ops` to Optimizer constructors
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 928
- Forks
- 227
- PR merge metrics
- No merged PRs in 30d
Description
The Optimizer constructor takes a Graph and constructs an Ops instance internally. This prevents users from using Ops.withSubScope() to prefix the name of optimizers.
This problem impacts all Optimizer subclasses.
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 inspecting the Optimizer constructor and each Optimizer subclass, focusing on how Ops is currently created and how Ops.withSubScope() would be supplied. The work is complete when users can pass an existing Ops to all affected constructors and use it to prefix optimizer names consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100