Visualize hierarchical estimates
Go to file
2021-12-07 16:53:44 +01:00
data feat: Refactoring to make index.js and research.js use the same function 2021-11-25 15:31:10 +00:00
lib Change expected/max calculation when changing the dataset 2021-11-28 15:46:54 +00:00
pages fix: Aesthetics 2021-11-25 15:49:58 +00:00
public MVP with just an ordering, but no quantitative estimates 2021-06-06 23:14:05 +02:00
styles Changed slider order. Inferred relative utility compared to a reference point. However, object structures used in the code remain messy 2021-06-10 21:59:48 +02:00
.gitignore feat: Added expected and maximum number of comparisons 2021-11-28 15:33:19 +00:00
package-lock.json tweak: prepare for refactor 2021-12-07 16:53:44 +01:00
package.json tweak: prepare for refactor 2021-12-07 16:53:44 +01:00
postcss.config.js MVP with just an ordering, but no quantitative estimates 2021-06-06 23:14:05 +02:00
README.md tweak: Small reorganizing 2021-11-25 11:09:17 +00:00
tailwind.config.js MVP with just an ordering, but no quantitative estimates 2021-06-06 23:14:05 +02:00

About

This repository creates a react webpage that allows to extract a utility function from possibly inconsistent binary comparisons

Object structure

The core structure is json array of objects. Only the "name" attribute is required; the (numerical) id is also internally required but it's created on the fly. The reason that ids are needed is that comparing objects is annoying.

The isReferenceValue property determines the display at the end, but it is optional.

So internally this would look like:

[
    {
        "id": 1,
        "name": "Peter Parker",
        "someOptionalKey": "...",
        "anotherMoreOptionalKey": "...",
        "isReferenceValue": true
    },
    {
        "id": 2,
        "name": "Spiderman",
        "someOptionalKey": "...",
        "anotherMoreOptionalKey": "..."
    }
]