markdown-body entry-content container-lg" itemprop="text">

This repository has been archived, and it is no longer maintained. You can find the submission to the conference in the Zenodo repository.

Paper DOI: 10.1109/ACSOS61780.2024.00032

An Aggregate Vascular Morphogenesis Controller for Engineered Self-Organising Spatial Structures

Authors

Angela Cortecchia (*)	Danilo Pianini (*)	Giovanni Ciatto (*)	Roberto Casadei (*)
angela.cortecchia@unibo.it	danilo.pianini@unibo.it	giovanni.ciatto@unibo.it	roby.casadei@unibo.it

(*) Department of Computer Science and Engineering
Alma Mater Studiorum --- Università di Bologna - Cesena, Italy

About
- Experiments
Getting Started

About

In the field of evolutionary computing, the concept of Vascular Morphogenesis Controller (VMC) has been proposed in to model the growth of artificial structures over time.

A thorough analysis of the VMC model revealed some limitations:

assumes the organization structure is a tree, here intended as a directed acyclic graph with a single root and with a single path connecting the root with each leaf;
the model is implicitly synchronous, as it assumes that (i) the evaluation of the nodes must proceed from the leaves to the root (and back), and (ii) the update of the whole tree occurs atomically.

Although, depending on the context, these assumptions may be acceptable, in general they may induce (possibly hidden) abstraction gaps when VMC is used to model real-world systems, and, at the same time, limit the applicability of the pattern to engineered morphogenetic systems.

To address these limitations, in this work, we propose FieldVMC: a generalisation of the VMC model as a field-based computation, in the spirit of the Aggregate Programming (AP) paradigm.

Experiments

This repository contains the source code for the experiments presented in the paper "An Aggregate Vascular Morphogenesis Controller for Engineered Self-Organising Spatial Structures".

The experiments want to show the capabilities of the proposed model in generating self-organising spatial structures.

Some examples of the generated structures are shown below:


Starting Structure	Self-Organised Structure

Structure after cutting a part of it	Self-Organised Structure after the cutting

The images show the evolution of a structure from a starting configuration to a self-organized structure, see the Understanding the experiments section for a detailed explanation of the images.

The goal of this evaluation is to show that the proposed FieldVMC supports the construction of the same structures of its predecessor, and, in addition, that it can work in scenarios not previously investigated. To this end, we designed a set of five experiments:

self-construction from a single node (growth from seed),
self-repair after disruption (network segmentation) with no regeneration (cutting),
self-integration of multiple FieldVMC systems (grafting)
self-segmentation of a larger structure (budding), and
self-optimisation of multiple large structures into a more efficient one (abscission and regrowth).

Getting started

Requirements

In order to successfully download and execute the experiments are needed:

Internet connection;
Git;
Linux, macOS and Windows systems capable of running Java 17 (or higher);
1GB free space on disk;
GPU with minimal OpenGL capabilities (OpenGL 2.0);
4GB RAM.

Limitations

The experiments do not generate any form of data to be evaluated on, the evaluation is purely visible at the moment;
On different monitor types with different resolutions, the graphical interface could appear a bit different;
For GUI interpretation, please refer to the Simulation Graphical Interface section.

Understanding the experiments

In all the experiments, the cyan area represents the resource and the yellow area the success, with darker shades indicating higher values.
Nodes are represented as circles. The root is identified by a dark outer circumference.
The size of a circle depends on the amount of resource and success received relative to all other nodes in the system: we fix the maximum possible size $D$, we compute the maximum amount of resource $R$ and the maximum amount of success $S$ across all nodes in the system; then, for each node in the system with success $s$ and resource $r$, we determine its size $d$ proportionally to $D$ as $d=\frac{D (r + s)}{R + S}$.
Their color depends on the amount of resource nodes have and is assigned based on the hue of the HSV color space, with the most resource associated with indigo, and the lowest with red.
Dashed lines are communication channels, solid black lines represent the tree structure, and green (resp. orange) lines depict the resource (resp. success) distribution flows, the thicker they are, the more resource (resp. success) is being transferred.

The experiments are:

oneRoot: self-construction from a single node (growth from seed),
cutting: self-repair after disruption (network segmentation) with no regeneration (cutting). The segmentation is performed by removing a part of the structure after 500 simulated seconds, and the nodes are not able to regenerate the missing part;
graft: self-integration of multiple FieldVMC systems (grafting). Two distinct structures are created, and after 500 simulated seconds, they are merged into a single structure;
graftWithMoreLeaders: self-segmentation of a larger structure (budding). Two distinct structures are created with possibly more than leader each; after 500 simulated seconds, they are merged into a single structure;
graftWithSpawning: self-optimisation of multiple large structures into a more efficient one (abscission and regrowth). Two distinct structures are created, and after 500 simulated seconds, they are merged into a single structure. During the simulation, nodes are able to spawn new nodes and destroy the ones that are not useful anymore, resulting in an optimized structure.

Walk-through the experiments

This section provides a brief overview of the oneRoot experiment, to give an idea of how the experiments work. The oneRoot experiment simulates the self-construction of a structure from a single node. The detailed instructions to reproduce the experiment are in the section "Reproduce the entire experiment".

The simulation can be launched with the command ./gradlew runOneRootGraphic, or the one in the section "Extremely quick-start". Once the simulation has started, the Alchemist GUI will open. After the time needed for Alchemist to load the simulation, it will show the initial structure, that is a single black point representing the root node, in between the resource (cyan gradient) and success (yellow gradient) layers. For more details of the simulation (e.g., the appearance, the meaning of the different shapes, etc.) see section Understanding the experiments. Now the simulation can be started by pressing the P key on the keyboard. By pressing the P key again, the simulation will pause (and resume). When the simulation starts, if you wish to execute it at "real time" speed, press the R key (and again to return to the fast speed). For other features of the GUI, please refer to the Simulation Graphical Interface section.

