It's pretty silly of you to say that GOOGLE IS NOT DOING JUSTICE when you don't even have a clue what they are doing. If you do not cheat, you will not get picked up for cheating, regardless of whether your algorithm is very similar to someone else's. If you do cheat, you will be caught. It is as simple as that.
On May 19, 5:28 pm, Wasif Hossain <[email protected]> wrote: > After the Qual. Round, I found that My logic (and the code also almost > similar) for SNAPPER problem is SAME as Neal.wu who is in 1st position. Then > what about this case? will I or Neal.wu be both SUSPENDED or not? Moreover, > I am from Bangladesh and he is from USA or some other country. If anyone of > us is suspended, then I think that Google IS NOT DOING JUSTICE because > nobody of us know each other. Again, if we both proceed to Round 1, then I > think that only SIMILAR CODE CHECKING is not done by google but something > else!!! My opinion is that, google checks the SAME IP Address first. If it > is so, then checks for the next criterion (Similar Code) , and only when > this is also proved, then the contestant is eliminated. Please let us know > your opinion. > > Thanks a lot. > > On Wed, May 19, 2010 at 3:20 AM, Muntasir Azam Khan <[email protected] > > > > > wrote: > > > Isn't a smart cheater an oxymoron? What incentive does somebody have for > > > cheating in smart way? Is it like when a unskilled programmer pays a > > > skilled one to get them high rank in an algorithm competition or > > something? > > > > > There is lot more to do when it comes to identify the cheaters. > > > > > What if we just add a line trying to just print something or introduce > > > > some no op codes like > > > > i = i + 0 ; > > > > > what should we actually compare. at source, or assembly or binary > > itself. > > > > Basically how do we catch the smart cheaters. > > > > > let us not go by probability numbers here saying only 10% of code is > > > > similar hence the code is not copied as 90% of code is still original > > > > becuase it is often this 10% which is the real trick needed to solve > > > > the problem. > > > Actually, last year there were some lists of cheaters put up by users. > > These were generated using something much simpler than the approaches > > suggested here - mostly checked whether two submissions were exact > > matches or had an edit distance less than some small number. You can > > find lists of cheaters from last year in this forum thread at > > TopCoder: > >http://forums.topcoder.com/?module=Thread&threadID=650760&start=0&mc=41. > > The interesting thing is that even such simple checks found a huge > > number of cheaters in the Qual round. > > > But these were made by contestants, the GCJ admins will likely be > > employing different methods. > > > -- > > 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 > athttp://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.
