Chapter 1. Package Structure in MeVisLab

Table of Contents

1.1. What is a Package?
1.2. How Does MeVisLab Find Packages?
1.3. Who "Knows" About Packages?

1.1. What is a Package?

A self-contained directory structure that consists of the following components:

  • PackageGroup

    • PackageName

      • Package.def

      • bin

      • Configuration

      • Documentation

      • lib

      • Modules

      • Projects

      • site-packages

      • Sources

      • TestCases

Figure 1.1. Example for a Package Tree

Example for a Package Tree

In this example, we have a PackageGroup named MyPackageGroup. Below it, two packages can be found: General and Development. Below each package, the typical folders can be found as shown for the General package. This example was generated with the Project Wizard in MeVisLab.

The folders Networks and ToolRunnerReports in the figure above are on the same level as the PackageGroup.

A PackageGroup can contain any number of packages, and of course there can be different PackageGroups.

The PackageIdentifier is defined by <PackageGroupName>/<PackageName>, e.g., the MeVisLab Standard package has the identifier MeVisLab/Standard.