The multi-agent framework is split up into different parts. Each component is provided with separate documentation. In this section, we give an overview of all framework elements. The whole framework is published at Maven Central.
The source codes are written in Java (latest release version) with a defined syntax structure; all code documentation is created with Doxygen. We are also using unit testing and the Git-Flow developing model.
Component | Status | Development & Results | Description |
---|---|---|---|
AgentSpeak(L++) | LightJason/AgentSpeak-Java has been deployed to maven central and is considered stable. It is currently in the testing phase to increase the amount of test-cases and finding/fixing bugs. All necessary elements exist and the core components are covered by tests. | This component defines the main agent structure. It contains the whole syntax and the base agent structure. It also supports agent generators and configuration to create sets of agents by ASL files. Due to the interface structure, all elements can be redefined. |
Component | Status | Development & Results | Description |
---|---|---|---|
Examples | LightJason/Examples is under development to always present working examples for tutorials and knowledge base articles. | Repository with the base structure of each LightJason AgentSpeak(L++) examples. The examples are presented and explained in the tutorial section. | |
Benchmark | LightJason/Benchmark demonstrates the scalability and performance of LightJason/AgentSpeak(L++). See → benchmark page for details. | This repository contains a benchmarking suite for the LightJason multi-agent framework. We try to keep the structure of a Java Microbenchmark Harness and adapted for the structure of a multi-agent system. |
Component | Status | Development & Results | Description |
---|---|---|---|
Docker | LightJason/Docker is considered stable and provides a working build and testing environment. | The LightJason Docker container is used for development and automating processes of LightJason. The container is split up into different sections with different build environments. |