Created and Installed File Structure

The setup program or the respective component creates the following file structure.

Installation Directory

The location of the installation directory depends on the operation system.

Windows

If no other directory has been specified for the installation, MERLIC is, by default, installed in the following directories depending on the installation type.

  • Current user: %LOCALAPPDATA%\Programs\MVTec\MERLIC-26.03
  • All users: %PROGRAMFILES%\MVTec\MERLIC-26.03
Linux

On Linux systems, there is no default installation directory. MERLIC RTE and MERLIC Frontend can be installed in a directory of your choice. However, the extracted files will be placed in a specific sub-directory named after the respective version, for example, "merlic-26.03.0".

Main Directory

In the following, the most important directories and files are described briefly. Depending on your installation, not all directories may be present.

bin:

This directory contains the executables in the sub-directory named after the execution platform. Furthermore, the directory contains additional files that are needed for the MERLIC application. Also, the HALCON tool hbench can be found in this folder.

calib:

This directory contains description files for the calibration plates, which you can use to calibrate your camera. It also contains a pdf document with calibration plates that can be printed for test purposes. For more information see the topic Calibrate Camera.

cmake:

This directory contains the CMake configuration files for the communication plug-in development SDK.

codemeter:

This directory contains files required for the license.

dl:

This directory contains pre-trained deep learning models for some MERLIC tools that use deep learning functionality.

drivers:

This directory contains drivers, e.g., for the GigE Vision Streaming Filter.

examples:

This directory contains various examples in different subdirectories:

  • communication_plugins: example communication plug-ins for different use cases
  • containers:
    • frontend: example Dockerfile and scripts that can be used as starting point for building containers for MERLIC Frontend
    • rte: example Dockerfile and scripts that can be used as starting point for building containers for MERLIC RTE
    • observability: examples for transmitting and monitoring recorded traces of the MERLIC Frontend
  • images: example images used in the provided examples
  • models: classifier file for example MVApps with classification
  • mvapps: MERLIC Vision App examples
  • recipes: example recipe files and MERLIC Vision Apps for MERLIC with process integration
  • rest_plugin_clients: example REST API clients in different programming languages. You can use the respective source code of the examples as template for your own applications and adjust them as desired.
  • tool_development:
    • convert_tools: converts custom tools of previous MERLIC versions for usage in MERLIC 5.2 or higher
    • procedures: HALCON procedures required to enable the use of interface procedures
    • tool_templates: example of a custom tool that can be used as a tool template for the development of your own custom tools
genicam:

This directory contains files for the GenICam standard. These files are required for the camera interfaces provided by MERLIC.

help:

This directory contains the documentation of MERLIC in all available languages.

include:

This directory contains the header files needed for the development of communication plug-ins.

lib:

This directory contains the libraries needed for the development of communication plug-ins.

ocr:

This directory contains pre-trained fonts.

som.d:

This directory is installed if MERLIC has been installed via the MVTec Software Manager (SOM). It contains files that are required by SOM for the installation, uninstallation, and future updates.

tools:

This directory contains the tools provided in MERLIC. It also contains the language files for the translation of the tool names and parameter names.

widgets:

This directory contains the Designer widgets of MERLIC.

Created File Structure for Configurations and Logs

This section will provide you with essential information about file paths related to configurations and logs in MERLIC for both Linux and Microsoft Windows operating systems. The following files are created during the run of MERLIC applications and remain on the system even after uninstallation. Therefore they are not part of the initial installation package.

Created Data

Folder description

Path shortcut in Linux

Path shortcut in Windows

Communicator/conf

This directory is the default location for plugin configurations.

~/.config/MVTec/

%AppData%\MVTec

Communicator/OPC_UA

This directory represents the "Certificate Store" for OPC UA applications. It contains different directories for trusted, own, and rejected certificates. For more Information, see OPC UA Plug-in.

Configurations

This directory contains the created configuration files for the Image Source Manager. For more information, see MERLIC Image Source Manager (ISM).

MERLIC5.ini

The MERLIC INI File is generated with the name "MERLIC5.ini" by default. It enables you to manually configure various settings for different components of MERLIC. For more information, see The MERLIC INI File.

Log file

MERLIC provides a logging mechanism that automatically writes log messages. For more Information, see Logging.

~/.local/share/MVTec/MERLIC

%LOCALAPPDATA%\MVTec\MERLIC

Directory Agent

The Directory Agent is a component that oversees the organization and access of the MERLIC software.

/tmp/MERLIC

%ALLUSERSPROFILE%\MVTec\MERLIC