Use AuthenticatePrediction instead of AuthenticateTraining

[gottagetgit]

Purpose

• The main method calls the wrong function to authenticate itself even though it works the way it is. The other method is not called any other time and therefore is orphan code if not used. This PR is to reunite an orphan with it's parent.

Does this introduce a breaking change?

[ ] Yes
[X] No

Pull Request Type

What kind of change does this Pull Request introduce?

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

• Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

• Test the code

What to Check

Verify that the following are valid

• ...

Other Information

There should be no difference to the output of this program. It's simply that two methods were created by the original author to AuthenticateTraining, and AuthenticatePrediction. But AuthenticatePrediction is never called. AuthenticateTraining is called twice.

Technically, we can remove one of the methods and rename the other. But perhaps there was an intention by the author to separate the two for some training purpose.

[gottagetgit]

Relates to issue #257

[fsharpn00b]

Hello @gottagetgit,

Thank you very much for this fix. The double call to AuthenticateTraining looks like a copy/paste error.