You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 31, 2023. It is now read-only.
For each parameter we have to pick a number for, we should have a document that describes the parameter, what it affects, and what attacks we are protecting against in picking a 'correct' value (aka, what could go wrong if we pick the wrong value)
The text was updated successfully, but these errors were encountered:
Let's do this in a principled way and ensure that:
each such document has a stable URI
each such parameter has a name which eventually corresponds exactly to a relevant übercalc parameter
supporting document URIs are referenced directly in übercalc
Based on discussion with @sternhenri, he may choose to use Observable calculators as document. If the above are followed, this could help establish a pattern for solidifying the relationship between übercalc and such documentation. This can be developed in a number of ways over time.
For each parameter we have to pick a number for, we should have a document that describes the parameter, what it affects, and what attacks we are protecting against in picking a 'correct' value (aka, what could go wrong if we pick the wrong value)
The text was updated successfully, but these errors were encountered: