From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,7a2d45f282a1da1c X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-08-15 20:30:17 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!arclight.uoregon.edu!wn13feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi_feed4!attbi.com!sccrnsc04.POSTED!not-for-mail Message-ID: <3F3DA544.7080604@attbi.com> From: "Robert I. Eachus" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: float with 24-bit resolution References: <3F3CCB0F.543478AF@adrianhoe.nospam.com.my> <3f3cd7f4$1_2@news.tm.net.my> <3F3CE28D.B841A191@raytheon.com> <3F3D10B7.9080707@attbi.com> <3F3D2195.D984062E@raytheon.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit NNTP-Posting-Host: 66.31.71.243 X-Complaints-To: abuse@comcast.net X-Trace: sccrnsc04 1061004616 66.31.71.243 (Sat, 16 Aug 2003 03:30:16 GMT) NNTP-Posting-Date: Sat, 16 Aug 2003 03:30:16 GMT Organization: Comcast Online Date: Sat, 16 Aug 2003 03:30:16 GMT Xref: archiver1.google.com comp.lang.ada:41550 Date: 2003-08-16T03:30:16+00:00 List-Id: Mark Johnson wrote: > and we have to take that information plus the current location to > generate a new location at the iteration rate of the model (say 30 Hz). > The instructor is dealing with terms such as speed, bearing, and changes > in those values while the software inside must generate X / Y position > and do the appropriate conversions. Right, my only point was that since the LSB difference in distances was small in any one time interval, errors would build up if you did: for t in 1..n loop -- t in milliseconds X := X + Vx; Y := Y + Vy; end loop; instead of: for t in 1..n loop X := X0 + t*Vx; Y := Y0 + t*Vy; end loop; (Of course, you are actually doing this for a set of tracks and looking for matches.) I actually had to explain why the first formulation was not "more efficient." (Or maybe it was more efficient, just wrong. My attitude has always been that I don't care how fast you can calculate a wrong answer.) -- Robert I. Eachus "As far as I'm concerned, war always means failure." -- Jacques Chirac, President of France "As far as France is concerned, you're right." -- Rush Limbaugh