...
The setup file contains the information about which config file to use for the software.
The config file contains the global configuration for all libraries (naming convention, file structure, …)
A library contains a collection of elements. It exists of the library file and the database for this one library.
...
The idea is that you could switch between different setupsetups. Each setup could have a different folder structure and naming convention. By using the different setup files you can separate them completely.
...
| Info |
|---|
When the config file defined in the setup file is not access ableaccessible, the startup screen will appear. |
...
The config file contains the global configuration of all libraries.
Here you can define the file structure and naming convention for each of the libraries.
When creating you your new setup for the software you can specify the file location.
The file can be stored everywhereanywhere. The setup file referenced to this config file.
...
A library contains a collection of elements.
Each library exists of two parts:
...
Define the file structure in the global settings and overwrite values or path patterns that are relevant for this library. This way, the naming convention stays consistent over through all libraries, but you can control individual parts by overwriting values depending on this specific library.
...
The models will be trained from by das element for you. Over time these models will improve, will contain more categories and help to label your library even further and better.
...