Algorithm Fields

For a more condensed summary this information is available in table view

The specification for Algorithm has these fields:

name

Required-string
a human-readable name to ease identification and discoverability for human users

Example

"Object Detection Algorithm for detection of faulty weld seams"

description

Required-string
a short, human-readable description of the Algorithm to aid a human user in analysing the Algorithm’s capabilities and its applicability to a certain problem

Example

"This algorithm can be used to solve a specifc problem, and applies some fancy technologies."

classification_schema

Required-enum [Simulation, ML, others]
the classification of the Algorithm, to describe the specialization area

Example

"ML"

type

Required-string[]
a detailed list of attributes to describe the Algorithm’s field of application

Example

["neural network", "deep learning", "convolutional neural network", "CNN"]

version

Optional-string
the version, as defined by the provider

Example

"1.0"

list_of_microservices

Required-string[]
a list of Microservice Asset IDs, which are contained in the algorithm

Example

["MSID_MYMS_A", "MSID_MYMS_B"]

deployment_mapping

Required-string
a mapping specifying which microservice should run on which host. By default each microservice is assigned a respective host, but this behaviour is not always ideal (eg. when two or more Microservices may need to run on the same host)

Example

{"MSID_MYMS_A": "HOSTID_MYHOST_A", "MSID_MYMS_B": "HOSTID_MYHOST_A"}