2e4c76a257
feat: Changed flag to support negative value comparisons
2022-04-11 13:40:51 -04:00
a15c573f94
feat: Added OpenPhil 2018 AI risk grants
2022-04-08 16:26:24 -04:00
47a39af37e
tweak: Added reminder to write name
...
Also removed old unnecessary file.
2022-03-07 14:15:04 -05:00
8ce1a4a857
feat: Add visualizations.
2022-02-08 19:08:35 -05:00
f50fbf3d26
feat: Add results
2022-02-08 18:26:12 -05:00
c8cd6d8ce1
feat: align graph
2022-02-08 17:44:59 -05:00
b52ddbcfdf
feat: Propagate squiggleString
2022-02-08 16:26:15 -05:00
f8fafb837f
fix: cleanup
2022-01-31 17:39:36 -05:00
bf400502e5
feat: Show squiggle function on the graph
2022-01-31 17:30:26 -05:00
21fbab054c
fix: cleanup
2022-01-31 17:09:46 -05:00
404c720b35
feat: Allow for squiggle/guesstimate type inputs
2022-01-31 16:59:14 -05:00
87722e5ae1
chore: Refactor to refer to an input box rather than to a slider which no longer exists
2022-01-31 16:19:22 -05:00
b86deafefd
chore: Switch formatter.
2022-01-30 10:29:45 -05:00
bd5bdb9cd0
fix: Pander to human biases.
...
The expected number of steps is less than the
true number half the time. This confuses users.
Also some formatting.
2022-01-30 10:26:05 -05:00
ec50da23f1
fix: shorter table text
2022-01-29 18:03:22 -05:00
bb72e9831a
fix: Change text to point out it's the geometric mean.
2022-01-29 18:00:18 -05:00
fc91cdd2dd
fix: Make geom mean robust to low numbers by adding logs rather than multiplying small numbers. fix display of the number 1, which wasn't in any of the cases.
2022-01-29 17:45:23 -05:00
5ec31fa365
fix: Formatting + avg => geomMean
2022-01-29 16:06:16 -05:00
e610d798d3
fix: install netlify plugin
2022-01-28 15:51:29 -05:00
f47cf4ca69
fix: double definition bug
2022-01-28 15:21:30 -05:00
216f704232
feat: comparison changer
2022-01-28 15:09:41 -05:00
c7ae6d6586
feat: Working implementation of a comparisons changer
2022-01-28 13:48:47 -05:00
dfa0a38a29
feat: Changes in preparation for being able to change comparisons
2022-01-28 12:50:45 -05:00
3f0b918725
fix: Point app to personal server...
...
rather than to unreliable heroku server.
2021-12-10 00:33:04 +01:00
fa45832cde
fix: Move next verstion to 'latest'
2021-12-08 17:07:40 +01:00
f48d9a838d
fix: regress next version
2021-12-08 16:55:24 +01:00
41872fe07c
fix: Move next version to '@latest'
...
Trying to fix a netlify issue.
2021-12-08 16:51:27 +01:00
5de6a18e10
fix: Kill submit button once end is reached
2021-12-08 16:46:17 +01:00
9a22936ed7
fix: Udpated next to non-vulnerable version
2021-12-08 16:15:46 +01:00
e92f473015
fix: force netlify rebuild
2021-12-08 14:01:59 +01:00
a556eef732
tweak: Re-enable connection to mongo
2021-12-08 13:53:47 +01:00
d2f1d8dd50
fix: munging around with tailwinds configuration
2021-12-08 13:49:29 +01:00
5175b9c097
fix: Munging around with tailwind configs
2021-12-08 13:16:56 +01:00
c9bc44d7e5
fix: Fixed tailwinds
...
Moved tailwinds out of devDependencies and into normal dependencies
I am hoping this will fix the display in the netlify nextjs deployment
2021-12-08 12:59:17 +01:00
849a09207e
chore: Refactored and added comments
2021-12-08 12:35:18 +01:00
3d6a544a72
feat: Refactored to avoid useState in lib/findPaths.js
...
Note: This is important because it allows for restarting
the utility-function extractor. It also makes for code
which is more understandable.
2021-12-08 11:56:20 +01:00
958a2e366f
tweak: Moved state variable to comparisonView body
2021-12-08 11:34:28 +01:00
f134df4b0a
tweak: Extracted some buildRow functionality to its own function
...
Note: More difficult than it sounds given the constraint
that I want to preserve functionality.
2021-12-08 11:30:13 +01:00
f82043d24a
tweak: Small convenience fixes
2021-12-08 11:20:03 +01:00
22bb8610e1
0.6.1
2021-12-08 00:45:04 +01:00
ed59faafe1
tweak: Asynchronous refactoring
2021-12-08 00:44:55 +01:00
b99aa05318
0.6.0
2021-12-07 23:46:26 +01:00
54111831ca
feat: Implemented O(n) => O(log2(n)) speedup.
2021-12-07 23:45:55 +01:00
74d1f2be23
feat: Produce an O(n) to O(log2(n)) improvement in findPaths
...
Details: The findPathsInner function in lib/findPaths.js is too
expensive, and has a tendency to throw "too much recursion" errors.
However, it can be optimized. In particular, instead of just
going through all paths, we could go in the paths in the
right direction.
Note that: The current improvements don't do that yet. I was trying
to do that at the findDistance level, but I was being dumb.
2021-12-07 20:45:19 +01:00
f8791450a2
0.5.0
2021-12-07 18:41:57 +01:00
5f0cb26db0
fix: Too much recursion error + make sure mongo request goes through.
...
Too much recursion error: Use a simpler table
Make sure mongo request goes through:
- Do it before the computation +
- + put the computation inside a timeout.
2021-12-07 18:40:17 +01:00
760baa30a9
tweak: prepare for refactor
2021-12-07 16:53:44 +01:00
300806112c
tweak: prepare for refactor
2021-12-07 16:52:56 +01:00
ad66c33eb8
fix: Updated caniuse lite
2021-12-07 16:49:07 +01:00
2b9ce6e142
Change expected/max calculation when changing the dataset
2021-11-28 15:46:54 +00:00
