SAC '22 Code Challenge 3
Welcome to the third SAC Code Challenge of the school year!
The difficulty will range from CCC Junior 1 to CCC Senior 4.
The contest organizer is
.The problem setter is
.Special thanks to
, , , , , , , , , , , and for testing and helping with the problems!The contest will run from February 11th, 00:00 EST, until February 14th, 00:00 EST. 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 partial 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.
Problems
Problem | Points | AC Rate | Users | Editorials |
---|---|---|---|---|
SAC '22 Code Challenge 3 P1 - Hair Hazards | 3 | 74.4% | 582 | Editorial |
SAC '22 Code Challenge 3 P2 - Unicycle License | 5 | 41.2% | 273 | Editorial |
SAC '22 Code Challenge 3 P3 - Bob Sort | 5p | 25.9% | 165 | Editorial |
SAC '22 Code Challenge 3 P4 - Finding Friends | 15p | 22.0% | 69 | Editorial |
SAC '22 Code Challenge 3 P5 - Chat Corrections | 12p | 16.0% | 43 | Editorial |
Comments