As correct predictions would have a MASSIVE impact in understanding the data and thus cause of weight loss/gains, we need to start giving it a shot.
Below you can see the new endpoint given data for two prediction szenarios for the next day.
The response has always the same two keys "wightInCaseTakenShitBeforeWeighing" and "weightInCaseNotTakenShitBeforeWeighing"
GET https://dubisoftw-weightracker-backend.azurewebsites.net/api/v1/prediction
{
"wightInCaseTakenShitBeforeWeighing": 133.87,
"weightInCaseNotTakenShitBeforeWeighing": 133.43
}
Add a UI feature to display the prediction and the error margin.
Please only display the usecase that is relevant.
As correct predictions would have a MASSIVE impact in understanding the data and thus cause of weight loss/gains, we need to start giving it a shot.
Below you can see the new endpoint given data for two prediction szenarios for the next day. The response has always the same two keys "wightInCaseTakenShitBeforeWeighing" and "weightInCaseNotTakenShitBeforeWeighing"
Add a UI feature to display the prediction and the error margin. Please only display the usecase that is relevant.