In order to use the offline tester / visualizer tool for testing your solution locally, you'll have to modify your solution
by adding the main method that interacts with the tester / visualizer via reading data from standard input and
writing data to standard output. As long as you do not change the implementation of the methods init and sendTroops, this
doesn't affect the way your solution works when submitted to our server.
Here are example solutions for different languages, modified to be executed with visualizer. They all implement the same strategy, which is close to the strategy used by AIs.
To run the tester with your solution, you should run:
java -jar Tester.jar -exec "<command>" -seed <seed>
Here, <command> is the command to execute your program,
and <seed> is seed for test case generation.
If your compiled solution is an executable file, the command
will be the full path to it, for example, "C:\TopCoder\solution.exe" or
"~/topcoder/solution". In case your compiled solution is to be run
with the help of an interpreter, for example, if you program in Java,
the command will be something like "java -cp C:\TopCoder Solution".
Additionally you can use the following options:
Visualizer works in two modes. In regular mode, steps are visualized one after another with a delay specified with -delay parameter. In paused mode, the next turn will be visualized only when you press any key (except space). The space key can be used to switch between regular and paused modes. The default starting mode is regular. You can use -pause parameter to start in paused mode.
-novis : Turns off visualization.
-delay <delay> : Sets the delay (in milliseconds) between visualizing consecutive simulation steps. The default value is 100.
-pause : Starts visualizer in paused mode.
Finally, you can print any debug information of your solution to standard error,
and it will be forwarded to the standard out of the tester.