search

cirelesna / pe

0 stars 0 forks source link

Period prediction #3

Open cirelesna opened 5 months ago

cirelesna commented 5 months ago

image.png

Data should be analyzed before making a period prediction if not the predictions would be inaccurate. User should be prompted to provide more up to date information

soc-pe-bot commented 4 months ago

Team's Response

Moving forward, we will have additional checks in place to ensure that the latest three cycle lengths are recent before making a prediction. There will also be a reminder in the UG to remind users to update their period regularly.

Also, this severity is medium because a user who regularly updates their period inputs will receive accurate predictions.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Not so useful prediction

image.png

While the users record period in the past (2022), the predicted next period is also in 2022, which is not that useful, maybe can consider making the prediction always happen in the future.

[original: nus-cs2113-AY2324S2/pe-interim#1516] [original labels: type.FeatureFlaw severity.Medium]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

Prediction is based on the average cycle lengths of past period inputs. Therefore, a user needs to update PulsePilot regularly to get accurate prediction. Moreover, it is not likely for a user who has not updated her period inputs since 2022 to do a period prediction in 2024.

Moving forward, we will have additional checks in place to ensure that the latest three cycle lengths are recent before making a prediction. There will also be a reminder in the UG to remind users to update their period regularly.

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: [replace this with your explanation]

## :question: Issue response Team chose [`response.NotInScope`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
## :question: Issue severity Team chose [`severity.Medium`] Originally [`severity.High`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]