Application runs at texture.utia.cas.cz.

Post content First the idea is introduced, then the features and future features are explained and in the end the used architecture and technologies brief description is elaborated.

Why is there need for such apllication

Texture features are specific data extracted for a wide variety of tasks, such as in computer vision. There are many algorithms for extracting these features, but each one has different characteristics. Although comparative studies have been written, they are often limited by the number of features and the specific testing environment. So there is no tool or resource in which to universally compare textural features. Maybe until now. The developed benchmark does just that. The benchmark can test and evaluate features universally for multispectral data (for any number of spectra).

Application

I would like to briefly introduce the application. Where you can: Managing own experiments

Exploring experiments of others

Setup and run an experiment and the view the results in detail

Visualize the features

Future application features The benchmark is still in development and I work on it in my free time, there are going to be added following essential application features soon:

  • Algorithm comparison
  • User input of features

and other application features:

  • more features
  • more evaluation criteria
  • choice of criteria

Architecture and technologies

It is a web application with cloud computing and symptom evaluation. The entire benchmark is divided into a client application and a server part.

The client application is programmed using the Flutter framework, and since it is a multi-platform technology, it can be deployed not only as a web application but also as a native application for Windows or Linux.

The server part of the application is then created using three servers: a communication server, a solution server and a database server. The communication server serves the web application and provides security and sends requests that it cannot handle to the resolving server (typically requests for the extraction and evaluation of texture features). The solving server then contains a queue for the extraction and evaluation of features, which is served by workers, the amount of which can be scaled and the overall performance of the benchmark can be scaled. Both previously mentioned servers then communicate with the database server (MongoDB), in which they store and retrieve data. In the server part, Python and the Flask framework are used for the most part, but also, for example, binary files compiled from C++ subprograms containing feature extraction algorithms. These are then supplemented with Python subprograms with the same purpose.