github/concrete
1
1
Fork 0
mirror of https://github.com/zama-ai/concrete.git synced 2026-02-08 19:44:57 -05:00
Code Issues Packages Projects Releases Wiki Activity

chore: test slow compiler

Browse Source 
- fix CI scripts for the current compiler releases
- add keycache system
This commit is contained in:
IceTDrinker
2021-12-13 13:09:39 +00:00
committed by Zama Bot
parent ad2cbf4842
commit 31ae92a5db
21 changed files with 291 additions and 103 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/user/tutorial/compilation_artifacts.md
View File

@@ -6,7 +6,7 @@ In this tutorial, we are going to go over the artifact system, which is designed
In case of compilation failures, artifacts are exported automatically to `.artifacts` directory under the working directory. Let's intentionally create a compilation failure and show what kinds of things are exported.
<!--python-test:skip-->
<!--pytest-codeblocks:skip-->
```python
def f(x):
return np.sin(x)

16
docs/user/tutorial/table_lookup.md
View File

@@ -21,7 +21,7 @@ where
results in
<!--python-test:skip-->
<!--pytest-codeblocks:skip-->
```python
circuit.run(0) == 2
circuit.run(1) == 1
@@ -35,7 +35,7 @@ Moreover, direct lookup tables can be used with tensors where the same table loo
results in
<!--python-test:skip-->
<!--pytest-codeblocks:skip-->
```python
input = np.array([[0, 1, 3], [2, 3, 1]], dtype=np.uint8)
circuit.run(input) == [[2, 1, 0], [3, 0, 1]]
@@ -45,7 +45,7 @@ circuit.run(input) == [[2, 1, 0], [3, 0, 1]]
Sometimes you may want to apply a different lookup table to each value in a tensor. That's where direct multi lookup table becomes handy. Here is how to use it:
<!--python-test:skip-->
<!--pytest-codeblocks:skip-->
```python
import concrete.numpy as hnp
@@ -68,7 +68,7 @@ where
results in
<!--python-test:skip-->
<!--pytest-codeblocks:skip-->
```python
input = np.array([[2, 3], [1, 2], [3, 0]], dtype=np.uint8)
circuit.run(input) == [[4, 27], [1, 8], [9, 0]]
@@ -82,7 +82,7 @@ Direct tables are tedious to prepare by hand. When possible, **Concrete Framewor
Here is an example function that results in fused table lookup:
<!--python-test:skip-->
<!--pytest-codeblocks:skip-->
```python
def f(x):
return 127 - (50 * (np.sin(x) + 1)).astype(np.uint32) # astype is to go back to integer world
@@ -94,7 +94,7 @@ where
results in
<!--python-test:skip-->
<!--pytest-codeblocks:skip-->
```python
circuit.run(0) == 77
circuit.run(1) == 35
@@ -116,14 +116,14 @@ and after floating point operations are fused, we get the following operation gr
Internally, it uses the following lookup table
<!--python-test:skip-->
<!--pytest-codeblocks:skip-->
```python
table = hnp.LookupTable([50, 92, 95, 57, 12, 2, 36, 82])
```
which is calculated by:
<!--python-test:skip-->
<!--pytest-codeblocks:skip-->
```python
[(50 * (np.sin(x) + 1)).astype(np.uint32) for x in range(2 ** 3)]
```