From ba5204bcc1d961d5da10c99b46d2e669bf930be5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stefan=20Schr=C3=B6der?= Date: Thu, 12 Mar 2015 15:26:39 +0100 Subject: [PATCH] Update WHATS_NEW.md --- WHATS_NEW.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/WHATS_NEW.md b/WHATS_NEW.md index 6b59c6d0..df9921ba 100644 --- a/WHATS_NEW.md +++ b/WHATS_NEW.md @@ -6,7 +6,7 @@ WHATS NEW When reviewing the feedback from our users, we realized that jsprit cannot solve certain kinds of problems adequately. To illustrate and characterize them, look at the following examples. -jsprit, which was basically specific configurations of the schrimpf-algorithm was/is good and fast at solving this: +jsprit was/is good and fast at solving this: ![schrimpf_simpleCluster](https://github.com/jsprit/misc-rep/raw/master/wiki-images/vrp_clustered_schrimpf_simpleCluster.png) @@ -17,7 +17,7 @@ between depot and the existing clusters. Obviously, the way we ruined and recreated wasn't sufficient to solve the problem reasonably. To make it even more obvious, we added a job cloud surrounding - the depot. The schrimpf-algorithm (as we configured it) yields the following solution. + the depot yielding the following solution. ![schrimpf_moreClusters_depotNoise](https://github.com/jsprit/misc-rep/raw/master/wiki-images/vrp_clustered_schrimpf_moreClusters_depotNoise.png)