| | Re: Very strange problems
|
|
(...) Just that it is not pre-emptive. If you don't msleep() at the appropriate places in your code, you'll never go back to the scheduler or the other threads. This can come as a surprise, since you'll only notice it when one thread never executes. (...) (24 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
|
|
| | Re: Very strange problems
|
|
(...) That seems very likely. (...) Great :). The complete rules for the tournament can be found on the course web page, which is linked from our page. Tobias (24 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
|
|
| | Re: Very strange problems
|
|
(...) Neural nets do similar things. Our class had some very interesting cheaters. I actually thought the students learned as much from watching their robots cheat as they did from any other single component, since figuring out the "cheating" forced (...) (24 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
|
|
| | Re: Very strange problems
|
|
(...) Probably movement since it is easier. Our fitness function may have to change once we see the result though. GA tends to give you individuals that cheat every chance they get :). (...) It will be found at (URL) Right now we have our (...) (24 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
|
|
| | Re: Very strange problems
|
|
(...) What sort of "issues" are these? Are you referring to the normal issues of multithreading (synchronization, deadlock, etc.), or specific legOS-related problems with it? I have a program that uses a decent amount of multithreading, and I'd hate (...) (24 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
|