CNTK directs console output to stderr about cntk HOT 4 CLOSED

I think only “payload” output (such as rec output) should go to stdout. All other errors, warnings and informational messages should go to stderr.

Andreas

From: Alexey Orlov [mailto:[email protected]]
Sent: Tuesday, January 26, 2016 4:18 AM
To: Microsoft/CNTK [email protected]
Subject: [CNTK] CNTK directs console output to stderr (#25)

Currently CNTK directs all console output to stderr rather than stdout. Was it for a reason?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/25.

from cntk.

Andreas, you said and informational messages. (to stderr). I believe this is exactly what we have now. Moreover, if I invoke, e.g., Simple2d example, nothing goes to stdout. If that's the way we believe it should be, fine. Just wanted to clarify.

from cntk.

Any actual output data should go to stdout, while messages, informational or errors, should be on stderr. I don’t think we have any data output at present. But I can imagine writing to stdout instead of a file e.g. for integrating with pipe-based tools like Kaldi. Since that may be binary data, we should keep stdout pristine.

From: Alexey Orlov [mailto:[email protected]]
Sent: Wednesday, January 27, 2016 12:52
To: Microsoft/CNTK [email protected]
Subject: Re: [CNTK] CNTK directs console output to stderr (#25)

Andreas, you said and informational messages. (to stderr). I believe this is exactly what we have now. Moreover, if I invoke, e.g., Simple2d example, nothing goes to stdout. If that's the way we believe it should be, fine. Just wanted to clarify.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/25#issuecomment-175847549.

from cntk.

To the best of our knowledge CNTK adheres to the UNIX model:

• data to stdout
• messages to stderr

Issue closed

from cntk.