From: rars-d-request@lysator.liu.se Subject: rars-d Digest V97 #44 X-Loop: rars-d@lysator.liu.se X-Mailing-List: archive/volume97/44 Precedence: list MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----------------------------" To: rars-d@lysator.liu.se Reply-To: rars@lysator.liu.se (Rars mailing-list) ------------------------------ Content-Type: text/plain rars-d Digest Volume 97 : Issue 44 Today's Topics: Re: Very silly question Re: compiling rars Re: Very silly question Reminder for BORS participants Re: compiling rars Re: Reminder for BORS participants Re: newbie ------------------------------ Date: Thu, 17 Apr 1997 20:16:55 -0400 (EDT) From: Daniel Brooks To: Rars mailing-list Subject: Re: Very silly question Message-ID: Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 17 Apr 1997, David Jones wrote: :)How do I unsubscribe from this damn thing? Surely it's not that bad, but, to unsubscribe, send a message to the mailing list with a subject of 'unsubscribe' (no qoutes) and presto, youre off! Daniel Brooks | Daniel Brooks -- Email: d-brooks@usa.net | | PGP key fingerprint - DB 10 E4 99 4C B5 86 11 3B 5A BC 56 34 37 57 18 | ------------------------------ Date: Thu, 17 Apr 1997 18:00:22 -0700 From: Max To: rars@lysator.liu.se (Rars mailing-list) Subject: Re: compiling rars Message-Id: <3.0.1.32.19970417180022.0087bde0@carlsbad.ucsd.edu> Content-Type: text/plain; charset="us-ascii" Daniel writes: >Well, no, I don't. but here is part of the list of error messages: > >Linking RARS.EXE: >[...] >Linker Error: Undefined symbol _RACEMODE in module carz.CPP >[...] >Linker Error: Undefined symbol Car::RecordMovie(void far*) in module CARZ.CPP >Linker Error: Undefined symbol Car::ReplayMovie(void far*) in module CARZ.CPP These and many of the other errors are in movie.cpp. Near as I can tell, the source file is there, but it is not in part of the project file. I had to make that change, and then it all worked fine. - Christopher Lund ------------------------------ Date: Fri, 18 Apr 1997 14:57:57 +0800 From: "Allan W. S." To: "Rars mailing-list" Subject: Re: Very silly question Message-Id: <199704180705.PAA14491@eastgate.cyberway.com.sg> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit ---------- > From: David Jones > To: Rars mailing-list > Subject: Very silly question > Date: Thursday, April 17, 1997 4:46 PM > > How do I unsubscribe from this damn thing? Not at all silly. I found my answer too. To unsubscribe send a mail to rars-request@lysator.liu.se with Subject: unsubscribe Allan. ------------------------------ Date: Fri, 18 Apr 1997 19:52:24 -0300 From: Maido Remm To: rars@lysator.liu.se Subject: Reminder for BORS participants Message-Id: <3.0.1.16.19970418195224.18ef7a88@tamm.ebc.ee> Content-Type: text/plain; charset="us-ascii" The working week is over and I am glad to remind you that next oval racing event at Milwaukee 1 mile oval is in the middle of next week, deadline for submissions on Tuesday. CAR SIZE 10x15 feets! Pre-race testing points to one and only one simple fact - no matter how fast you are, you have to finish race to be successful. Most competitors from last race will not survive to the end of race. They collide with slow cars (H4 - 40 mph, H5 - 5 mph!). Thus I strongly suggest to spend this weekend in designing anti-collision code. Consider the presence of unnormally slow cars on the track. For beginners: There is two simple ways to look ahead and avoid collisions: 1. The predefined situation check in situation structure s.dead_ahead For example: if (s.dead_ahead) result.vc = 0.9 * s.v; // slow down add steering algoritm to this if you like. The dead_ahead is a simple and works rather well as it is, but it only looks ahead 2.5 car length (37.5 feets) which is obviously not enough if very slow car is on your way. You should try to design more intelligent way of looking ahead. 2. A better way to look ahead is to use nearby structure (defined in car.h). This presents you the data about 5 closest cars in front of you. You can then define your action if you see a car in front of you within 400 feets (as I do) or any other distance. Some sample code: int i, kount; for(i=0;i<5;i++) if(s.nearby[i].who<16) { x=s.nearby[i].rel_x; // distance to right (or left if < 0) y=s.nearby[i].rel_y; // distance ahead vx=s.nearby[i].rel_xdot; // relative lateral speed component vy=s.nearby[i].rel_ydot; // relative forward speed d=sqrt(x*x + y*y); // distance to other car if (vy >= 0.0) continue; // the car in front is faster else if(x*vx>0) continue; // the cars are moving apart else if(d > 400) continue; // look ahead 400 feets and be careful else if(d > 200) danger = 1; // look ahead 200 feets ++kount; // if we see there a slower car if (kount > 1) danger = 2; // or several slow cars within 400 feets else danger = 2; // - danger! } For more, look in jackbot.cpp (very efficient!). Jas, WappuCar, Bulle and Ralph2 have advanced passing code also. P.S. Do not get confused while reading JackBot, it was designed for older version of rars, the x and y in s.nearby are defined differently. Currently x is distance to the right, y distance to front. dy == -1 means that front car is 1 feet/sec slower than you are. dx == -1 means that other car is moving left 1 feet/sec relative to your car. See you next week ( finishing race), Maido ------------------------------ Date: Fri, 18 Apr 1997 15:34:13 -0400 (EDT) From: Daniel Brooks To: Rars mailing-list Subject: Re: compiling rars Message-ID: Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 17 Apr 1997, Max wrote: :)Daniel writes: :) :)>Well, no, I don't. but here is part of the list of error messages: :)> :)>Linking RARS.EXE: [several very dumb errors] :) :)These and many of the other errors are in movie.cpp. Near as I can tell, :)the source file is there, but it is not in part of the project file. I had :)to make that change, and then it all worked fine. Ok. Now that you mention it, I don't remeber seeing that in the project, so I'll go add it. Thanks a bunch, Daniel Brooks Maybe someone should upload a replacement with a fixed project file. | Daniel Brooks -- Email: d-brooks@usa.net | | PGP key fingerprint - DB 10 E4 99 4C B5 86 11 3B 5A BC 56 34 37 57 18 | ------------------------------ Date: Fri, 18 Apr 1997 16:16:48 -0400 (EDT) From: rscott@NetUSA.Net (Ralph Scott) To: rars@lysator.liu.se Subject: Re: Reminder for BORS participants Message-Id: Content-Type: text > P.S. Do not get confused while reading JackBot, it was designed for older > version of rars, the x and y in s.nearby are defined differently. Currently > x is distance to the right, y distance to front. dy == -1 means that front > car is 1 feet/sec slower than you are. dx == -1 means that other car is > moving left 1 feet/sec relative to your car. Now *I* am confused. Has the nearby structure changed from v.64 to v.65? To my knowledge, it has not. ---ralph ------------------------------ Date: Fri, 18 Apr 1997 23:54:25 +0200 (MET DST) From: bm321465@muenchen.org (Henning Klaskala) To: rars@lysator.liu.se Subject: Re: newbie Message-Id: <199704182154.XAA00517@henkhost.muenchen.org> Content-Type: text On April 10, Daniel Brooks wrote: > Yea, but like I said, we don't all know that much about C++, let alone the > math I've seen in the robots I've downloaded. I'm only a sophmore, and > havent had trig yet. I am going to borrow a trig text book to learn as we > go. Fortunatly, there are several juniors that have had trig. Knowing trig may help, but isn't necessary. I don't even include math.h in my robots. Nevertheless they are usually the fastest. The math in the other robots is there only to impress and confuse newbies. ;-) Henning -------------------------------- End of rars-d Digest V97 Issue #44 **********************************