From f6717c87f983420c452404f7a0dc6366eaf3b087 Mon Sep 17 00:00:00 2001
From: Eric Salem <eric.salem@group1.com>
Date: Thu, 25 Apr 2019 13:32:25 -0400
Subject: [PATCH] Issue 632, NelderMeadSimplex Does Not Always Return Best
 Evaluated Point Immediately prior to completion, re-evaluate objective
 function with best vertex to set proper state.

---
 src/Numerics/Optimization/NelderMeadSimplex.cs | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/Numerics/Optimization/NelderMeadSimplex.cs b/src/Numerics/Optimization/NelderMeadSimplex.cs
index 020dc06c..3d201f02 100644
--- a/src/Numerics/Optimization/NelderMeadSimplex.cs
+++ b/src/Numerics/Optimization/NelderMeadSimplex.cs
@@ -173,6 +173,7 @@ namespace MathNet.Numerics.Optimization
                     throw new MaximumIterationsException(String.Format("Maximum iterations ({0}) reached.", maximumIterations));
                 }
             }
+            objectiveFunction.EvaluateAt(vertices[errorProfile.LowestIndex]);
             var regressionResult = new MinimizationResult(objectiveFunction, evaluationCount, exitCondition);
             return regressionResult;
         }