LISTSERV - MASON-INTEREST-L Archives

MASON-INTEREST-L Archives

August 2012

MASON-INTEREST-L@LISTSERV.GMU.EDU

	LISTSERV Archives
	MASON-INTEREST-L Home
	MASON-INTEREST-L August 2012

	Log In
	Register

	Subscribe or Unsubscribe

	Search Archives

Options:	Use Monospaced Font Show Text Part by Default Show All Mail Headers
Message:	[<< First] [< Prev] [Next >] [Last >>]
Topic:	[<< First] [< Prev] [Next >] [Last >>]
Author:	[<< First] [< Prev] [Next >] [Last >>]

Subject:	Re: Possible "bug" with getNeighborsMaxDistance
From:	Seth Tisue <[log in to unmask]>
Reply To:	MASON Multiagent Simulation Toolkit <[log in to unmask]>
Date:	Sat, 11 Aug 2012 10:09:59 -0400
Content-Type:	text/plain
Parts/Attachments:	text/plain (9 lines)

On Fri, Aug 10, 2012 at 6:38 PM, Sean Luke <[log in to unmask]> wrote:
> Okay, I see the issue.  You're doing toroidal lookups.  The toroidal code presently runs from max to min, doing toroidal wrap-around, without considering if a grid cell was looked up twice.  For example, if you have a 10x10 grid and are in location <5,5>, and do a 5-element range lookup, cell <5,0> will be in that collection, along with cell <5,10>, which is the exact same cell.

I remember when NetLogo had this same bug :-)

--
Seth Tisue | Northwestern University | http://tisue.net
lead developer, NetLogo: http://ccl.northwestern.edu/netlogo/

ATOM RSS1 RSS2

LISTSERV.GMU.EDU