microsoft/InnerEye-DeepLearning

We have a field "recovery_start_epoch" in deep_learning_config that can probably be retired

Open

#570 opened on Sep 30, 2021

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Python (519 stars) (138 forks)batch import
good first issuenot urgent

Description

recovery_start_epoch is not settable. We use it to determine the list of training epochs - but even that could be dead code. Verify and clean up

AB#4535

Contributor guide

Tech stack
python
Domain
backend
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.
clear
Prerequisites
Pythonfamiliarity with the repository
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Look in the deep learning config file (likely in InnerEye/ML/configs) for the 'recovery start epoch' field. Search the codebase for all references to this field. If it is unused, remove the field and any associated logic. Ensure no tests rely on it.