Downloads

• Executable JAR of the visualizer
• Source code of the visualizer
• Training data
• Top 2 solutions from round 1

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 your methods, this doesn't affect the way your solution works when being submitted to our server.

To simulate a single test case, your program should implement the following protocol (each integer is to be read from / printed in a separate line):

• Read integer N.
• Read N strings plyData[0], plyData[1], ... , plyData[N-1].
• Call trainingModel(plyData). Let ret be the return value.
• Print the integer in ret. Flush standard output stream.
• if ret==1 goto StartTesting.
• Read integer NumPairs.
• Receive NumPairs training pairs by performing the following NumPairs times:
•          Read 1600*1200 integers leftImage[0], leftImage[1], ... , leftImage[1600*1200-1].
•          Read 1600*1200 integers rightImage[0], rightImage[1], ... , rightImage[1600*1200-1].
•          Read integer G.
•          Read G doubles groundTruth[0], groundTruth[1], ... , groundTruth[G-1].
•          Call trainingPair(leftImage, rightImage, groundTruth). Let ret be the return value.
•          Print the integer in ret. Flush standard output stream.
•          Break out of the training loop if ret==1
• StartTesting:
• Call doneTraining().
• Read integer NumPairs.
• Receive NumPairs testing pairs by performing the following NumPairs times:
•          Read 1600*1200 integers leftImage[0], leftImage[1], ... , leftImage[1600*1200-1].
•          Read 1600*1200 integers rightImage[0], rightImage[1], ... , rightImage[1600*1200-1].
•          Call testingPair(leftImage, rightImage). Let ret[] be the return value.
•          Print the integers in ret[] each on a separate lines. Flush standard output stream.

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

    
N = parseInt(readLine())
for (i=0; i < N; j++)
    plyData[i] = readLine()
ret = trainingModel(plyData)
printLine(ret)
flush(stdout)
if (ret==1) goto StartTesting
      
NumPairs = parseInt(readLine())
for (f = 0; f < NumPairs; f++)
{
    for (j=0; j < 1600*1200; j++)
        leftImage[j] = parseInt(readLine())
    for (j=0; j < 1600*1200; j++)
        rightImage[j] = parseInt(readLine())
    G = parseInt(readLine())
    for (j=0; j < G; j++)
        groundTruth[j] = parseDouble(readLine())
    ret = trainingPair(leftImage, rightImage, groundTruth)
    printLine(ret)
    flush(stdout)
    if (ret==1) goto break
}
StartTesting:
doneTraining()
NumPairs = parseInt(readLine())
for (f = 0; f < NumPairs; f++)
{
    for (j=0; j < 1600*1200; j++)
        leftImage[j] = parseInt(readLine())
    for (j=0; j < 1600*1200; j++)
        rightImage[j] = parseInt(readLine())
    ret[] = testingPair(leftImage, rightImage)
    for (j=0; j < 7; j++)
        printLine(ret[j])
    flush(stdout)
}

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

java -jar tester.jar -exec "<command>" -train example_data/training.csv -test example_data/testing.csv -folder example_data/

<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".

The *.ply files should be in the same folder as the tester.jar file.

Additionally you can use the following parameters:

• -seed <seed>. Sets the seed used for test case generation. Default value is 1.
• -train <training file>. Sets the file that contains a list of the training pairs.
• -test <testing file>. Sets the file that contains a list of the testing pairs.
• -folder <image folder>. Sets the base folder where the images are located.
• -novis. Turns visualization off.
• -silent. Turns debug output off.
• -faces. Renders the faces of the 3d model.

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.