name output files after config and write output log #5
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.
This is something that annoyed me for a long time, so I finally fixed it:
When running monofonic on two config files:
both of them will write their data into e.g.
input_powerspec.txt
and therefore overwrite the values of the first run making it hard to remember which config file which output belongs to and compare them.Even worse when running
in both cases the
input_powerspec.txt
ends up in the current directory instead of the one where the config is.So I changed it that the config object also stores it's location and basename and therefore we can then name the output files e.g.
config-test-a_input_powerspec.txt
.And in addition I added the output log at
config-test-a_log.txt
like in music.