mirror of
https://github.com/zama-ai/concrete.git
synced 2026-02-09 03:55:04 -05:00
chore: lowercase for filenames
This commit is contained in:
committed by
Benoit Chevallier
parent
6b3adc217f
commit
bdb1140bee
@@ -12,7 +12,7 @@ def f(x):
|
||||
return np.sin(x)
|
||||
```
|
||||
|
||||
This function fails to compile because **Concrete Framework** doesn't support floating point outputs. When you try to compile it (you might want to check [this](../basics/COMPILING_AND_EXECUTING.md) to see how you can do that), an exception will be raised and the artifacts will be exported automatically.
|
||||
This function fails to compile because **Concrete Framework** doesn't support floating point outputs. When you try to compile it (you might want to check [this](../basics/compiling_and_executing.md) to see how you can do that), an exception will be raised and the artifacts will be exported automatically.
|
||||
|
||||
### environment.txt
|
||||
|
||||
@@ -226,7 +226,7 @@ This file contains information about the bounds of the final computation graph o
|
||||
%3 :: [32, 125]
|
||||
```
|
||||
|
||||
You can learn what bounds are [here](../../dev/explanation/TERMINOLOGY_AND_STRUCTURE.md).
|
||||
You can learn what bounds are [here](../../dev/explanation/terminology_and_structure.md).
|
||||
|
||||
### mlir.txt
|
||||
|
||||
@@ -245,4 +245,4 @@ module {
|
||||
|
||||
```
|
||||
|
||||
You can learn more about MLIR [here](../../dev/explanation/MLIR.md).
|
||||
You can learn more about MLIR [here](../../dev/explanation/mlir.md).
|
||||
@@ -4,9 +4,9 @@ Tutorial
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
COMPILING_TORCH_MODEL.md
|
||||
TABLE_LOOKUP.md
|
||||
WORKING_WITH_FLOATING_POINTS.md
|
||||
INDEXING.md
|
||||
MACHINE_LEARNING_TOOLS.md
|
||||
COMPILATION_ARTIFACTS.md
|
||||
compiling_torch_model.md
|
||||
table_lookup.md
|
||||
working_with_floating_points.md
|
||||
indexing.md
|
||||
machine_learning_tools.md
|
||||
compilation_artifacts.md
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Table Lookup
|
||||
|
||||
In this tutorial, we are going to go over the ways to perform direct table lookups in **Concrete Framework**. Please read [Compiling and Executing](../basics/COMPILING_AND_EXECUTING.md) before reading further to see how you can compile the functions below.
|
||||
In this tutorial, we are going to go over the ways to perform direct table lookups in **Concrete Framework**. Please read [Compiling and Executing](../basics/compiling_and_executing.md) before reading further to see how you can compile the functions below.
|
||||
|
||||
## Direct table lookup
|
||||
|
||||
@@ -78,7 +78,7 @@ Basically, we applied `squared` table to the first column and `cubed` to the sec
|
||||
|
||||
## Fused table lookup
|
||||
|
||||
Direct tables are tedious to prepare by hand. When possible, **Concrete Framework** fuses the floating point operations into table lookups automatically. There are some limitations on fusing operations, which you can learn more about on the next tutorial, [Working With Floating Points](./WORKING_WITH_FLOATING_POINTS.md).
|
||||
Direct tables are tedious to prepare by hand. When possible, **Concrete Framework** fuses the floating point operations into table lookups automatically. There are some limitations on fusing operations, which you can learn more about on the next tutorial, [Working With Floating Points](./working_with_floating_points.md).
|
||||
|
||||
Here is an example function that results in fused table lookup:
|
||||
|
||||
@@ -26,7 +26,7 @@ assert circuit.run(60) == f(60)
|
||||
print("All good!")
|
||||
```
|
||||
|
||||
One can look to [numpy supported functions](../howto/NUMPY_SUPPORT.md) for information about possible float operations.
|
||||
One can look to [numpy supported functions](../howto/numpy_support.md) for information about possible float operations.
|
||||
|
||||
|
||||
## Limitations
|
||||
@@ -37,4 +37,4 @@ This biggest one is that, because floating point operations are fused into table
|
||||
|
||||
To give a precise example, `100 - np.fabs(50 * (np.sin(x) + np.sin(y)))` cannot be compiled because the floating point part depends on both `x` and `y` (i.e., it cannot be rewritten in the form `100 - table[z]` for a `z` that could be computed easily from `x` and `y`).
|
||||
|
||||
To dive into implementation details, you may refer to [Fusing Floating Point Operations](../../dev/explanation/FLOAT-FUSING.md) document.
|
||||
To dive into implementation details, you may refer to [Fusing Floating Point Operations](../../dev/explanation/float-fusing.md) document.
|
||||
Reference in New Issue
Block a user