garage.torch.optimizers should have a consistent API

Description

This issue does not include a description.

Contributor guide

Tech stack

pythonpytorch

Domain

backendapideveloper experience

Issue type

refactor

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

needs investigation

Prerequisites

None

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

25

Research direction

The issue lacks a description, so the contributor should first examine the existing optimizer implementations in the garage/torch/optimizers/ directory. Look for inconsistencies in parameter naming, method signatures, or class interfaces across different optimizers. A good starting point would be to review the code and then propose a standardized API, possibly based on PyTorch's optimizer conventions or common reinforcement learning patterns.