Talk:Waves/Precise Intersection

From Robowiki
< Talk:Waves
Revision as of 12:18, 18 May 2009 by Nat (talk | contribs) (add credit)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Credits - Waves/Precise Intersection
Old wiki page: Rednaxela/SuperBotWidth
Original author(s): Rednaxela
Credits - Waves/Precise Intersection
Old wiki page: Garm/BotwidthCalculation
Original author(s): Krabb
Credits - Waves/Precise Intersection
Old wiki page: Skilgannon/PreciseIntersect
Original author(s): Skilgannon

You cannot post new threads to this discussion page because it has been protected from new threads, or you do not currently have permission to edit.

Contents

Thread titleRepliesLast modified
Bot width and GuessFactors219:20, 26 November 2012

Bot width and GuessFactors

When GuessFactor normalize angles based on MEA, doesn´t it distort the edges of the bot?

Looks like bots with distances farther away than when the wave was collected are calculated as being wider than they really are. Similar distortion happens when bullet power changes.

Am I missing something?

MN16:55, 26 November 2012

In the gun, I only ever collect/project the center angle. I only use precise bot width in my gun to find the exact center angle in the range. I use an imprecise bot width as the bandwidth in my kernel density when aiming.

In movement, the precisely predicted bot width is also the bandwidth in my kernel density. I still ignore it whenever collecting angles.

Voidious18:54, 26 November 2012

Using only the center of the range makes sense.

I wonder how much improvement is due to precise calculation, and how much is due to distortion (imprecise/unpredictable calculation).

MN19:19, 26 November 2012