...
The prediction service represents a web interface which allows to request, insert and modify prediction data from the database. Operations are performed by sending URL requests, whereas each operation is well defined as a so called route. The property prediction service comes along with a graphical user interface at http://localhost:8004/ui/ which provides visual access to all available routes. Hereby, all routes involving the request of data are enlisted under the View section.
For this tutorial we are using only two routes. One to verify wherever an algorithm configuration exists and one to request all available predictions within from our database.
- /algoconfig/list
- /prediction/list
...
In our example we run a machine learning algorithm which produces a set of flare prediction predictions to store within our database. Hereby, the algorithm consists of a training phase and a test testing or prediction phase. Within the training phase the algorithm learns and tunes its parameters which then can be stored within the database as a configuration for later use. Afterwards, within the test testing phase, we use this configuration to compute flare predictions which are also stored within the database.
For the following example we assume, as the two functions 'train_model' and 'test_model' are already defined within the python script. Otherwise, we refer to the following HowtoHow-to: Ingest prediction data in database (REST API).
Given the two above two functions we could define our algorithm's workflow as follows:
...
Here you can download the full python source code.
request_ property prediction_data.py
For a more detailed implementation with dummy data you can download the python following demo script (recommended).
request_prediction_data_demo.py
| Info |
|---|
This page was adopted from Request property data from database (REST API). |