GlobeX Cup '19 Senior

GlobeX Cup '19 will have a junior and senior division, featuring problems with difficulties from elementary to advanced. To determine which division suits you the best, we recommend looking at the problem statements from last year's contest. This is the senior division of the contest.

Registration

Please fill out this form in order to register for the contest and be eligible for prizes.

Senior Prizes

1st Place: $70 Cash Prize
2nd Place: Wolfram|One + Wolfram|Alpha Pro
3rd Place: Free Admission to ToHacks & CuHacking

Contact

For any inquiries, please email globexcup@gmail.com or message our Instagram page GlobeXCup.


Here are the parameters of the contest:

  • Contest duration: 3 hours.
  • Number of problems: 5. Each problem will be worth 100 points, with subtasks. The pretest/systest format will be used for problems 3-5. For more information about the pretest/systest format, see this page.
  • Rated for all participants who submit at least once.
  • Scoreboard will be visible.
  • No submission limit.
  • Ties will be broken by the sum of times used to solve the problems starting from the beginning of the contest. The first submission time of your highest score will be used.
  • Checkers for problems: standard unless otherwise specified.

Due to rampant issues with cheating on contests that has happened recently, any suspicious behavior during the contest window may result in your rating being impacted negatively. Such behavior includes, but is not limited to:

  • Registering for the contest with at least two accounts.
  • Participating in the contest with an account that is not your primary account.
  • During the contest window, talking about the contest in more detail than answering a yes/no question about whether one participated in the contest. This includes, but is not limited to, posting spoilers about the contest and public speculation of the contest.
  • Attempting to exploit bugs in the platform to subvert the constraints of the contest.
  • Deliberately obfuscating code.

Punishments may include performance being unrated or, for more serious infractions, being forcibly ranked at the bottom of the scoreboard.

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 and Discord.

The problem writers for this contest are alextxu, Ninjaclasher, and AQT. Special thanks to ChrisT for testing.


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

This contest will consist of 5 problems, the difficulty of which may range from anywhere CCC Senior to CCO level. Some problems offer partial marks in the form of subtasks. If you cannot solve a problem fully, we encourage you to go for these partial marks.

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 first 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++.
  • Read carefully, and try to attempt all the problems. They may not be as hard as they seem and you may get partial points!

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



Comments


  • 7
    hxxr  commented on Dec. 15, 2019, 3:42 a.m.

    :thonk:

    enter image description here


  • 13
    Riolku  commented on Dec. 14, 2019, 3:19 p.m.

    Is globex ever going to be rated, public'd and given editorials?


    • -6
      shuai_bi  commented on Dec. 20, 2019, 12:36 a.m.

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


    • 4
      wleung_bvg  commented on Dec. 15, 2019, 1:02 a.m.

      The real question is whether S5 will actually be rejudged instead of just being marked as system tested.


      • 0
        shuai_bi  commented on Dec. 20, 2019, 2:50 a.m.

        S5 was fully systested.


  • 9
    richardzhang  commented on Dec. 9, 2019, 4:46 a.m. edited

    I wish to appeal the judging verdict for my S3 submission. It TLE'd on systests (AC on pretests), however when I resubmit the exact same code, it gets 33/100. Is it possible to rejudge my submission because of this? (Link to resub https://dmoj.ca/submission/1747867)


  • 4
    Ninjaclasher  commented on Dec. 8, 2019, 1:15 p.m. edited

    There is currently an issue regarding the judges. Please DO NOT join the contest until further notice, as none of your submissions will be judged. Anyone who is currently in the contest and is significantly affected by this may request to be unrated.

    Update: This issue has now been fixed. Anyone who had a window overlapping 7am EST to 8:30am EST may request to be unrated.