Skip to content

Printing training statistics by default discussion #1367

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sfilipi opened this issue Oct 24, 2018 · 4 comments
Closed

Printing training statistics by default discussion #1367

sfilipi opened this issue Oct 24, 2018 · 4 comments
Labels
API Issues pertaining the friendly API usability Smoothing user interaction or experience

Comments

@sfilipi
Copy link
Member

sfilipi commented Oct 24, 2018

Before the ML.Net Environment changes to Local environment, PR #923 during training of a pipeline, we would see output in the console.

I am trying a long-ish to train model today; takes about 4 minutes, and I find the absence of any progress reporting unsettling. I am not sure whether things are working as expected, or working at all.
I think this will be off-putting for the users.

@sfilipi sfilipi added API Issues pertaining the friendly API usability Smoothing user interaction or experience labels Oct 24, 2018
@justinormont
Copy link
Contributor

I very much like having the intermediate progress output.

Specifically, this gives me:

  • Percent done (or a way to guess)
  • Indication of any progress
  • Knowledge of which component is taking time
  • Warnings/errors insitu

I would like us to go a bit further and have all trainable components output a more useful friendly (ComponentX ##.#% complete). This is only doable for components with known end points and not components which run until convergence. This also gets a bit nasty with threading.

@artidoro
Copy link
Contributor

@Zruty0 since you authored the #923 PR, do you know if the change was intentional?

@Zruty0
Copy link
Contributor

Zruty0 commented Oct 27, 2018

It was an intentional change to NOT write to console willy-nilly.
Right now, ML.NET's MLContext doesn't write to console.

If you do mlContext.Log += Console.WriteLine, we will have the output back in the console, but in a non-colorized format that is more applicable for parsing than for human readability.

I am not sure whether the colorized pretty console printing is something we want to have in the library at all.

@Zruty0
Copy link
Contributor

Zruty0 commented Oct 27, 2018

@TomFinley do you have a comment?

@codemzs codemzs closed this as completed Jun 30, 2019
@ghost ghost locked as resolved and limited conversation to collaborators Mar 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
API Issues pertaining the friendly API usability Smoothing user interaction or experience
Projects
None yet
Development

No branches or pull requests

5 participants