search

SoarGroup / Soar

Soar, a general cognitive architecture for systems that exhibit intelligent behavior.
http://soar.eecs.umich.edu
Other
322 stars 70 forks source link

Soar Debugger not showing input link correctly #446

Open PLatCIC opened 2 months ago

PLatCIC commented 2 months ago

When running an application with several Soar agents, all with the debuggers open, I sometimes find that the input pane has not been updated correctly, as the following screen shot shows:

image

At this point some messages have been sent to this agent. The input pane shows ^message M5 and ^message M6, but these are old messages that were deleted long ago. However, if I print I2 in the trace pane I seen on M5 or M6, but I do see M18, M19, and M20, which is correct at this point. I tried in the upper right pane to go to other tabs and come back to input, but that didn't help.

It seems that the input pane is not always getting updated.

scijones commented 1 month ago

If you right click on the pane (where some text is) and click "properties" or "window->properties" (depending on where exactly you click), then you have a pop up box that should say "update automatically every nth decision". if that's 0 currently, change it to 1 and see if that helps.

garfieldnate commented 1 month ago

Mine was 0 by default! The dialog says "0 => none", which is unclear to me. I would say "0 (never)".

So maybe this is a bad default? Or does it significantly slow down the debugger to have these running, so it's a good default?

If this is a good default, I think we need to add a button or something to make the issue obvious and make it obvious how to change it.

scijones commented 1 month ago

This still might not resolve @PLatCIC 's issue, though. That same box says "update on stop", I believe. And that may be failing. I'm not sure the exact manner in which the agents are being run.

I am 60/40 towards thinking this is a good default because of how busy some input links can get. I agree about your wording change, though.