"Relative" scale for metrics … comparing layouts to "min" achievable and "max" (not-optimized) costs for each metric #92
fredsilon
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hey, I just want to share a comparison I made for each metric.
I wanted to have some sort of reference points that could relate existing layouts to some "minimum" and "maximum" for each metric.
optimize_sawith 250 random permutations of "abcdefghijklmnopqrstuvwxyzäöüß,." … an approach that I observed as quite effective to find a min cost solution.optimize_sa [...] -s $permutation_000 … -s $permutation_249evaluatetool. I used 1e5 random layouts for this. (Default ngrams, default evaluation parameters, standard keyboard). The "maximum" reference in my case is defined as the median of the 1e5 rnd layouts … one median for each metric (their unweighted cost).I then plotted the result showing the unweighted cost for each metric:
I also scaled the plot as a second version:
Version 1: Unweighted cost

Version 2: Scaled to 0 (=min) and 100 (=median of random layouts)

I'm not sure, if this is really helpful to assess given layouts. Especially it's unclear, if the defined "min" and "max" reference points could be justified … especially as the random layouts spread a lot. But in the end it was fun to look at the metrics like this.
(and this brings me to a next mini-project to check which correlations are there between each metric … e. g. optimizing just for one metric … and then looking into all other metrics how they changed as well)
All reactions