Hello Coders,
The 25th edition of 101 Hack is here. This time we have 5 interesting challenges lined up for you.
The contest commences on 20th May 2015 at 16:30 UTC, and will run for 2 hours. You can sign up for the contest here.
You will get a Hackerrank T-shirt if you ranked in top 10.
The problem statements will be available in English and Chinese.
Problem Setters
Problem Testers
GL&HF
What's wrong with my solution for Devu and a Journey on Metro?
Or this is the right way but i have some mistakes in another part of code? May be problem with precision.
I've just calculated P[k][v] — probability to be in vertex v in k steps. You can do it naively since k <= 50 and n <= 50. Instead of "some illegal Markov chain magic" :)
Shocked by the performance of the top teams from the ICPC world final, we intended to make the problem relatively easy to make many people feel like [tourist].
i failed because of this :
actual : 2.568375701948238E9
expected : 2568375701.948237895965576172
I did all calculations in doubles (there's no long double in java)
Maybe it is because of the precision checker's problem, I do not think 1e-6 will make precision problems for this kind of challenge.
Anyone knows how codeforces implemented the precision checker?
You should find default CF checkers in Polygon.
Is it a bug in some standard checker or was it written specifically for this problem?
I've got some questions about editorial. Please, can someone prove me: Why minimal number of swaps <= 1 and why it's optimal to do swaps which decrease the string size as less as possible?
There seem to be problems with grading of Devu and a Journey on Metro, several people have complained that outputs that are (within precision margin) the same as expected ones are judged as incorrect.
Sorry about this, the implementation of the precision check has problem, it just check the absolute difference, and haven't check the relative difference, it is a disaster! As a tester, it is mostly my fault, because I just checked if cout << fixed << setprecision(5) and setprecision(6) and setprecision(7) will get the correct answer or not. I do not know the built-in precision checker only check the absolute difference. :(