Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a naive implementation of aimacode#81 . I can see a few issues emerging principally around measuring performance based on the state of an agent.
If I take the vacuum world example, we will probably want a performance measure that take into account the number of actions performed by the vacuum cleaner. When moving or sucking, the vacuum cleaner consumes energy and hence we should somehow associate a state to the agent. The idea would be to be able to measure at each point in time, how much energy has been consumed by the agent and score the performance based on that.
The current Agent API has a run method that returns an updated environment but doesn't update the agent state. I am not sure what's the best way to handle it:
STATE
type parameter to the agent trait. Update this state in the run method and return the updated agent alongside the updated environment. But then it feels that we could move the run method out of the agent altogether and put it in aSimulation
trait/case class