... | @@ -13,7 +13,7 @@ Through the Energy Optimization Toolbox, a user of the SDK4ED platform will be a |
... | @@ -13,7 +13,7 @@ Through the Energy Optimization Toolbox, a user of the SDK4ED platform will be a |
|
|
|
|
|
The overall structure of the Energy Toolbox is depicted in the figure below:
|
|
The overall structure of the Energy Toolbox is depicted in the figure below:
|
|
|
|
|
|
[[/uploads/energy_toolbox_architecture.png]]
|
|
![image](https://gitlab.seis.iti.gr/sdk4ed-wiki/wiki-home/wikis/uploads/energy_toolbox_architecture.png)
|
|
|
|
|
|
The Energy toolbox comprises a front- and a back-end infrastructure. The front-end UI sends requests to the back-end by specific APIs. The back-end energy-analysis tools have been implemented as an individual Docker Image, which is deployed as an individual Docker Container and are invoked through the APIs (using Python Flask), perform the analysis on projects from Github and store all the results in a MongoDB database (independent Docker container) via specific APIs.
|
|
The Energy toolbox comprises a front- and a back-end infrastructure. The front-end UI sends requests to the back-end by specific APIs. The back-end energy-analysis tools have been implemented as an individual Docker Image, which is deployed as an individual Docker Container and are invoked through the APIs (using Python Flask), perform the analysis on projects from Github and store all the results in a MongoDB database (independent Docker container) via specific APIs.
|
|
|
|
|
... | | ... | |