Update argument scores

[nickkeesG]

Split getArgumentScores into one for each score. Each score calculation ONLY considers users who voted AND have a relevant ingroup/outgroup. This should fix the issue we had with unusually low scores.

@sofvanh

[netlify]

✅ Deploy Preview for mindmeldtool ready!

Name	Link
🔨 Latest commit	84f1b55
🔍 Latest deploy log	https://app.netlify.com/sites/mindmeldtool/deploys/677cb3deca45dd000824fa24
😎 Deploy Preview	https://deploy-preview-8--mindmeldtool.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 48 (🟢 up 5 from production) Accessibility: 89 (no change from production) Best Practices: 92 (no change from production) SEO: 100 (no change from production) PWA: 60 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[sofvanh]

@nickkeesG Something seems wrong with the calculation of Fragmentation. A lot of the nodes that should score high in fragmentation are showing "Not enough data to calculate scores".

CEALLAR Dec 4 on this branch:

CEALLAR Dec 4 on main:

[nickkeesG]

There are two changes which need to happen in the ArgumentScoreHandler:

1. I made a mistake in getFragmentationScore. The final return statement should be multiplied by two
   return 2 * fragmentationSum / uniquenessSum // normalize score to range 0 - 1

2. Currently, a node can only get a fragmentation score if it ALSO gets a consensus score. I recommend we allow for nodes to receive scores, even if the other one isn't computable yet. There's an if statement at the end of argumentScoreHandler which currently requires neither score be null.

This is what is currently causing the graph to look way less orange than it should.

[sofvanh]

I'll think about how to deal with this - probably we'll show frag/cons even if the other one isn't being calculated.

What happened here is that the nodes that don't show a score on the branch were mostly voted on by people who are friends with one another, so the nodes have a fragmentation score but not a consensus score.

[sofvanh]

Solution: Allow consensus and fragmentation to be undefined, in which case show "More data needed" in score info.

[sofvanh]

Notice how with the new scoring algorithm we get more bright yellows!