skorch-dev/skorch

Document intermediate value debugging in FAQ

Open

#430 opened on Jan 29, 2019

View on GitHubContributor guide
 (3 comments) (1 reaction) (0 assignees)Jupyter Notebook (414 forks)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (6,171 stars)
PR merge metrics
 (PR metrics pending)

Description

I think this is a topic that is relevant to many users and we can document the multiple output case there as well. See #428 as well.

Contributor guide

Research direction
Review the existing FAQ and the referenced issue #428 to craft a clear explanation of intermediate value debugging.
Tech stack
pythonpytorch
Domain
machine learningdocumentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85