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 methods init and makeMoves, 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 approach: send the next available ship to the next unvisited star as long as there are unvisited stars.
You may modify and submit these example solutions.
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:
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.
-vis : Turn on visualization. Ufo paths are shown in yellow. Your ships' paths are shown in gray. Paths on which your ships travelled with ufo's are shown in green. Press Space to pause/resume simulation (simulation starts paused).
-save output.png : Write visualization results to file output.png.
-delay 50 : Set the delay between moves to 50 ms.
-noufo : Ufo's will not be drawn during visualization.