Hello!
As the new Contest Coordinator at HackerEarth, I'm honored to invite you to HackerEarth HourStorm #8; it's a 1-hour competition with 3 traditional (but nice) algorithmic tasks. We are going to hold it on Friday at 14:30 GMT (you can check the time here.
For traditional algorithmic tasks, you will receive points for every test case your solution passes, so you can get some points with partial solutions as well. Check contest page for more details about in-contest schedule and rules.
MazzForces is the setter of this round and I'm the tester of problems. Prepared problems were interesting and I enjoyed solving them, I hope you find them interesting too. As usual, here are the prizes for the top three contestants:
- $75 Amazon gift card
- $50 Amazon gift card
- $25 Amazon gift card
In addition, the top 5 will win HackerEarth t-shirts.
GL & HF.
Let's discuss the problems after the contest!
P.S. I'm sorry for the problem occurred on problem B (A counting problem). I was the tester of this contest; the problem was Anand has changed test cases and didn't run my solution on test cases again and his solution has a little bug, so test cases 17-29 were wrong. We apologize for this problem. Now rejudge is done.
Here are the winners:
In general, it would be great if you add the date and time in the blog
Added, thanks.
How come time mentioned in the blog and in the link are different?
The right time is 14:30 GMT, timing will be updated in the contest page.
Clashes with TopCoder SRM 750.
SRM starts at 19:30 PM, so there is a half hour between contests.
Sorry, missed it because I added HourStorm to calendar when it was scheduled at 16:00 GMT.
I wonder how can I receive my gift cards from previous contests? Had not got any e-mails
From my experience it takes them about a month to send the gift cards.
Well, I guess HourStorm #3 was more than a month ago
We have gone through our leaderboard and realized that there was miss from our end due to human error and we extend our apologies for the same. You must have received a mail regarding the same. We will forward you the prize next week.
Yes, thank you!
The constraints for "A summation problem" is too big. It leads a weird situation that to pass you must define modulo as a constant like const int mod = 123123123, otherwise int mod = 123123123 will get tle :(.
I saw that from your submissions now, but the intended the solution passed in approximately half of the TL, so I thought the constraints are okay.
What changes so much when we add const ?
That's so 2005 to think that if reference solution fits into half the TL then everything is ok. There was a lot of evolution on this topic since. I think good idea is to write not only solutions you want to pass, but also those you consider too slow and then set time limit somewhere around geometrical mean
According to standings, I have a scored solution for last problem submitted at 1:00:19 — for a contest that is supposedly 1 hour long. Is this a bug or a feature? :)