 | | Re: C$ - Code Only
|
| (...) Kevin, I really didn't plan on having a "contest". Sorry if I misled you. I know several people have code, and they wanted to know how it stacks up against other people's code. I'm just trying to set-up a format in which they can do that. So (...) (21 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto)
| | | | | Re: C$ - Code Only
|
| (...) Folks who read rtlToronto can skip this part. I added it because I'm cross posting to robotics.rcx. For those who don't know, rtlToronto had a contest with robots playing Connect Four. Creating a robot for this is double faceted. Getting (...) (21 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto, lugnet.robotics.rcx)
| | | | | Re: C$ - Code Only
|
| (...) Steve, I'm obviously curious to undestand what all you packed into your code. Kevin (21 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto)
| | | | | Re: C$ - Code Only
|
| (...) Steve, I'm obviously curious to undestand what all you packed into your code. Kevin (21 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto)
| | | | | Re: C$ - Code Only
|
| (...) Steve, One of the thing I noticed when working on the book generation code, there are typically multiple unique drop sequences that get you to the same board state, even when just picking the best hypothetical moves. In an RCX environment that (...) (21 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto)
| | | | | Re: C$ - Code Only
|
| (...) Steve, One of the thing I noticed when working on the book generation code, there are typically multiple unique drop sequences that get you to the same board state, even when just picking the best hypothetical moves. In an RCX environment that (...) (21 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto)
| | | | | Re: C$ - Code Only
|
| (...) Forgive a clueless question here, but is QuiteC different than NotQuiteC? If so where can I learn more about it? Thanks! The oldest mention of the term "QuiteC" I could find on LUGNET was only 3 weeks ago but MAYBE I'm searching wrong? see (...) (21 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | Re: C$ - Code Only
|
| (...) NQC compiles not quite C code into LEGO firmware opcodes. You download the .rcx result, and LEGO firmware interprets the program. This makes it slow. QuiteC and brickOS both use H8 native C compilers that spit out H8 assembly code directly. (...) (21 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | Re: C$ - Code Only
|
| (...) I think most people seriously underestimated how hard building the robot would be. The funny thing is, all of rtlToronto's events have the same general premise: Build a robot that does something. Second, if you can make the robot do it well, (...) (21 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto, lugnet.robotics.rcx)
| | | | | Re: C$ - Code Only
|
| (...) yes, it was all about the ~game~ within the C$ game. I really wanted to scare you with that bit of info at the last min. (...) you must be SO PROUD of yourself. :) Chris "I stole an opening book off the web." S.H. (21 years ago, 6-Feb-04, to lugnet.org.ca.rtltoronto)
| | | | | Re: C$ - Code Only
|
| (...) I am admittedly biased toward BrickOS; however, I am wondering if you attempted to free some memory in BrickOS by disabling features that you didn't need? If you are only going to run one program (whether single threaded or multi), you can (...) (21 years ago, 7-Feb-04, to lugnet.org.ca.rtltoronto, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | Re: C$ - Code Only
|
| (...) Nope. I knew there was a certain amount configurability in brickOS, but I assumed it would be hard to get it down to a minumum. (...) With librcx, I started out with the minimum and added only what I needed. (...) Kevin (21 years ago, 12-Feb-04, to lugnet.org.ca.rtltoronto, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| |
