In the equetronic-api repo there are two instances of the same file, the EqHelpers.js file, which are in the following locations:

Submodule: equetronic-helpers/EqHelper.js
Helpers: helpers/EqHelper.js

And whenever any change is made in the submodule the same exact change should be made to the helper file.

Reason

The equetronic-helpers repo is hosted on git6. The equetronic-api is running on a Digital Ocean server. The equetronic-helper is added as a submodule to the equetronic-api repo. now the instance running on the Digital Ocean during the time of writing this document cannot access the submodule hosted on git6. Hence, as a work around a copy of the EqHelper.js file from the submodule is added to the equetronic-api/helpers directory.

Simulator can be more robust

When we were creating the simulator file, real time data and issues were not clear. So the simulator has the following drawbacks that can be improved:

Since we are importing data from the training records and the data is sorted desc in ids, when we create a new sample file, the live file plays it backwards, therefore the last ehm_data record is played first.