DMOPC '15 February Contest

Welcome to the fifth Don Mills Open Programming Competition of the 2015-2016 season!

The problem writers this time are fifiman, k_53P, cheesecake, Xyene, and FatalEagle.

If this is your first time participating in the DMOPC this season, you can learn about our new system here.

This round will be rated for all participants.

The theme for this month's contest will be Steins;Gate.

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

The contest consists of 6 questions with a wide range of difficulties, and you can get partial marks for partial solutions in the form of subtasks. If you cannot solve a problem fully, we encourage you to go for these partial marks. The difficulty of a problem may be anywhere from CCC Junior to CCO level. 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 (9PM EST), 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 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 the problems will be solvable with C++.

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

After the contest finishes, we'll have a optional feedback form we would like you to fill out.

Good luck!

Problems

Problem Points AC Rate Users Editorials
DMOPC '15 Contest 5 P1 - Gel Bananas 3p 14.8% 233 Editorial
DMOPC '15 Contest 5 P2 - D-Mails 5p 47.2% 115 Editorial
DMOPC '15 Contest 5 P3 - All Your Base 7p 32.4% 117 Editorial
DMOPC '15 Contest 5 P4 - Steins;Number 12p 21.2% 77 Editorial
DMOPC '15 Contest 5 P5 - World Line Convergence 15p 24.1% 108 Editorial
DMOPC '15 Contest 5 P6 - Event Horizon 25p 11.1% 20 Editorial

Comments


  • -1
    fafalnq  commented on Feb. 10, 2016, 2:17 p.m. ← edited

    I got 50 on the first problem, and I got the same score with 'resubmit'. However I clicked 'Submit solution' with the exact same code I wrote and I got 100. Weird.


    • 1
      FatalEagle  commented on Feb. 10, 2016, 9:37 p.m.

      long is 32 bits on a 32-bit judge and 64 bits on a 64-bit judge. Please use either int or long long for consistent behavior.


      • -1
        fafalnq  commented on Feb. 11, 2016, 2:08 a.m.

        thx alot


  • 1
    grikukan  commented on Feb. 9, 2016, 5:04 p.m.

    It writes "you are already in contest" but I can't do anything


  • 0
    fsdom  commented on Jan. 31, 2016, 4:04 a.m.

    "if your submission ACs on only the pretest for subtask 1, you will receive a temporary score of 2"- what does it mean? Temporary score! I mean no partial point for pretests?


    • 2
      cheesecake  commented on Jan. 31, 2016, 4:32 a.m.

      Your temporary score is your expected score on the system tests, scaled down by a factor of 10. For example, if you receive a temporary score of 2. You are expected to get 20% on the systest.