Skip to content
This repository has been archived by the owner on Mar 21, 2024. It is now read-only.

Refactor report generation code so it is consistent across legacy configs and LightningContainer models. #457

Open
Shruthi42 opened this issue May 12, 2021 · 0 comments
Open

Refactor report generation code so it is consistent across legacy configs and LightningContainer models. #457

Shruthi42 opened this issue May 12, 2021 · 0 comments
Assignees
@peterhessey
Labels
not urgent Not needed for current work

Comments

@Shruthi42
Copy link
Contributor

Shruthi42 commented May 12, 2021 •
edited by azure-boards bot
Loading

For legacy models, there is a method generate_report defined in MLRunner and a flag generate_report in DeepLearningConfig to specify whether to write a report or not. For newer LightningContainer models, there is a function create_report defined as part of the container. How can we make these two codepaths more consistent?

AB#4011
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@peterhessey peterhessey

Labels
not urgent Not needed for current work
Projects
InnerEye-OSS
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Shruthi42 @peterhessey