Downloads

• Executable JAR of the visualizer
• Source code of the visualizer

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. Since you do not change the implementation of method findLoop, this doesn't affect the way your solution works when being submitted to our server.

To simulate a single test case, your program should read the following data from standard input in this exact order (each integer/string is located in a separate line):

• Integer SZ.
• Strings diagram[0], diagram[1], ..., diagram[SZ - 1], in this order.

Once this data is read, pass it to your implementation of findLoop method and let ret be the return value. After that, write ret to the standard output and flush the standard output.

In other words, you should implement the following pseudocode in the main method of your solution:

    SZ = parseInt(readLine())

    for (i=0; i < SZ; i++)
        diagram[i] = readLine()

    ret = findLoop(diagram)

    printLine(ret)

    flush(stdout)

In order to run the tester / visualizer, you should use the following command:

java -jar Vis.jar -exec "<command>"

<command> is the command you would use to execute your solution. If your compiled solution is an executable file, the command will just 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 parameters (all are optional):

• -seed <seed>. Sets the seed used for test case generation. Default value is 1.
• -novis. Switches the visualization off, leaving only text output.
• -side. Sets the size of one cell of the board, in pixels. The default value is 10. This parameter also affects whether black dots representing lattice points and numbers within cells are drawn. It happens only when side ≥ 10.

The visualizer colors cells as follows: white means no clue, red is an unsatisfied clue and blue is a satisfied clue.

You can print any debug information of your solution to the standard error stream and it will be forwarded to the standard output of the tester.

For more information on using visualizers, please check the following recipe draft from TopCoder Cookbook. Note that this is not a troubleshooting thread, please use the match forum for questions instead.