Error messages given through different streams

[Jintram]

eGFRD error messages are not given via the same stream.

This results for example in difficulties with piping the messages to a file. (Because of - I guess - buffer issues the order gets messed up.) Especially when messages originate directly from C++, it's hard to synchronize them with Python error messages.

In C++ different stdout commands are used.

Perhaps we should decide on a single error message "channel".

MW

[Jintram]

Tomek says:

Looks as if that was a problem with flushing the streams.

C++ does not output the streams immediately but rather waits until "enough" output has accumulated and then picks a suitable output time.
By adding cerr.flush() you can force C++ to output the error stream directly. However, we do not want to hack GSL...

But maybe it already helps to add some of these commands in our code in the relevant places (rootfinder?) to force some reliable error output. You might give it a try, but I agree that you should not focus too much on that now.