This might be obvious, but have you tried putting a breakpoints in at that
method and using the relevant tools in your IDE to see what is going on?
Due to the complexity inherent in ABMs it's not uncommon for bugs to not be
in the obvious spot in the code. The old fashion print statement can also
be really useful when trying to see what is going on (i.e., print to
console when the agent state changes - don't rely upon the inspectors).
Writing a couple unit tests and running them on a simple variation of your
ABM will also help track down the code.

Robert Zupko

On Wed, Jan 23, 2019 at 12:01 PM Annetta Burger <[log in to unmask]> wrote:

> Because it is very hard to troubleshoot the ABM code without Inspectors.
> I'm going to dig into the geomason1.5 source code to find why the
> Inspectors are not working in geomason1.5. I understand there may be a fix.
> Does anyone have any suggestions of where to look and how I might solve
> the problem of Inspectors not working in MASON?
> As a reminder, I'm just trying to get the simple Inspector code to operate:
>     public Object getSimulationInspectedObject() {
>         return state;
>     }  // non-volatile
> Thanks.