Downloads

Helpful information

In order to use the offline tester / visualizer tool for testing your solution locally, you'll have to adopt your solution to read the parameters from standard in and write the output to standard out. This doesn't affect the functioning of the solution you submit to our server.

To do this, you should implement the following pseudocode:

    main()
    {
        N = int(readLine())
        for (i=0; i<N; i++)
            expr_avg[i] = readLine()
        for (i=0; i<N; i++)
            expr_diff[i] = readLine()
        for (i=0; i<N; i++)
            mutation[i] = readLine()
        for (i=0; i<N; i++)
            obs_time[i] = readLine()
        ret = trainingData(0, expr_avg, expr_diff, mutation, obs_time)
        printLine(ret)
        flush(stdout)

        N = int(readLine())
        for (i=0; i<N; i++)
            expr_avg[i] = readLine()
        for (i=0; i<N; i++)
            expr_diff[i] = readLine()
        for (i=0; i<N; i++)
            mutation[i] = readLine()
        ret = testingData(expr_avg, expr_diff, mutation)
        printLine(ret.size())
        for (i=0; i < ret.size(); i++)
            printLine(ret[i])
        flush(stdout)
    }

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

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.