Skip to content
Snippets Groups Projects
  1. Mar 03, 2012
    • Sam Moore's avatar
      Tweaking manager/simulate.py, updating manual and webpage · 476617a8
      Sam Moore authored
      You can now pass arguments to your AI through the manager program.
      Simply include the path to the AI and arguments in quotation marks.
      
      EG:
      ./stratego "../../agents/foo/bar --debug" ../../agents/other/agent
      
      simulate.py was making broken links to log files, fixed.
      
      Logging of stderr! If anything is printed to stderr, it is all saved in logfilename.stderr by simulate.py
      
      Tried to make the manual page better, probably failed.
      
      Updated webpage since we have now changed the date.
      
      Also tried to fix vixen again, haven't tested.
      476617a8
  2. Mar 02, 2012
    • Sam Moore's avatar
      Fixed bug in simulate.py + hacky fix for bug in vixen · 9e4bc3c0
      Sam Moore authored
      simulate.py wasn't setting the "gameID" variable correctly,
      meaning all games were logged to "red.vs.blue.1.1"
      
      Bug in vixen found by [SLX]; it attempts to move outside the board.
      Usually when losing.
      
      Path finding algorithm (path.py) shouldn't move outside the board.
      But somehow it is.
      
      Hacky fix at the moment by checking for moves outside the board in
      vixen's score calculation, and allocating -100 to these moves.
      9e4bc3c0
  3. Feb 02, 2012
    • Sam Moore's avatar
      Did some stuff · 6066930d
      Sam Moore authored
      Probably should have committed immediately after I did whatever the stuff was? Not several weeks later?
      
      I appear to have improved the vixen AI slightly
      
      Aha, I remember! Altered manager program so that two ports are used (4560 and 4561) instead of just one.
      This means you can use network controllers for both players, not just one.
      6066930d
  4. Jan 19, 2012
  5. Dec 24, 2011
    • Sam Moore's avatar
      Bug in simulate.py caused by "INTERNAL_ERROR" · fda21e69
      Sam Moore authored
      When INTERNAL_ERRORs occur, the colour wasn't added to the array in the "ALL" results.
      So when the script looks up agents["ALL"][index][4] (the colour entry), there was an indexing error.
      Fixed by adding the colour to the result array when INTERNAL_ERROR occurs.
      
      TODO: Discover cause of INTERNAL_ERROR - in the manager program
      
      It occurs on mufasa, but not on my laptop.
      I believe it is due to AI timeouts not being handled correctly by the manager program (stratego).
      On my laptop, things run nice and fast, and since all the AI work properly, there are no timeouts.
      On mufasa, things run shit and slow, and pretty much every game I tested ended with a move timeout.
      Timeout causes broken pipe after AI program is told to exit?
      
      As a temporary measure, increased timeout to 60s (from 2s). If this doesn't stop timeouts,
      there must be some other factor making things slow.
      "The problem is determining where the shittiness lies... is it the shittiness of the VM, the shittiness of python,
      the shittiness of the manager program..."
      
      Running another test round on mufasa over christmas. Hopefully it will finish running by new year. (Assume 60s a move, 300 moves a game... 12 games...)
      
      Considering putting my laptop in the clubroom and just running the competition on that.
      fda21e69
  6. Dec 22, 2011