Now an interesting question... Take a look at neal.wu's code for problem B: "Fair Warning", which I have attached to this mail. It is so long that you can't type, debug and verify the output for this program in 10 minutes - this was the time taken by neal.wu. Now how do you explain this? Did he copy a part of the source from a header file?
On Mon, May 17, 2010 at 5:40 PM, Dhruva Sagar <[email protected]>wrote: > good point > > > On Mon, May 17, 2010 at 17:39, Felipe Sodré Silva <[email protected]>wrote: > >> Of course, but Paul's point is that once you have an algorithm that is >> fast enough for running under 4 minutes, it's not worth wasting time trying >> to figure out a faster one. >> >> >> On Mon, May 17, 2010 at 8:53 AM, Dhruva Sagar <[email protected]>wrote: >> >>> Well the more efficient your algorithm, the faster you'll get the output >>> and the faster you'll submit it. >>> So yes it matters >>> >>> >>> On Mon, May 17, 2010 at 17:20, Manish kumar Singh <[email protected] >>> > wrote: >>> >>>> Thank you for that wonderful explanation! But may I know whether or not >>>> the efficiency of the algorithm is also a deciding factor?? >>>> >>>> >>>> On Mon, May 17, 2010 at 5:13 PM, Paul Smith <[email protected]>wrote: >>>> >>>>> neal.wu solved 1-small after 6 minutes and 12 seconds, 1-large after 6 >>>>> minutes and 48 seconds. 2-small after 15 minutes and 19 seconds, 2-large >>>>> after 16 minutes and 12 seconds, 3-small after 27 minutes and 5 seconds, >>>>> getting it wrong once, and 3-large after 27 minutes and 30 seconds. >>>>> >>>>> As he was completely finished in 27 minutes and 30 seconds, with 1 >>>>> wrong attempt at a small input which costs him 4 minutes, his total score >>>>> is >>>>> 99 points, and his penalty time is 31 minutes and 30 seconds. >>>>> >>>>> Nobody scored 99 points in less than 31 minutes and 30 seconds, so neal >>>>> is the "winner" of the qualification round. >>>>> >>>>> Penalty time is more important in future rounds if your score is near >>>>> that required for 1000th place, and indeed penalty time may decide the >>>>> winner in the finals in the case of a tie. >>>>> >>>>> Paul Smith >>>>> >>>>> [email protected] >>>>> >>>>> >>>>> On Mon, May 17, 2010 at 12:14 PM, Manish kumar Singh < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> I'm new to code-jam and I'm excited to participate in the next year. >>>>>> Can any one let me know how is the rank decided when the marks are the >>>>>> same. >>>>>> Also how much does efficiency matter? >>>>>> >>>>>> One last question.. in the scores listed below, what does the time >>>>>> 6:12, 31:30, etc signify? >>>>>> >>>>>> Rank ContestantScore Penalty 10pt23pt 10pt23pt 10pt23pt Problem >>>>>> statistics 4:55 >>>>>> 9739/11495 correct5:40 >>>>>> 8169/9676 correct 15:19 >>>>>> 3370/4417 correct16:12 >>>>>> 2499/3041 correct 14:19 >>>>>> 8273/8744 correct22:22 >>>>>> 3108/7844 correct 1 >>>>>> [image: United States] neal.wu 99 31:30 6:12 >>>>>> 6:48 >>>>>> 15:19 >>>>>> 16:12 >>>>>> 27:05 >>>>>> 1 wrong try 27:30 >>>>>> >>>>>> Thank you. >>>>>> >>>>>> Regards, >>>>>> Manish >>>>>> >>>>>> -- >>>>>> 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]<google-code%[email protected]> >>>>>> . >>>>>> For more options, visit this group at >>>>>> http://groups.google.com/group/google-code?hl=en. >>>>>> >>>>> >>>>> -- >>>>> 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]<google-code%[email protected]> >>>>> . >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/google-code?hl=en. >>>>> >>>> >>>> -- >>>> 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]<google-code%[email protected]> >>>> . >>>> For more options, visit this group at >>>> http://groups.google.com/group/google-code?hl=en. >>>> >>> >>> >>> >>> -- >>> >>> Thanks & Regards, >>> Dhruva Sagar. >>> >>> -- >>> 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]<google-code%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/google-code?hl=en. >>> >> >> -- >> 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]<google-code%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/google-code?hl=en. >> > > > > -- > > Thanks & Regards, > Dhruva Sagar. > > -- > 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]<google-code%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-code?hl=en. > -- 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.
B.cpp
Description: Binary data
