@meir It was my favorite problem too, but the problem is not easy in the sense that proving that the solution is correct is far from trivial. However since in these contests one normally uses their intuition and pattern recognition to come up with a solution fast and not full mathematical proofs, the problem writer was quite successful at confusing the contestants and preventing many from submitting the "intuitive" solution, which made it rather amusing =)
On May 9, 9:08 am, meir <[email protected]> wrote: > This was my favorite problem, since the solution is so easy > and yet many people were confused. > They also gave a complex example for the 3rd sample input even though > there is never a need to hold down any element not in it's position. > Statistically this was the hardest problem with only 58% solving > correctly and > and only half as many attempts as problem C(A more severe drop then > can be explained by simply > being the last problem). > So Kudos to google for being successfully confusing thousands of > contestants. > > Me > > On May 8, 6:03 pm, Carlos <[email protected]> wrote: > > > > > > > > > In the output specifications of GoroSort (problem D) we could read: *Answers > > with an absolute or relative error of at most 10-6 will be considered > > correct. * and in the sample we could see every output as floating point > > number (like 2.000000 or 4.000000). > > But every correct output is an integer number!! > > > so, why did they write this feature of output format? > > > Thanks!! > > Carlos. -- You received this message because you are subscribed to the Google Groups "google-codejam" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code?hl=en.
