Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

research/650-stygmergy-controller #650

Open
jharwell opened this issue May 11, 2020 · 0 comments
Open

research/650-stygmergy-controller #650

jharwell opened this issue May 11, 2020 · 0 comments

Comments

@jharwell
Copy link
Owner

jharwell commented May 11, 2020

There are a number of different dimensions to this, but the main idea is that
the controller does things based on what it finds in the environment, instead of
having any memory (i.e. it is purel reactive, and thus easy to model
mathematically).

  • Robot allocates a D1/D2 task based on what it encounters in the environment,
    and if it doesn't encounter anything interesting for a set period of time, it
    chooses a random task instead. No task length estimates!

  • Robots bring blocks they pick up partway back to the nest and then MAYBE drop
    them near a pile of other blocks (i.e. doing caches without the cache data
    structure), where the chance a robot drops vs. not is somehow based on the
    size of the cache/pile of blocks it encounters.

From Lerman2003, if the controller is purely reactive to the environment, they
it SHOULD be possible to predict their rate of ecountering various stimuli
sufficiently well that the overall task allocation distribute can be modeled by
the rate equation idea from the paper.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant