Ability to pass an existing `Ops` to Optimizer constructors

Open
#267 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
machine-learning

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.

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.

Dominant language
Java
Stars
928
Forks
227
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tensorflow/java

All issues in tensorflow/java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.