This project is inspired by an another project on pharo: , and this version uses:
.
Add the repository directly in Pharo thanks to the Iceberg.
Pharo 8, Pharo 9 and Pharo 10 :
(https://github.com/OpenSmock/MolAnts)
MolAnts require for the component aspect and
for the visual aspect.
The actual implementation of the TMASimulationManagerType: MASimulationManager, describe the manager of the MolAnts's system. It aims to put in relation every entity of the system. The simulation manager reference all the entities of the system in ordered collections or dictionaries and can access to all the entities and send them events. This feature permits to do concrete actions as interaction between ants and insects or ants and pheromones.
Futhermore, the simulation manager contains the main loop of the system. This loop send the simulationStepSend event message to each entity at each turn.
The simulation manager also implements methods to manage ants and insects (create, update and remove).
Finally this implementation provides start / pause / play / stop methods on the class side. Also on the side class the simulation manager provides the simulation data as step duration, width and height of the ground, and ant hill position.
Variables :
-simulationThread, containing the thread that sends at every step the event: * simulationStepSend*.
-step, is an integer that count the number of step.
-isAntHillCreated, is a Boolean that is put to true at the creation of the first ant and put to false when ants are removed.
-ants, is an ordered collection of ants. It contains all ants of the system. It is used to draw them on the ground and update the info panel.
-nbAnt, is an integer incremented at each ant creation. It is used to set the name of each ant component instance.
-insectsPos, is a dictionary containing all the insects of the simulation and their position. Key: a point. Value: an ordered collection of insects.
-nbDelivered, is an integer that count the number of insect delivered to the anthill.
-feedingPointsPos, is a dictionary containing all the feeding points of the simulation and their position. Key: a point. Value: an ordered collection of feeding points.
This event is consumed by all the entities of the simulation: ground, ants, insects and pheromones. Thanks to this event, the simulation loop in the simulation thread send at each step of the simulation the simulationStepSent message to all the entities. This permit for each entity of the simulation to do their actions.
This event also provides two messages: pheromoneNew:for: and pheromoneReturnNew:for, that needs to be implemented by the pheromone component. This two messages notify the Pheromone component of a pheromone creation or update.
This service is used by the ground and the ants. It describes methods that the simulation need to implement. Some of these methods permit to get information about the simulation. As all alive ants, insects positions and all pheromones positions and data. These data are used in the different implementations of ants to do consistent actions and in the ground to draw entities.
This service also describe two methods that the simulation need to implement: start/stop. And a variable: isRunning that the simulation implementation needs to keep up-to-date.
Variables :
-isRunning, is a Boolean that is set to true when the simulation is playing and set to false when it is paused or stopped.
The actual implementation of the TMAInsectsType: MAInsect, describe one insect. It means that if there are 50 insects on the simulation, there are also 50 instances of MAInsects. This implementation is very simple, insect only move on the ground randomly (waiting to be eaten...) at each step of the simulation.
Variables :
-position, is a point.
-ageInMs, is an integer.
Insects provide this event that is consumed by the simulation manager. This event describe one method positionChnagedFor:oldPos:newPos: that aim to be implemented by the simulation manager to keep the dictionary of insect positions up-to-date.
The actual implementation of the TMAFeedingPointType: MAFeedingPoint, describe one feeding point. This implementation is very simple, feeding point only receive eated message. This message decrease their capacity and when their capacity is equal to 0 the feeding point disappear from the ground.
Variables :
-position, is a point.
-capacity, is an integer.
Feeding points provide this event that is consumed by the simulation manager. This event describe one methods that aim to be implemented by feeding points.
The actual implementation of the TMAPheromonesType: MAPheromones, manage all the pheromones of the simulation. Pheromones are stored in two dictionaries, one for exploration's pheromones and one for returning's pheromones. Dictionaries has for key: the position and for value: an association: (an Ant -> an Integer). In this association the ant represent the last ant that visits the pheromone and the integer represent the intensity of the pheromone.
Pheromones are created by ants when they are moving on the ground and if an ant moves on a position where a pheromone already exists the pheromone is only update (intensity set to maximum). And at each step of the simulation each pheromone intensity is decreased by one.
Variables :
-maxIntensity, is an integer representing the intensity maximum of the pheromone.
-pheromonesDict, is a dictionary containing every pheromones of exploration. Key: a point. Value: an association (ant->intensity).
-pheromonesReturnDict, is a dictionary containing every pheromones of return. Key: a point. Value: an association (ant->intensity).
This service is provided by the pheromone implementation and used by the ground and the simulation manager. It provides two methods to retrieve the pheromones dictionaries. This aim to draw pheromones on the canvas and to detect if an ant is around pheromones.
The actual implementation of the TMAAntsType: MAAnt, describe one ant. For each ant created there is also one MAStage component and one MARole component created. There are associate through their component name (example: Ant29, StageAnt29 and RoleStageAnt29). The stage of the ant is created by the ant and the role is created by the stage. The implementation of the ant MAAnt permit to increase the age of the ant and to send to the stage the order to do the simulation step and to move.
Variables :
-position, is a point.
-ageInMs, is an integer.
This service is provided by the ant implementation isn't used by another component. However, it permits to describe methods that the ant implementation need to provide.
Variables :
-stage, containing the stage associate to the ant. It is used to access to the correct stage and do actions.
The actual implementation of the TMAStageType: MAStage, describe the stage of one ant. The stage manages the life cycle of an ant, it determines when an ant is an egg, an adult or when the ant is dead. It also sends to the role the order to do the simulation step and to move.
Variables :
-eggStateDurationInMs, is an integer to determine the duration in ms of the egg state of the ant.
-adultStateDurationInMs, is an integer to determine the duration in ms of the adult state of the ant.
This service is provided by the stage implementation and used by the ant implementation. It describes methods that the stage needs to implement because the ant implementation needs it to work correctly.
Variables :
-stageName, is an symbol used to know the actual stage of the ant: egg or adult.
-role, containing the role associate to the stage. It is used to access to the correct role to do actions and to stop the role component correctly.
Stages provide this event that is consumed by the simulation manager. This event describe one method stageChanged:for: that aim to be implemented by the simulation manager to remove, from the ordered collection ants, ants that are dead.
The actual implementation of the TMARoleeType: MARole, describe the role of one stage. The role provides the behavior of an ant at each step. Actually roles are implemented by MAQueen, MAFighter or MAWorker that are subclass of MARole. In each different implementation there is one method: doSimulationStepFor: that manage the action of the ant and one method: moveFrom: that manage the position of the ant at each step.
MAWorker variables :
-phase, is a symbol to represent the actual phase of the ant: explore of return.
-oldPositions, is and ordered collection of 5 points used by the worker role do not move on the last 5 position the worker already visit.
This service is provided by the role implementation and used by the stage. It describes methods that the role needs to implement because the stage implementation needs it to work correctly.
Variables :
-roleName, is a symbol used to know the role of an ant: queen, fighter or worker.
Roles provide this event that is consumed by the simulation manager. This event describes methods that aim to make the actions of the ants concrete in the system.
The actual implementation of the TMAGroundType: MAGround is the implementation of the system's view. It permits to draw all the entities of the system on a canvas and to keep the information panel up-to-date. It also permits to have a functional interface with buttons to start, pause and stop the system and also buttons to change the refresh rate.
Variables :
-mySpace, containing the BlSpace object.
-refreshing, is an integer used to know the actual refresh rate of the view.
-stepView, is a BlTextElement used to print the actual step on the view.
-nbInsectsView, is a BlTextElement used to print the actual number of insects on the view.
-nbDeliveredView, is a BlTextElement used to print the actual number of insects delivered on the view.
-nbPheromonesView, is a BlTextElement used to print the actual number of pheromones on the view.
-nbEggsView, is a BlTextElement used to print the actual number of eggs on the view.
-nbAntView, is a BlTextElement used to print the actual number of ants on the view.
-nbFeedingPointView, is a BlTextElement used to print the actual number of feedingPoints on the view.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent