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

docs: Update terminology_and_structure.md

Browse Source
This commit is contained in:
Jeremy Bradley-Silverio Donato
2022-01-06 17:38:31 +01:00
committed by Benoit Chevallier
parent 5abaf5dce6
commit ddf8c830d7
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/dev/explanation/terminology_and_structure.md
View File

@@ -8,7 +8,7 @@ In this section we will go over some terms that we use throughout the project.
- a data structure to represent a calculation
- basically a computation graph where nodes are either inputs or operations on other nodes
- tracing
- it is our technique to take directly a plain numpy function from a user and deduce its intermediate representation in a painless way for the user
- it is our technique to directly take a plain numpy function from a user and deduce its intermediate representation in a painless way for the user
- bounds
- before intermediate representation is sent to the compiler, we need to know which node will output which type (e.g., uint3 vs uint5)
- there are several ways to do this but the simplest one is to evaluate the intermediate representation with all combinations of inputs and remember the maximum and the minimum values for each node, which is what we call bounds, and bounds can be used to determine the appropriate type for each node