COMP3122-2324-Project / Simpsyber

0 stars 0 forks source link

[DEFECT] Incorrect scoring if you encounter no defect throughout the run #1

Open ghost opened 7 months ago

ghost commented 7 months ago

If you are lucky enough to encounter no defect throughout the run, you should have 0 Change Failure Rate and 0 Mean Time to Recover, which is perfect and deserves a straight A.

However, the scores seem to be deducted for no reason in this case:

As the game design ties our performance to an overall score, that is, all we do in the game is to strive for a higher score, it is important to have the scoring system work as intended.

ivanLeung-18 commented 7 months ago

I agree with your perspective. Normally, scores should not be deducted without a reason. I think you do not have encounter any event of Mean Time to Recover (MTTR) such as recovering from any failure. For example, I try one times that I don't make any action on Kanban Page. the picture 1 can show the result, 'Mean Time to Recover' is displaying '--'. which mean the initialization value.

Picture 1: image

In my case, it shows numerical values like '0d' or '4.9d' since I have doing any recover or encounter the any defects (Picture 4) in the game. This could be the root cause of the unexpected score deductions.

Picture 2:

螢幕截圖 2024-02-09 上午4 54 22

Picture 3:

螢幕截圖 2024-02-09 上午12 46 15

Picture 4:

螢幕截圖 2024-02-09 上午4 56 49
ghost commented 7 months ago

@ivanLeung-18 From your results, I think the root cause can be the Change Failure Rate, since we do not have a number displayed in Mean Time to Recover unless we have Change Failure Rate > 0.

Also another issue here: how come Change Failure Rate is capped at B grade? Has anyone managed to achieve an A?

ivanLeung-18 commented 7 months ago

@happytommy123 I agree your idea since if we don't make the any event of Change Failure Rate such as any defects exists. it would make the Change Failure Rate == 0. The Mean time to recover would be "--". there are demo video to show evidence. Video 1 is not trigger any event of Change Failure Rate. Video 2 trigger any event of Change Failure Rate such as any defects exists.

Video 1:

https://github.com/COMP3122-2324-Project/Simpsyber/assets/156775094/3f75c37b-cab7-453c-8791-b1dc40af7a57

Video 2:

https://github.com/COMP3122-2324-Project/Simpsyber/assets/156775094/41206a69-bfb2-4431-a292-cb3817b3b023