Mock CCC '19 Contest 1 Junior

Hello, welcome to a mock CCC! Here are the parameters of the contest:

  • Contest duration: 3 hours.
  • Number of problems: 5, full feedback, with subtasks. The problems follow the CCC format of being worth 15 marks each. All problems have explicit subtasks.
  • Not rated.
  • Scoreboard will be hidden.
  • Number of submissions allowed per problem: 50.
  • Checkers for problems: Unless otherwise specified, identical. The contest will follow the standard convention of having all lines terminate in a \n character.
  • Testers for this contest: aeternalis1, Cthulhu, j2267wan, ksun48, quantum, ss__jonathan, wleung_bvg.

Clarification requests for the contest must be routed through the clarification system provided on DMOJ, and not through other channels including but not limited to Slack. Furthermore, all clarification requests will be handled the way they normally are in IOI. Note that, in particular, clarification requests must come in the form of yes/no questions.

Before the contest date, you may wish to check out the tips and help pages.

The contest consists of 5 questions with a range of difficulty from CCC Junior 1 to CCC Junior 5. It is highly recommended to read all of the problems. You will have 3 hours to complete the contest. After the contest window begins, you may begin at any time. Your personal timer will start counting down, and you will be able to submit until 3 hours from when you started, or until the hard deadline, whichever comes first.

After joining the contest, you proceed to the Problems tab to begin. You can also go to Users if you wish to see the rankings.

We have listed below some advice as well as contest strategies:

  • Start from the beginning. Ties will be broken by the sum of times used to solve the problems starting from the beginning of the contest. The last submission time of your highest score will be used.
  • Remove all extra debugging code and/or input prompts from your code before submitting. The judge is strict — your output must match the judge output 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 the problems will be solvable with C, C++, Java, and Python.

At the end of the contest, you may comment below to appeal a judging verdict. In the case of appeals, the decision(s) of our staff is final.

Problems

Problem Points AC Rate Users Editorials
Mock CCC '19 Contest 1 J1 - Pusheen's Report Card 3p 36.2% 1004 Editorial
Mock CCC '19 Contest 1 J2 - Pusheen OCR 3p 55.0% 748 Editorial
Mock CCC '19 Contest 1 J3 - Pusheen Eats Tuna Sashimi and Tuna Nigiri 3p 19.4% 385 Editorial
Mock CCC '19 Contest 1 J4 - Pusheen Plays Neko Atsume 3p 19.5% 320 Editorial
Mock CCC '19 Contest 1 J5 - Pusheen Designs a Sushi Boat 7p 17.0% 235 Editorial

Comments


  • -10
    JustinXu  commented on Jan. 19, 2019, 2:20 p.m. ← edited

    This comment is hidden due to too much negative feedback. Show it anyway.


    • 2
      avid  commented on Jan. 19, 2019, 2:30 p.m.

      lol.


  • 6
    randomperson89  commented on Jan. 19, 2019, 3:27 a.m.

    Anyone else having issues with judging? I keep getting stuck on "Your submission is being processed..." or "We are waiting for a suitable judge to process your submission..."


    • 0
      1369738647  commented on Feb. 5, 2019, 3:19 a.m.

      You refresh the page


  • -18
    Dordor1218  commented on Jan. 18, 2019, 3:17 p.m. ← edit 2

    This comment is hidden due to too much negative feedback. Show it anyway.


    • 2
      Kirito  commented on Jan. 18, 2019, 3:37 p.m.

      Judges are fine, what you are seeing is likely a side effect of the number of test cases.


      • -19
        Dordor1218  commented on Jan. 18, 2019, 4:44 p.m.

        This comment is hidden due to too much negative feedback. Show it anyway.


        • 20
          xiaowuc1  commented on Jan. 18, 2019, 4:59 p.m.

          I've manually looked at all of your WA solutions and all of them are incorrect.

          If you have any disputes about the correctness of the test data, please file a ticket instead of posting about this publicly.