Competitive programming scripts

• Contests parsing
• Problems parsing
• Compilation and problems testing
• Stress testing
• Testing interactive problems
• Installation or settings update

Contests parsing

There are two options for parsing the contest:

• Install the html of the contest yourself and parse the installed file (preferred way, if the contest is live):

setup_contest -html ~/Downloads/contest.html -title cf1637

• Specify the link (for codeforces the link should point to /problems page, for atcoder - to tasks_print page):

setup_contest -url https://codeforces.com/contest/1637/problems
setup_contest -url https://atcoder.jp/contests/agc010/tasks_print

Problems parsing

As well as for contests parsing there are two options:

• Install the html of the problem yourself and parse the installed file:

setup_problem -html ~/Downloads/problem.html -index H

• Specify the link:

setup_problem -url https://codeforces.com/contest/1637/problem/H
setup_problem -url https://atcoder.jp/contests/agc010/tasks/agc010_f

Compilation and problems testing

There are scripts to compile or test in debug mode: cmpl and bld as well as to compile ans test in release mode: fcmpl and fbld. Also, drun is used to test the solution without compilation.

Compilation and testing main.cpp:

cmpl main
bld main
fcmpl main
fbld main
drun main

Stress testing

To stress test your solution you need to implement a generator and correct solution. All of them must be executable (i.e. already compiled). For example:

stress_test -sol main -gen gen.py -brute brute

Testing interactive problems

To test an interactive problem you need to implement an interactor. For example:

interact -sol main -int interactor -input in1

Installation or settings update

Before installation set your own settings inside settings.js.

Inside debug section there are settings used for bld and cmpl. Inside release section there are similar settings used for fbld and fcmpl.

Also, it is possible to set which files and directories should be created when executing setup_problem or setup_contest. problem_files are created inside each problem directory, and contest_files are created inside the contest directory.

chmod +x install.sh
./install.sh

In case PATH warning is thrown, you need to add /Users/<username>/Library/Python/<version>/bin (the correct path must be mentioned in the warning) to the PATH:

PATH="/Users/<username>/Library/Python/<version>/bin":"$PATH"

You can uninstall it with pip3:

pip3 uninstall competitive_programming_scripts