github/concrete
1
1
Fork 0
mirror of https://github.com/zama-ai/concrete.git synced 2026-04-17 03:00:54 -04:00
Code Issues Packages Projects Releases Wiki Activity

docs(frontend): fix gitbook link error

Browse Source
This commit is contained in:
aquint-zama
2024-06-21 11:51:39 +02:00
parent 3a884f5c9b
commit e441839dd9
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/dev/compilation/optimizer.md
View File

@@ -40,7 +40,7 @@ In more complex cases, the optimizer iteratively performs an exhaustive search,
## How can I determine, understand, and explore crypto-parameters
One can have a look at [reference crypto-parameters](../../../compilers/concrete-optimizer/v0-parameters/ref/v0_last_128) for each security level (but for a given correctness). This provides insight between the calcululs content (i.e. maximum precision, maximum dot 2-norm, etc.,) and the cost.
One can have a look at [reference crypto-parameters](https://raw.githubusercontent.com/zama-ai/concrete/release/2.2.x/compilers/concrete-optimizer/v0-parameters/ref/v0_last_128) for each security level (but for a given correctness). This provides insight between the calcululs content (i.e. maximum precision, maximum dot 2-norm, etc.,) and the cost.
Then one can manually explore crypto-parameters space using a [CLI tool](../../../compilers/concrete-optimizer/v0-parameters/README.md).