The distribution called itself torus-ml while shipping a package directory named concrete, so the name a user installs and the name they import disagreed — and most of the tree already said torus.ml, which could not resolve against src/concrete. Moved src/concrete to src/torus and pointed the include at it. The dependency was Zama's concrete-python from their index. It is torus-fhe from ours, which is what luxfhe/torus already ships: that frontend declares torus-fhe and ships a torus/fhe module, so every 'from torus.fhe' in this tree was already naming our compiler and only the dependency lagged. Two distributions share one namespace, which is the shape the upstream this forked from used and the reason the split works: torus-fhe gives torus.fhe, torus-ml gives torus.ml. Swept every other spelling — identifiers, enum members, workflow variables, filenames, notebooks. LICENSE and NOTICE keep the upstream attribution a fork owes; the figures carry the old name in JPEG metadata a text sweep cannot reach.
1.4 KiB
Upgrading Torus ML In Your Project
This guide aims to help developers who are upgrading from older versions of Torus ML. Although we cannot cover everything, we have compiled the most important points to assist you in your transition. If you encounter any issues, please reach out through our community channels.
Upgrading to 1.0.0
Please take note of the following changes when upgrading to version 1.0.0:
-
execute_in_fheargument in.predict()methods has been replaced byfhe="disable|simulate|execute". Thedisableoption runs the model in Python, whilesimulateperforms an FHE simulation, andexecuteprovides actual FHE execution. -
encrypt_run_decryptfunction can now only be executed in FHE. For FHE simulations, please use thesimulatefunction instead. -
In some models, the
forward_fhefunction has been renamed tofhe_circuitfor consistency across all models. -
verbose_compilationparameter has been renamed toverbosein the compile functions. -
compilation_artifactsparameter has been renamed toartifacts. -
use_virtual_libparameter intorus.ml.torchhas been removed from the following functions:compile_onnx_modelcompile_torch_modelcompile_brevitas_qat_modelThis means that models are now always converted to FHE, and only FHE-friendly models can be compiled.