Difference between revisions of "User talk:Nat"
(moved User talk:Nat to User:Nat/Talk Archive 20090620: archive) |
(→MicroBot Wave Surfing: new section) |
||
Line 1: | Line 1: | ||
− | + | {{Navbox small | |
+ | | title = Archived Talk | ||
+ | | namespace = User | ||
+ | | parent = Nat | ||
+ | | page1 = Talk Archive 20090406 | ||
+ | | title1 = 2009/04/06 | ||
+ | | page2 = Talk Archive 20090620 | ||
+ | | title2 = 2009/06/20 | ||
+ | }} | ||
+ | |||
+ | == MicroBot Wave Surfing == | ||
+ | Anyone have 10TB of memory and hard disk to spare? I need that to perform my own microbot wave surfing. The large part of Wave Surfing is precise prediction, which nonetheless can't fit in micro. I wonder if I cached ''all'' the prediction and just access it at runtime. Now I roughly calculated. Let see, I restricted the location, absBearing, velocity and distance to all integer. Total possible location on the map is 764*564 = 430896 locations, multiply by 360 absBearing, ~950 distance, 17 velocity. Saves in short (2 bytes), contain x and y will result in around 764*564*360*950*17*2*2 = 10020917376000 B 9786052125 KiB = ~9,556,692 MiB = ~9,333 GiB = ~9.114 TiB. | ||
+ | |||
+ | Anyone have ideas how can I reduced those number? If I use 80*60 possible locations, 36 possible absBearing, 17 velocity and 19 possible distance, it still cost 43MB Note that this need to be preloaded into the robot, not calculating on-the-fly. |
Revision as of 06:17, 20 June 2009
- Archived Talk:
- 2009/04/06 - 2009/06/20
MicroBot Wave Surfing
Anyone have 10TB of memory and hard disk to spare? I need that to perform my own microbot wave surfing. The large part of Wave Surfing is precise prediction, which nonetheless can't fit in micro. I wonder if I cached all the prediction and just access it at runtime. Now I roughly calculated. Let see, I restricted the location, absBearing, velocity and distance to all integer. Total possible location on the map is 764*564 = 430896 locations, multiply by 360 absBearing, ~950 distance, 17 velocity. Saves in short (2 bytes), contain x and y will result in around 764*564*360*950*17*2*2 = 10020917376000 B 9786052125 KiB = ~9,556,692 MiB = ~9,333 GiB = ~9.114 TiB.
Anyone have ideas how can I reduced those number? If I use 80*60 possible locations, 36 possible absBearing, 17 velocity and 19 possible distance, it still cost 43MB Note that this need to be preloaded into the robot, not calculating on-the-fly.