Configure
Behavior of Concrete Numpy can be customized using Configuration
s:
Alternatively, you can overwrite individual options as kwargs to compile
method:
Or you can combine both:
Additional kwarg to compile
function have higher precedence. So if you set an option in both configuration
and in compile
method, the value in the compile
method will be used.
Options
show_graph: bool = False
Whether to print computation graph during compilation.
show_mlir: bool = False
Whether to print MLIR during compilation.
verbose: bool = False
Whether to print computation graph and MLIR during compilation.
dump_artifacts_on_unexpected_failures: bool = True
Whether to export debugging artifacts automatically on compilation failures.
p_error: float = 0.000063342483999973
Error probability for table lookups.
jit: bool = False
Whether to use JIT compilation.
loop_parallelize: bool = True
Whether to enable loop parallelization in the compiler.
dataflow_parallelize: bool = False
Whether to enable dataflow parallelization in the compiler.
auto_parallelize: bool = False
Whether to enable auto parallelization in the compiler.
enable_unsafe_features: bool = False
Whether to enable unsage features.
virtual: bool = False (Unsafe)
Whether to create a virtual circuit.
use_insecure_key_cache: bool = False (Unsafe)
Whether to use the insecure key cache.
insecure_key_cache_location: Optional[Union[Path, str]] = None
Location of insecure key cache.
Last updated