Take the three metrics category classes, make them do the thing inside the model's predict() method. Test, probably.
Sensitivities are going to have to be hardcoded for now, since those are passed in from the frontend. Probably want to store those in a variable and have setters somewhere, or have them just read in all of the sensitivities from a file before predicting.
Try to write this in a way that will make frontend integration easy. MVC?
Related Epic:
Backend
Number Of Story Points: [number]
Acceptance Criteria:
[x] Ready when all 3 classes have been created
[x] Done when the UserSettingsModel uses the three metrics classes and MetricsCalculator to predict()
[x] Done when there is some form of testing done on this
Comments
This is an example comment
-- Name of person commenting
Description:
Take the three metrics category classes, make them do the thing inside the model's predict() method. Test, probably. Sensitivities are going to have to be hardcoded for now, since those are passed in from the frontend. Probably want to store those in a variable and have setters somewhere, or have them just read in all of the sensitivities from a file before predicting. Try to write this in a way that will make frontend integration easy. MVC?
Related Epic:
Backend
Number Of Story Points: [number]
Acceptance Criteria:
Comments