Axons are the building blocks of CortexFramework, AVUTECscamera operating system and AI integration platform.

With Axons a Cortex can be built.

A Cortex can be described as a collection of Axons put in a certain order. Axons receive, create and forward messages, depending on the Axon.

Messages contain pieces of information, MessageInfos.

 

Example: An ANPRAxon will receive a message containing an image (MSG_IMAGE). It takes the images and performs ANPR. After recognition this Axon will add a MessageInfo (MI_ANPR_RESULT) to the message containing the recognized license plate . The message is send to the next Axon in line, in this scenario mostly the ANPRThresholdAxon.

 

Together a set of Axons create a pipeline handling incoming video streams, processing them and outputting results to third party systems.

 

Source/input axons, processing axons and output axons.

The axons can be subdivided in three categories:

•Input Axons:
generate images or what are called MSG_IMAGE, a message containing a source image.

•Processing Axons:
process the images coming from the input Axons.
Each Axon can add an Axon-specific MessageInfo to the received message. Axons further in the Cortex use the MessageInfos as a trigger to execute certain behavior.

•Output Axons :
act as a sink to output the result of a Cortex to a third party system. The values of MessageInfos are used to determine what information is send and when.

 

Settingspanel and viewpanel

Each Axon has its own settingspanel, where the actual configuration of the settings take place.

Most Axons have their own viewpanel. In the viewpanel the images coming from one of the sensors (depending on the flow of the Cortex) can be seen. The image shows all the processing that is done earlier in the Cortex.

 

Triggers tab

The Avutec rule engine is an important part of CortexFramework to tailor functionality. With the rule engine triggers and actions can be scripted per Axon to obtain extra functionality required for a project.

Therefor each Axon has it is own triggers tab, where a script can be implemented.

Scripts are generally composed by the AVUTEC support team.