Welcome to the second Junior SAC Code Challenge of the school year!
The difficulty will range from CCC Junior 1 to CCC Junior 5.
The contest organizer is.
The problem setter is.
Special thanks to, , , , , , , and for testing and helping with the problems!
The contest will run from March 11th, 00:00 EST, until March 14th, 00:00 EDT. You will have a two-hour window to solve the problems.
Here are the parameters of the contest:
- Contest duration: 2 hours.
- Number of problems: 5, full feedback (you will see the results of each submission instantly). Each problem will be worth 100 points and have partials marks in the form of subtasks.
- Scoreboard will be visible.
- No incorrect submission penalty.
- There will be no submission limit.
- Ties in score will be broken by the last submission time that increased your score.
- This contest is unrated.
Before the contest date, you may wish to check out the tips and help pages.
We have listed below some advice as well as contest strategies:
- Problems will be approximately increasing in difficulty. Reading all of the statements is still recommended.
- Remove all extra debugging code and/or input prompts from your code before submitting. The judge is very strict — most of the time, it requires your output to match exactly.
- Do not pause program execution at the end. The judging process is automated. You should use stdin / stdout to perform input / output, respectively.
- It is guaranteed that all problems and subtasks will be solvable in C++ and Java; Python users are recommended to use PyPy.
|SAC '22 Code Challenge 4 Junior P1 - Obligatory DeMello Problem||3||63.3%||154||Editorial|
|SAC '22 Code Challenge 4 Junior P2 - Obligatory Geometry Problem||3p||55.3%||137||Editorial|
|SAC '22 Code Challenge 4 Junior P3 - Obligatory Triangle Problem||5p||25.8%||112||Editorial|
|SAC '22 Code Challenge 4 Junior P4 - Obligatory Permutation Problem||7p||19.2%||65||Editorial|
|SAC '22 Code Challenge 4 Junior P5 - Obligatory Output Only Problem||10||20.9%||27||Editorial|