Stewart, I am afraid to say that your description so far has not been specific enough to describe what the intended behavior is, nor what the incorrect behavior is; and the pictures and code you're provided indicate that your model is likely too complex for me to be of much use.  It is entirely possible that there's a bug in (say), MASON's neighborhood lookup functions.  But to help you any further, I'd need a functioning, stripped down and simplified example.

Other routes you could take:
(1) print out what MASON is providing in its x and y bags for neighborhoods.  Does anything look amiss?
(2) instead of using MASON's neighborhood lookup function, why not just compute the four locations yourself?  It'll be much faster.  And then you can compare it against what MASON is providing.

Sean

On Jul 31, 2015, at 4:30 PM, Stewart Aitken <[log in to unmask]> wrote:

> Yes still has the bug.
> It may be that MASON can't do what I am trying to do with it.
> 
> Kind regards,
> 
> Stewart Aitken.
> 
> On 31 July 2015 at 15:22, Sean Luke <[log in to unmask]> wrote:
> By this you mean that it still has the error?
> 
> On Jul 31, 2015, at 3:29 PM, Stewart Aitken <[log in to unmask]> wrote:
> 
> > Thanks Sean,
> >
> > I have changed those two lines by removing the mySpace.tx and it works as before.
> 
> 
> 
> -- 
> 
> 
> 
> EMAIL DISCLAIMER http://www.york.ac.uk/docs/disclaimer/email.htm