I have a doubt regarding the contest timings.In the mail I received , its mentioned that the timing is Tuesday, March, 29, 2011 16:00 (UTC) which turns out to be 8:30 pm in India. But in the last codeforces match codeforces beta-64 the timing mentioned in the mail was Saturday, March, 26, 2011 16:00 (UTC) which turns out to be 9:30 pm in India. How is it possible that the same time on different days is differed by 1 hour?
Problems D and E were not what I expected from codeforces. Reading input and Writing output in Problem E was the hardest point in this problem and this is not how the standard codeforces tasks look like. I hope problem setters understand that it's not cool to make the output readable for humans by making it long and hard-to-print.
I guess that output format that contains not only "YES" or "NO" is needed to check that answers found by participants are correct as well as to check that situation when contestant found the solution while the author program didn't , doesn't happen. I didn't like it much either, but it is understandable.
Besides that I don't think that reading input and writing output is the most difficult part of problem E but we shall not discuss that before the end of the contest:)
Think output format for D should be tested on pretests completely and not give penalty for it, because I received +3 on it with forgotten dot at the end and double space :( .
I agree with what some people have said, problems D and E were not quite the best.
A: was very straightforward, but that's fine, specially in div 2 only.
B: was easy but needed a little thought.
C: was great, the statement was clear, needed thinking and solutions were nice.
D: was long and boring overall, just tons of code without much thinking was enough.
E: I didn't have time to tackle it in the contest, but seemed approachable, but I really didn't like the fact that looking for periodic tables was part of it. That may be more real life like, but in programming contests the speed and skills to find a periodic table that can be put on code fast seemed overly boring to me.
NOTE: I just mentioned this as my opinion, I appreciate all the effort the codeforces team puts into the contests, but those last two problems seemed to me that having div 2 only so often is making the writers to run out of nice problems quickly.
The problem setter could have easily replaced the atomic symbol with just atomic number or provided atomic symbol along with atomic number. Then it would have been a great problem... In programming contest even in the online contest searching google for data can be just interesting but not conventional. Here we are for our coding and algorithmic contest , not for searching contest... by the way problem E was very good if we ignore this fact..
But… :) I think there was too "coding hard" problems D and E. In problem E, i would appreciate for example list of all possible atoms, cause i won't have to rewrite them by hand…
Plus, it is a bit weird that so many people end up having the same standing in the contest (same score). Thus you could have a standing of say a 90, only to find out that there are actually 300 people above you. I think we need a more granular scoring system.
Problem E was too easy to code? You could have replaced the atom names with the number of their atomic number in words. In other words, you would say ninety nine instead of 99. This can be variable (ex you can say ninetynine or ninety-nine or in any human understandable format, occasionally also replacing with roman numerals). Also you could have removed the restriction of 100 and made it all the way to thousand (or one thousand). This would have made the contest more interesting.
I'm confused that some test case(just like #85) in problem E take over 20s to get result in my own computer, but it still got AC(with 600 ms) when I submit. Why ? I have tested some codes of others' and have the same problem. I don't think my computer runs 50 times slower than the server's.
which turns out to be 8:30 pm in India.
But in the last codeforces match codeforces beta-64 the timing mentioned in the mail was Saturday, March, 26, 2011 16:00 (UTC)
which turns out to be 9:30 pm in India.
How is it possible that the same time on different days is differed by 1 hour?
Reading input and Writing output in Problem E was the hardest point in this problem and this is not how the standard codeforces tasks look like.
I hope problem setters understand that it's not cool to make the output readable for humans by making it long and hard-to-print.
Sorry, I am afraid of saying that this contest is a little boring,the last two problem needs too much code ,but few about algorithm!.
Firstly I am a great fan of you. Bows!
Secondly my statement was just sarcastic.