Downloads

• Vis.jar
• Source Code

In order to use the visualizer for testing your solution locally, you'll have to modify your solution by adding the main method that interacts with the visualizer via reading data from standard input and writing data to standard output. Since you do not change the implementation of method placeLocations, this doesn't affect the way your solution works when being submitted to our server.

To simulate the placeLocations call on server side, your program should read the following data from standard input in this exact order (each integer is located in a separate line):

• Integer N.
• Integer xLen specifying the number of elements in X.
• Integers X[0], X[1], ..., X[xLen - 1], in this order.
• Integer yLen specifying the number of elements in Y.
• Integers Y[0], Y[1], ..., Y[yLen - 1], in this order.

Once this data is read, pass it to your implementation of placeLocations method and let ret be the return value. Write the following data to standard output in this exact order (each integer in a separate line):

• Integer len denoting the number of elements in ret.
• Integers ret[0], ret[1], ..., ret[len-1], in this order.

Make sure to flush the standard output after all this data is written.

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

    N = parseInt(readLine())

    xLen = parseInt(readLine())
    for (i=0; i < xLen; i++)
        X[i] = readLine()

    yLen = parseInt(readLine())
    for (i=0; i < yLen; i++)
        Y[i] = readLine()

    ret = placeLocations(N, X, Y)

    printLine(length(ret))
    for (i=0; i < length(ret); i++)
        printLine(ret[i])

    flush(stdout)

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

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

Here <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 options (all are optional):

• -seed <int> or -s <int>. Set the random generator seed to <int>.
• -x <command>. This is a shortcut for -exec <command>.
• -vis <file> or -v <file>. Write a picture to a file named "<file>.png". In a special case when <file> == "-", create a window and write a picture there.
• -vis_size <int> or -sz <int>. Set the image or window size in pixels (the default value is 1000).
• -points <int> or -n <int>. Once the test case is generated, rewrite the value of N parameter (number of points you return) to <int>.
• -initial <int1> <int2> or -xy <int1> <int2>. Resets the initial point of the NN tour to (<int1>, <int2>).
• -fixed <int> or -f <int>. Sets the number of other fixed points generated to <int>. A value less than 0 is interpreted as 0. A value larger than 10 is interpreted as 10.
• -offset <int1> <int2> or -o <int1> <int2>. Places the top-left corner of a window to (<int1>, <int2>). This is only relevant in "-vis -" mode.
• -tour_label or -tl. Label locations with the order they are visited.
• -return_label or -rl. Label locations with their index in your return array (fixed points are labeled with their index in the X and Y arrays).
• -dot or -d. Place a small black/gray dot at each of your points (red dots on fixed points are always present).
• -score. Display your raw score for this test case at the bottom of the image.

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 offline testers, 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.