Automatically write linkstats to output folder #3140
Closed
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.
It would improve my workflow if the
linkstats
were already contained in the output folder along all other relevant outputs such asoutput_events.xml.gz
. As it is now the linkstats are only located in the respective iteration folders.The small proposed change would also write an
output_linkstats.txt.gz
to the output folder if (and only if) the last iteration produced alinkstats.txt.gz
in the repsective iteration folder.Small sidenote: It guess it would make sense to also change the linkstats output to
.csv
as all other outputs.