1. 07 May, 2004 3 commits
  2. 06 May, 2004 1 commit
  3. 05 May, 2004 5 commits
  4. 04 May, 2004 4 commits
  5. 03 May, 2004 5 commits
  6. 30 Apr, 2004 2 commits
  7. 29 Apr, 2004 10 commits
  8. 28 Apr, 2004 8 commits
  9. 27 Apr, 2004 2 commits
    • Jay Lepreau's avatar
    • Robert Ricci's avatar
      Change the termination conditions in subtle, but important, way. When using · c91cc414
      Robert Ricci authored
      epsilon termination (and ALLOW_NEGATIVE_EPSILON), it used to be the case that
      we wrapped the termination condition in a fabs(), and compared that to epsilon.
      The termination condition is basically a measure of how 'stable' of a score
      we're at. What this meant was that we used to keep going until we reached a
      space where the solution was going neither up nor down too much. All this is
      relative to the difference between initial socre and the best score - so, if
      those are close (ie. it's an easy problem), we could end up thrashing a whole
      lot. With the new behavior, if we ever hit a spot in which solutions start
      getting worse, we'll stop.
      Also, fix the GNUPLOT_OUTPUT code, which I used to debut this.