Fix and improvement of Logger #308
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Not everything has been set up correctly in the Logger class. Therefore, the type of output (e.g.
INFO,WARNING) was missing, if the--logfileoption of ls1 was used.To improve the readibility and to distinguish between bools and numbers, the output of booleans was set to be
true/falseinstead of1/0.The present PR is related to the split-up of PR #255.
How Has This Been Tested?
A simulation with the logfile option was run and it was checked that the resulting file includes the type of output (first column).