As seen in the sequence below, the structure evolves from a single node to a more complex structure. Firstly, the structure results to expand towards the center of the available resources. This happens because the spawned nodes are in a zone with higher resources, used as weight in the leader election phase, thus the newly created node gets elected as the new leader, which results in an expansion towards the center of the resource layer. While the root gains more resources, nodes will spawn children based on their local success, meaning that the nodes which sense more success from the environment have higher probability and capabilities to spawn new children, resulting in an expansion towards the center of the success layer. The structure then stabilizes in what appears to be the optimal configuration, and the structure stops evolving.

Sequence of images showing the evolution in time of the structure in the oneRoot experiment.

Reproduce the entire experiment

WARNING: re-running the whole experiment may take a very long time on a normal computer.

Simulation Graphical Interface

The simulation environment and graphical interface are provided by Alchemist Simulator. To understand how to interact with the GUI, please refer to the Alchemist documentation.

Extremely quick-start of a basic experiment -- `(ba|z|fi)?sh` users only

Requires a Unix terminal ((ba|z|fi)?sh)
curl must be installed
run:

curl https://raw.githubusercontent.com/angelacorte/vmc-experiments/master/vmc-basic-example.sh | bash

the repository is in your Downloads folder for further inspection.

Reproduce the experiments through Gradle

Install a Gradle-compatible version of Java. Use the Gradle/Java compatibility matrix to learn which is the compatible version range. The Version of Gradle used in this experiment can be found in the gradle-wrapper.properties file located in the gradle/wrapper folder.
Open a terminal
Clone this repository on your pc with git clone https://github.com/angelacorte/vmc-experiments.git.
Move into the root folder with cd vmc-experiments
Depending on the platform, run the following command:
- Bash compatible (Linux, Mac OS X, Git Bash, Cygwin): ./gradlew run<ExperimentName>Graphic
- Windows native (cmd.exe, Powershell): gradlew.bat run<ExperimentName>Graphic
Substitute <ExperimentName> with the name of the experiment (in PascalCase) specified in the YAML simulation file. Or execute ./gradlew tasks to view the list of available tasks.

The corresponding YAML simulation files to the experiments cited above are the following:

oneRoot: self-construction from a single node (growth from seed) ./gradlew runOneRootGraphic,
cutting: self-repair after disruption (network segmentation) with no regeneration (cutting) ./gradlew runCuttingGraphic,
graft: self-integration of multiple FieldVMC systems (grafting) ./gradlew runGraftGraphic,
graftWithMoreLeaders: self-segmentation of a larger structure (budding) ./gradlew runGraftWithMoreLeadersGraphic, and
graftWithSpawning: self-optimisation of multiple large structures into a more efficient one (abscission and regrowth) ./gradlew runGraftWithSpawningGraphic.

NOTE: The tasks above will run the experiments with the default parameters, that are the one on which the evaluation has been performed.

Changing experiment's parameters

To change the parameters of the experiments, you can modify the YAML files located in the src/main/yaml folder. The parameters that can be changed are:

seed: the seed used to generate the random numbers, to have reproducible results;
leaderRadius: the radius within the leader election is performed;
maxResource: the maximum resource available inside the environment;
maxSuccess: the maximum success available inside the environment (usually set to the same value of maxResource);
initialNodes: the number of nodes to be created at the beginning of the simulation (except for the oneRoot experiment, which starts with a single node);
resourceLowerBound: the minimum amount of resource that a node can have in order not to die (for the oneRoot and graftWithSpawning experiments);
maxChildren: the maximum number of children a node can have (for the oneRoot and graftWithSpawning experiments);
minSpanWait: the minimum time a node has to wait before spawning a new node (for the oneRoot and graftWithSpawning experiments);
killingRange: the range within the nodes are removed (for the cutting experiment);
layerX: the position of the resource and success layer on the x-axis;
layerY: the position of the resource and success layer on the Y-axis (for the oneRoot experiments);
maxY & minY: position of the layer on the y-axis (for every experiment except oneRoot);
width & height: the width and height of the rectangle in which the nodes are placed, used to simplify the management of the nodes' translation (for every experiment except oneRoot);
gaussianShape: the shape of the Gaussian distribution used for the resource and success layer.

Each change in the parameters will result in a different structure generated by the simulation. The parameters provided in the YAML files are the ones used for the evaluation and the ones evaluated as "optimal".

For further information about the YAML structure, please refer to the Alchemist documentation.

Simulation entrypoint

The simulations in which nodes are able to spawn new nodes are the oneRoot and graftWithSpawning experiments. Their entrypoint can be found at src/main/kotlin/it/unibo/collektive/vmc/VMCSpawning.kt. The program takes as input the aggregate function withSpawning(), which uses a function that implements the spawning (and killing) logic.
Shortly, a node can spawn if:

it has enough resources to spawn a new node and remain alive;
it has less than the maximum number of spawn-able children,
it has been stable for at least the minimum time required; or it is the only node in his surroundings.

Similarly, a node can die if:

it has less than the minimum amount of resources required to survive;
it has no children;
it has been stable for at least the minimum time required.

The simulations that do not involve the spawning of new nodes are the cutting, graft, and graftWithMoreLeaders experiments. Their entrypoint can be found at src/main/kotlin/it/unibo/collektive/vmc/VMCWithoutSpawning.kt. It simply uses aggregate functions to elect leaders and manage the resource and success distribution.

angelacorte/vmc-experiments

ErrorLooks like something went wrong!

About

Topics

Resources

Uh oh!

Stars

Watchers

Forks

Releases 7

Packages 0

Uh oh!

Contributors 4

Languages

Error
Looks like something went wrong!

Packages