crc901-proof-of-concept/ailibs

A collection of Java libraries for basic AI algorithms (JAICore) and automated software composition, in particular AutoML (softwareconfiguration)

AILibs

AILibs is a collection of Java libraries related to automated decision making. It currently consists of two building blocks. It is also home of the current version of the AutoML-tool ML-Plan.

• JAICore (Java AI Core) is a collection of projects with basic general purpose AI algorithms mainly in the area of logic reasoning, heuristic search, and machine learning
• softwareconfiguration is a collection of projects related to automatically configuring software systems. Here we also maintain the code for our AutoML flagship ML-Plan

**Find out more about AILibs and how to use it.

Using AILibs in your project

You can resolve each of our projects via a Maven dependency (using Maven central as repository).

Maven

<dependency>
  <groupId>ai.libs</groupId>
  <artifactId>jaicore-ml</artifactId>
  <version>0.1.5</version>
</dependency>

Gradle

dependencies {
    implementation 'ai.libs:jaicore-ml:0.1.5'
}

Setting up your IDE to work with AILibs

Eclipse

Navigate to the folder where you cloned this repository and run

  ./gradlew eclipse

This automatically creates the eclipse project files and configures the dependencies among the projects. Then open Eclipse and go to the import menu, e.g., in the package manager. Choose to import Existing Projects into Workspace, select the folder where you cloned the repository, and make sure to check the Search for nested projects option.

AILibs JavaDoc API

JAICore

• JAICore:jaicore-basic
• JAICore:jaicore-ea
• JAICore:jaicore-experiments
• JAICore:jaicore-graphvisualizer
• JAICore:jaicore-logic
• JAICore:jaicore-math
• JAICore:jaicore-ml
• JAICore:jaicore-planning
• JAICore:jaicore-processes
• JAICore:jaicore-search

Software Configuration

• HASCO
• ML-Plan

Troubleshooting

Maven dependency resolvement problems

In some cases, Maven is not able to import referenced dependencies on repositories different from the central Maven repositories, resulting in a build failure. To solve this problem, one might add the following repositories to the pom.xml to be able to properly execute maven compile or similar:

<repositories>
    <repository>
        <id>jitpack.io</id>
        <url>https://jitpack.io</url>
    </repository>
    <repository>
        <id>nexus.cs.upb</id>
        <url>https://nexus.cs.upb.de/repository/maven-releases/</url>
    </repository>
</repositories>