Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 3e9882e

Browse files
authored
Update README.md
1 parent e3704be commit 3e9882e

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

‎README.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -113,13 +113,15 @@ DA.solve(plot=True)
113113

114114
***RESULTS***
115115

116-
From the console we can deduce the optimal result (see Fig. 4) . The global optimal has a fitness of 25, while duelist algorithm found 25.01. So Duelist Algorithm performs well.
116+
From the console we can deduce the optimal result (see Fig. 4) . The global optimal has a fitness of 25, while duelist algorithm found 25.01. Error of 0.01 can be reduced by putting more maximum generations in solver.
117+
117118
![result1](images/results.PNG)
118119
*Fig 4. Optimal Results in Console*
119120

120121
We can see that the algorithm quickly converges to the optimal point (see Fig. 5) as reported by the original article.
121-
![result2](images/results2.png)
122122

123+
![result2](images/results2.png)
124+
*Fig 5. Quick convergence of Duelist Algorithm*
123125

124126
For more examples refer to the python scripts in "examples" folder. [https://github.com/tsyet12/Duelist-Algorithm-Python/tree/master/examples]
125127

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /