Temporary Encog Normalization Extensions Library #97
Conversation
This file contains hidden or 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
…ested with my own application.
…r duration of network running. This also works with the latest NEAT network changes I have been making.
… with datasets. This is still work in progress and there are some improvements that can still be made (such as the ability to work with multiple data tables, speed enhancements and the implementation of time series data). The code will also need to be baked directly into the encog framework and the existing csv logic will need to be re-worked to use this new logic as a base.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Encog Extensions Library
Personally I found myself in a situation where I needed to use normalization with randomized
in memory data. The data could not be saved to a CSV as this would conflict with another frameworks
persistence mechanism.
The encog analyst is fantastic for normalizing data. It can take information stored in a CSV file
and automatically determine the normalized fields and their type of encoding
(including 1 of N equilateral encoding).
The only downside of this is that the logic is tightly coupled with the ReadCSV class.
Favouring extension as opposed to modification I decided to go about creating extension methods and
alternative classes to create an analyst that would normalize a generic .NET dataset.
At the moment this logic is a partial re-write of the existing encog analyst. For this reason
much of the code is duplicated (which I appreciate is a bad thing). My intention is to eventually
bake the logic directly into encog-core-cs by modifying the existing implementation. For now the code is there to be used when needed.