You will see the following document variables
in all FATE Flow
documentation, with the following meanings.
FATE project
deployment directory, containing configuration, fate algorithm packages, fate clients and subsystems: bin
, conf
, examples
, fate
, fateflow
, fateboard
, eggroll
, etc.FATE
, named fate
, contains algorithm packages, clients: federatedml
, fate arch
, fate client
, usually the path is ${FATE_PROJECT_BASE}/fate
FATE Flow
, named fateflow
, containing fate flow server
, etc., usually the path is ${FATE_PROJECT_BASE}/fateflow
FATE Board
, name fateboard
, contains fateboard
, usually the path is ${FATE_PROJECT_BASE}/fateboard
EGGROLL_HOME: the deployment directory for EggRoll
, named eggroll
, containing rollsite
, clustermanager
, nodemanager
, etc., usually in ${FATE_PROJECT_BASE}/eggroll
Deploy the FATE project
with reference to the main repository FederatedAI/FATE, the main directory structure is as follows
FATE_VERSION: The version number of FATE
, e.g. 1.7.0
FATE_FLOW_VERSION: the version number of FATE Flow
, e.g. 1.7.0
version: Generally in the deployment documentation, it means the version number of FATE project
, such as 1.7.0
, 1.6.0
.
version_tag: generally in the deployment documentation, indicates the FATE project
version tag, such as release
, rc1
, rc10
component_name
: the name of the component when the task is submitted, a task can have more than one of the same component, but the component_name
is not the same, equivalent to an instance of the class
componet_module_name
: the class name of the component
model_alias
: similar to component_name
, which is the name of the output model that the user can configure inside dsl
Example.
In the figure dataio_0
is component_name
, DataIO
is componet_module_name
, dataio
is model_alias
! [](https://user-images.githubusercontent.com/1758850/124451776-52ee4500-ddb8-11eb-94f2-d43d5174ca4d.png)