Compare weights - to see what is (un)learned #6
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 adds some code to compare two weightfiles in detail.
When running a testsuite over two nets as defined in nets.txt, the standard output will contain the positions where the result was different for.
Example output for two nets:
I just tested on 200 nodes instead of 0 nodes as well, although the number of found moves is higher (of course) the difference between nets has also increased: