Need help with library-checker-problems?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

yosupo06
170 Stars 39 Forks Apache License 2.0 1.5K Commits 72 Opened issues

Description

The problem data (Test case generator, judge's solution, task, ...) of Library Checker

Services available

!
?

Need anything else?

Contributors list

# 188,899
Shell
C++
HTML
atcoder
637 commits
# 157,452
jQuery
React
D
Nim
52 commits
# 592,667
TeX
C
Shell
Online ...
40 commits
# 489,931
atcoder
C++
HTML
Shell
35 commits
# 519,482
Shell
C++
HTML
atcoder
28 commits
# 477,699
C
Objecti...
sd-card
Shell
27 commits
# 246,937
automat...
Shell
TeX
Nim
3 commits
# 216,077
TeX
Vim
repl
Lua
2 commits
# 414,953
slack
React
react-r...
OCaml
1 commit
# 469,238
HTML
Sass
Shell
Online ...
1 commit
# 461,589
atcoder
C++
HTML
Shell
1 commit

Library Checker Problems

CI License

Source code of https://judge.yosupo.jp. You can get test cases of problems from this repository.

Requirements

  • Linux / OS X / Windows(MinGW-w64)
  • python3.5+
  • g++ / clang++ (Needs --std=c++14 and _int128t)

How to Use

cd /path/to/library-checker-problems

pip3 install -r requirements.txt

or pip3 install toml colorlog markdown jinja2

ulimit -s unlimited # for linux (doesn't need for OS X and WSL)

./generate.py -p unionfind # generate testcases of unionfind

or ./generate.py datastructure/unionfind/info.toml

ls datastructure/unionfind/in/ # testcases of unionfind ls datastructure/unionfind/out/ # solutions of unionfind file datastructure/unionfind/checker # binary of output checker

For developer

./generate.py -p unionfind --dev # developer mode
./generate.py -p unionfind --test # test mode (for developer, exec this command before PR)
cat datastructure/unionfind/unionfind.html # statement

./generate.py $(find . -name "info.toml" -not -path "./test/*") # generate all testcases

Test your solutions in local / CI

If you have any trouble

  • Create issue: we are very happy if you report any of our mistakes (e.g. test cases are weak, strange behavior of the site, English of statements is bad, ...). Anything others are also welcome.
  • Codeforces: https://codeforces.com/blog/entry/76945
  • Twitter: if you tweet your trouble with hashtag #LibraryChecker, we are going to help you. The account of admin is @yosupot.

困ったときは(If you have any trouble - Japanese edition)

  • issueを立てる: githubにはissueというTODOやバグなどをメモっておく機能があります。上の Issues → New issueから作成できます。
  • Twitter で #LibraryChecker というハッシュタグをつけて呟いてくれると、助けに行きます。@yosupot へリプライ / DM でも大丈夫です。

Contributing

We are welcome any issues and PRs! Except minor change (e.g. add test cases, fix statements), please create an issue first.

Contributing - Japanese Edition

不具合(テストケースが弱い, ジャッジが異常な挙動をする, 問題文にtypoを発見, などなど)を発見したとき、報告していただけるととっても助かります。

基本的には上に書いたようにissueを立ててもらえると助かります。 熱意がある人はCONTRIBUTING を参考にPull requestを送っていただけるととても助かります。

競プロerは必ずしもgithubに慣れているとは限らず、issue / pull request を送ったことがない人も少なくはないというのを理解しています。どれだけめちゃくちゃなものを送ってきても怒ったりこのリポジトリが壊れたりすることはないので、githubの練習がてら挑戦してみるというのもアリです(頑張ってサポートします)。

File structure / How to create the problem

guideline(en)

guideline(日本語)

library-checker-project

Thanks

We use testlib for verifier(input-checker) and output-checker.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.