And for the problems
Posted: Wed Dec 29, 2004 10:11 am
Since there is a lot of discussion about the problemset I feel saying some word myself.
First of all the Problemsetters made the problems deliberately easy so as to prevent the fate of ICPC2004. Only seven teams solved at least two and teams upto 65 solved one. Clearly, this seems to indicate that the Skill level of BUET Sphinx is same as that of some team solving 50 to 100 in OJ. But in reality there is certainly a huge gap between them. The main reason for this there was a problem of skill level 2 and then a jump to level 6. Therefore in NCPC the problemsetters tried to provide a set that is well distributed.
In my opinion they actually have done a good job, since the number of solved of each problem decreased at a steady rate.
As for the problems, I would like to give my views as a contestant:
Problem A: Very good introductory problem, no he hos, solve it and submit it.
Problem B: Well, i think this is the only odd one out. I must agree such one line code problem should not come in NCPC/ICPC contests. However, the answer was not directly visible so it required some analysis. The better and the experienced like Nasa, solved it on the spot, while less abled like me took longer and novices couldn't derive the formula.
Problem C: Another quality one from K. Zaman. Very easy to understand, requires some intuition to derive the solution and filled with traps which can be uncovered by the experienced.
Problem D: Easy geometry/trigonometry problem. In the contest, our team was the first to solve this and I think we used the most efficient method also. Many people used Binary_Search and others derived long and erroneous formula requiring 20+ lines of code. If one chooses to take the harder way, you are bound to be stuck and waste time.
Problem E: Trivial graph problem.
Problem F: If you find the right track this problem is very easy. A trivial minimum value( Calculas) problem. I think more teams could have solved it, but most probably they were interested in solving one of the harder ones, and did not have enough time after wasting precious time on solving easy problems like C and D.
Problem G: Very interesting problem, but haven't solved it yet.
Problem H: As mentioned earlier, a very painful to code problem.
Problem I: Haven't read it yet.
Problem J: This was the deceiver, on first reading many must have thought that this is a trivial BFS/DFS problem. But the difficulty level was realized only after reading posts regarding the problem.
As for the final words, it is true that problems B,D,F requires only knowledge of Math, but Math isn't much seperated from CS. The contests are regarding solving problems and Mathematics is the language while Computers are only tools. It is true that if problems B and F were replaced by some Graph/DP problem, there would be some change in Ranklist, but if one is totally unable to solve a problem while others can, then they don't have much right to complain.
First of all the Problemsetters made the problems deliberately easy so as to prevent the fate of ICPC2004. Only seven teams solved at least two and teams upto 65 solved one. Clearly, this seems to indicate that the Skill level of BUET Sphinx is same as that of some team solving 50 to 100 in OJ. But in reality there is certainly a huge gap between them. The main reason for this there was a problem of skill level 2 and then a jump to level 6. Therefore in NCPC the problemsetters tried to provide a set that is well distributed.
In my opinion they actually have done a good job, since the number of solved of each problem decreased at a steady rate.
As for the problems, I would like to give my views as a contestant:
Problem A: Very good introductory problem, no he hos, solve it and submit it.
Problem B: Well, i think this is the only odd one out. I must agree such one line code problem should not come in NCPC/ICPC contests. However, the answer was not directly visible so it required some analysis. The better and the experienced like Nasa, solved it on the spot, while less abled like me took longer and novices couldn't derive the formula.
Problem C: Another quality one from K. Zaman. Very easy to understand, requires some intuition to derive the solution and filled with traps which can be uncovered by the experienced.
Problem D: Easy geometry/trigonometry problem. In the contest, our team was the first to solve this and I think we used the most efficient method also. Many people used Binary_Search and others derived long and erroneous formula requiring 20+ lines of code. If one chooses to take the harder way, you are bound to be stuck and waste time.
Problem E: Trivial graph problem.
Problem F: If you find the right track this problem is very easy. A trivial minimum value( Calculas) problem. I think more teams could have solved it, but most probably they were interested in solving one of the harder ones, and did not have enough time after wasting precious time on solving easy problems like C and D.
Problem G: Very interesting problem, but haven't solved it yet.
Problem H: As mentioned earlier, a very painful to code problem.
Problem I: Haven't read it yet.
Problem J: This was the deceiver, on first reading many must have thought that this is a trivial BFS/DFS problem. But the difficulty level was realized only after reading posts regarding the problem.
As for the final words, it is true that problems B,D,F requires only knowledge of Math, but Math isn't much seperated from CS. The contests are regarding solving problems and Mathematics is the language while Computers are only tools. It is true that if problems B and F were replaced by some Graph/DP problem, there would be some change in Ranklist, but if one is totally unable to solve a problem while others can, then they don't have much right to complain.