http://robowiki.net/w/index.php?action=history&feed=atom&title=Thread%3AUser_talk%3AMN%2FHard-coded_segmentation%2Freply_%287%29Thread:User talk:MN/Hard-coded segmentation/reply (7) - Revision history2026-05-04T07:45:39ZRevision history for this page on the wikiMediaWiki 1.34.1http://robowiki.net/w/index.php?title=Thread:User_talk:MN/Hard-coded_segmentation/reply_(7)&diff=32632&oldid=prevVoidious: Reply to Hard-coded segmentation2013-12-06T17:50:35Z<p>Reply to <a href="/wiki/Thread:User_talk:MN/Hard-coded_segmentation/reply_(2)" title="Thread:User talk:MN/Hard-coded segmentation/reply (2)">Hard-coded segmentation</a></p>
<p><b>New page</b></p><div>I don't know that a surfer vs random movement would have different optimal weights. :-) But yes, SpinBot and DrussGT have pretty different movement profiles. I don't doubt they have different optimal weights. But I still might be wrong, and that's why we have science. :-)<br />
<br />
Choosing among multiple weightings would mean a performance hit similar to adding [[Virtual Guns]]. So it's important to figure out how much of an impact sub-optimal weightings have in the first place. I've always thought we were fairly non-scientifically rigorous around here with some of this kind of stuff. It might be fun to try to do some rigorous testing. Actually that's one of the first ideas in a while that gets me excited about doing some more actual Robocoding.</div>Voidious