Move all logging in core library and tools to use MDLogger - Redmine #2999
Currently, logging is still not done in a consistent way in the core
GROMACS library.
While large parts of the code in the actual mdrunner have been moved to
use it, other parts are still printing directly to stderr or stdout.
This is an umbrella task that should be used to organize subtasks that are focusing on individual parts of the code.
(from redmine: issue id 2999, created on 2019-06-25 by acmnpv)
- Relations:
- relates #1505
- child #3004 (closed)
- child #3005 (closed)
- child #3013 (closed)
- child #3015 (closed)
- child #3035 (closed)
- child #3036 (closed)
- Changesets:
- Revision da430b43 by Paul Bauer on 2019-07-18T09:54:05Z:
Extend MDLogger levels
Added logging levels for errors and debug information.
Extended tests to check those.
Refs #2999
Change-Id: I8b23de7baf3555ffc89896e68c1998608b7b71cf
- Revision 37563a1d by Paul Bauer on 2020-01-31T15:07:38Z:
Start using MDLogger in gmxpreprocess
Changed logging of one set of routines to use the logger interface
instead of calling fprintf to stderr.
Refs #2005, #2999
Change-Id: Ibbecab0af6a0fa1c62c754f8826b8ff84fa4886e
- Revision 99b15a53 by Paul Bauer on 2020-01-31T20:11:53Z:
Use MDLogger in grompp
Start using MDLogger in main grompp routine.
Refs #2999, #3005
Change-Id: Ic88e9a2ec271a4bf9502da5a268f532d422a1f1b
- Revision 1a3955c6 by Paul Bauer on 2020-02-05T07:17:26Z:
Use more MDLogger in preprocessing
Refs #2999, #3005
Change-Id: I2ec9f5d9d98d7b1add0cc3e9339e7a93b6e1c9a6