The first Algorithm Competition Online Rounds of the 2019 Topcoder Open has arrived! Round 1A will be held on Saturday April 20, 2019 at 12:00 UTC -4.Registration is open for the round and closes at 11:55 UTC -4, April 20 2019.
Did you win an Automatic Berth a.k.a Bye for Round 1? Check out the list of members who won an automatic berth to Round 2 here.
How many will qualify? The 750 highest scorers from each Round 1 will win a spot in Round 2 of the Algorithm Competition. Note: To be eligible to advance from an Online Round Match, the Competitor must finish the Match with a point total greater than zero.
There will be one more Round 1 — Round 1B on Wednesday, May 1, 2019 at 07:00 UTC -4.
Best of luck to you in the Arena! -Topcoder
Update: Match Summary and Editorials: https://www.topcoder.com/blog/2019-topcoder-open-algorithm-round-1a-editorials/
I think you need to mention positive scores are needed to qualify..
And it also looks like the only thing need mentioning! If you have positive score, you will be in top 750...
Just received an email saying I’ve won a bye to Round 2. Will there be another email for those who got to Round 4 (or even to the Finals) through the SRM point system in one of the 4 online stages? I imagine people who advanced through that rule won’t be eligible to participate in Round 2 despite the bye, right?
Who is the writer again?
That would be me.
Bonjour! Loved your sin(t) codeforces rating graph! another maxima expected after few contest. :)
Is it rated?
Yes, the match will be rated
Will this count towards the points for TCO regionals?
No it won't :)
1000 point problem's precision issues were frustrating, otherwise the round was good!
That's because the intended way was to avoid any floating-point number calculations until the very end?
I wanted to do that but don't the bounds mean it can overflow 64-bit integers?
If the percentages are set to 99, you end up (almost) doubling up to 100 times, which seems like it should be too much.
Maybe the idea is that such cases will never arise because they don't have a unique answer... but it doesn't seem obvious that this is true.
If at any point you reach a value which is greater than n*target, then you know that the average is larger than target, so you can stop calculating then.
You're right — I forgot to think about the average when I was doing the estimations.
Indeed, the intended solution was to use integers only and since I expected many people wouldn't do that, I expected the problem to provide plenty of challenge opportunities. Apparently, creating a test wasn't that easy, thus most solutions failed on the System Test.
Where can i find the intended solution? i looked at few solutions and all used floating point computation somehow.
The editorial is now posted: https://www.topcoder.com/blog/2019-topcoder-open-algorithm-round-1a-editorials/
I managed to pass this problem by calculating everything in cents, so only integers needed. To round a real number to the nearest int, I used
int(x + 0.5).I had a separate divide function that rounded numbers fully in integers.
So, what is best solution for 250 problem?
Just brute force all possibilities.