How to prevent trickery / cheating with comp. time.




This forum is dedicated to questions regarding Challenge 3

How to prevent trickery / cheating with comp. time.

Postby sebsch » Fri 26. Sep 2014, 11:00

Dear organizers,

are the following two assumptions correct about tasks 1 and 2?

  • The final evaluation will be performed using exactly the same bagfiles you published in conjunction with the virtual machines.
  • Contestants are not required to submit or publish their full source code for solving the tasks.

In case both are true I wonder: How can you effectively prevent teams from cheating? I could imagine teams precomputing very accurate solutions to both tasks using much more processing power and time than available on the final evaluation hardware and afterwards hardcoding this accurate result into their solution program. Result: Perfect computational efficiency, perfect accuracy.

What is your stance on that?

Thanks in advance,
Sebastian
sebsch
 
Posts: 9
Joined: Mon 22. Sep 2014, 14:12

by Advertising » Fri 26. Sep 2014, 11:00

Advertising
 

Re: How to prevent trickery / cheating with comp. time.

Postby markusachtelik » Fri 26. Sep 2014, 18:01

Dear Sebastian,

we're currently preparing the instructions for the final evaluation, which will also clarify on this.
1) the final dataset will not be the one in the current VM. It is however recorded in the same area, we just did a second flight of approx. the same path. So the path changes, but the overall conditions (lighting, texture) are approximately the same. We will most likely publish a sequence of the beginning of each dataset, such that contestants can initialize their solution and make sure everything is going to run properly.

2) contestants submit the VM with their solutions, where they can remove their source code. Just make sure that your solution is still executable with the provided launch files.

Best, Markus
markusachtelik
 
Posts: 27
Joined: Mon 7. Jul 2014, 20:09

Re: How to prevent trickery / cheating with comp. time.

Postby sebsch » Mon 29. Sep 2014, 10:50

Markus, thank you very much for clearing that up.
sebsch
 
Posts: 9
Joined: Mon 22. Sep 2014, 14:12

Re: How to prevent trickery / cheating with comp. time.

Postby sebsch » Thu 6. Nov 2014, 10:20

Hi,

I was wondering whether you still intend to do this:

markusachtelik wrote:We will most likely publish a sequence of the beginning of each dataset, such that contestants can initialize their solution and make sure everything is going to run properly.


Thanks in advance,
Sebastian
sebsch
 
Posts: 9
Joined: Mon 22. Sep 2014, 14:12


Return to Challenge 3

Who is online

No registered users

cron