# Developer Guide for Creating a New Algorithm Component¶

[中文]

## Develop an algorithm component of FATE¶

This document describes how to develop an algorithm component, which can be invoked by the FATE framework.

To develop a component, follow the below steps:

1. Define the python parameter object to be used by this component.
2. Define the meta file of the new component.
3. (Optional)Define the transfer_variable object if the component needs to perform operations of a federation.
4. Create the component which should inherit the class model_base.
5. Create the protobuf file required for saving models.
6. (Optional) If the component needs to be invoked directly through the python script, define the Pipeline component in fate_client.
7. Restart fate flow service

In the following sections we will describe the 7 steps in detail, with hetero_lr.

### Step 1. Define the python parameter object to be used by this component¶

Parameter object is the only way to pass user-define runtime parameters to the component being developed, so every component must it's own parameter object. In order to define a usable parameter object, three steps are needed.

1. Open a new python file called xxx_param.py, where xxx stands for your component's name. Place this file in the folder python/federatedm/param/. The class object defined in xxx_param.py should inherit the BaseParam class declared in python/federatedml/param/base_param.py
2. The __init__ method of your parameter class should specify all parameters that the component uses.
3. Override and implement the check interface method of BaseParam. The check method is used to validate the parameter variables.

Take hetero lr's parameter object as example, the python file is here

#### Firstly, it inherits the BaseParam class:¶

class LogisticParam(BaseParam):


#### Secondly, define all parameter variables in __init__ method:¶

def __init__(self, penalty='L2',
tol=1e-4, alpha=1.0, optimizer='rmsprop',
batch_size=-1, learning_rate=0.01, init_param=InitParam(),
max_iter=100, early_stop='diff', encrypt_param=EncryptParam(),
predict_param=PredictParam(), cv_param=CrossValidationParam(),
decay=1, decay_sqrt=True,
multi_class='ovr', validation_freqs=None, early_stopping_rounds=None,
stepwise_param=StepwiseParam(), floating_point_precision=23,
metrics=None,
use_first_metric_only=False,
callback_param=CallbackParam()
):
super(LogisticParam, self).__init__()
self.penalty = penalty
self.tol = tol
self.alpha = alpha
self.optimizer = optimizer
self.batch_size = batch_size
self.learning_rate = learning_rate
self.init_param = copy.deepcopy(init_param)
self.max_iter = max_iter
self.early_stop = early_stop
self.encrypt_param = encrypt_param
self.predict_param = copy.deepcopy(predict_param)
self.cv_param = copy.deepcopy(cv_param)
self.decay = decay
self.decay_sqrt = decay_sqrt
self.multi_class = multi_class
self.validation_freqs = validation_freqs
self.stepwise_param = copy.deepcopy(stepwise_param)
self.early_stopping_rounds = early_stopping_rounds
self.metrics = metrics or []
self.use_first_metric_only = use_first_metric_only
self.floating_point_precision = floating_point_precision
self.callback_param = copy.deepcopy(callback_param)


As the above example shows, the parameters can also be a Param class that inherit the BaseParam. The default setting of this kind of parameter is an instance of this class. Next create a deepcopy version of this instance to the class attributes. The deepcopy function is used to avoid the same pointer risk when running multiple tasks concurrently.

Once the class has been defined properly, a provided parameter parser can parse the value of each attribute recursively.

#### Thirdly, override the check interface:¶

def check(self):
descr = "logistic_param's"

if type(self.penalty).__name__ != "str":
raise ValueError(
"logistic_param's penalty {} not supported, should be str type".format(self.penalty))
else:
self.penalty = self.penalty.upper()
if self.penalty not in ['L1', 'L2', 'NONE']:
raise ValueError(
"logistic_param's penalty not supported, penalty should be 'L1', 'L2' or 'none'")

if type(self.eps).__name__ != "float":
raise ValueError(
"logistic_param's eps {} not supported, should be float type".format(self.eps))


### Step 2. Define the meta file of the new component¶

The purpose to define the meta file is that FATE Flow uses this file to get the information on how to launch the component.

1. Define component meta python file under components, name it as xxx.py, where xxx stands for the algorithm component being developed.

2. Implement the meta file.

• inherit from ComponentMeta, and name meta with the component's name, like xxx_cpn_meta = ComponentMeta("XXX"). XXX is the module to be used in the dsl file.

  from .components import ComponentMeta
hetero_lr_cpn_meta = ComponentMeta("HeteroLR")

- use the decorator xxx_cpn_meta.bind_runner.on_$role to bind the running object to each role.$role mainly includes guest, host and arbiter. If the component uses the same running module for several roles, syntax like xxx_cpn_meta.bind_runner.on_$role1.on_$role2.on_$role3 is also supported. This function imports and returns the running object of the corresponding role. Take hetero-lr as an example, it can be found in python/federatedml/components/hetero_lr.py @hetero_lr_cpn_meta.bind_runner.on_guest def hetero_lr_runner_guest(): from federatedml.linear_model.coordinated_linear_model.logistic_regression import HeteroLRGuest return HeteroLRGuest @hetero_lr_cpn_meta.bind_runner.on_host def hetero_lr_runner_host(): from federatedml.linear_model.coordinated_linear_model.logistic_regression import HeteroLRHost return HeteroLRHost  - use the decorator xxx_cpn_meta.bind_param to bind the parameter object to the component defined in Step 1. The function imports and returns the parameter object. @hetero_lr_cpn_meta.bind_param def hetero_lr_param(): from federatedml.param.logistic_regression_param import HeteroLogisticParam return HeteroLogisticParam  ### Step 3. Define the transfer variable object of this module. (Optional)¶ This step is needed only when the module is used in federated learning, where the information interaction between different parties is needed. Create a file to define transfer_class object under the folder transfer_class In this python file, you need to create a transfer_variable class which inherits BaseTransferVariables. Then, define each transfer variable as its attributes. Here is an example: from federatedml.transfer_variable.base_transfer_variable import BaseTransferVariables # noinspection PyAttributeOutsideInit class HeteroLRTransferVariable(BaseTransferVariables): def __init__(self, flowid=0): super().__init__(flowid) self.batch_data_index = self._create_variable(name='batch_data_index', src=['guest'], dst=['host']) self.batch_info = self._create_variable(name='batch_info', src=['guest'], dst=['host', 'arbiter']) self.converge_flag = self._create_variable(name='converge_flag', src=['arbiter'], dst=['host', 'guest']) self.fore_gradient = self._create_variable(name='fore_gradient', src=['guest'], dst=['host']) self.forward_hess = self._create_variable(name='forward_hess', src=['guest'], dst=['host']) self.guest_gradient = self._create_variable(name='guest_gradient', src=['guest'], dst=['arbiter']) self.guest_hess_vector = self._create_variable(name='guest_hess_vector', src=['guest'], dst=['arbiter']) self.guest_optim_gradient = self._create_variable(name='guest_optim_gradient', src=['arbiter'], dst=['guest']) self.host_forward_dict = self._create_variable(name='host_forward_dict', src=['host'], dst=['guest']) self.host_gradient = self._create_variable(name='host_gradient', src=['host'], dst=['arbiter']) self.host_hess_vector = self._create_variable(name='host_hess_vector', src=['host'], dst=['arbiter']) self.host_loss_regular = self._create_variable(name='host_loss_regular', src=['host'], dst=['guest']) self.host_optim_gradient = self._create_variable(name='host_optim_gradient', src=['arbiter'], dst=['host']) self.host_prob = self._create_variable(name='host_prob', src=['host'], dst=['guest']) self.host_sqn_forwards = self._create_variable(name='host_sqn_forwards', src=['host'], dst=['guest']) self.loss = self._create_variable(name='loss', src=['guest'], dst=['arbiter']) self.loss_intermediate = self._create_variable(name='loss_intermediate', src=['host'], dst=['guest']) self.paillier_pubkey = self._create_variable(name='paillier_pubkey', src=['arbiter'], dst=['host', 'guest']) self.sqn_sample_index = self._create_variable(name='sqn_sample_index', src=['guest'], dst=['host']) self.use_async = self._create_variable(name='use_async', src=['guest'], dst=['host'])  Among them, the properties that need to be set are: - name a string representing the variable name • src a list containing the combination of guest, host, arbiter. It states where the interactive information to be sent from. • dst a list containing the combination of guest, host, arbiter. It defines where the interactive information to be sent to. ### Step 4. Create the component which inherits the class model_base¶ The rule of running a module with fate_flow_client is as follows: 1. Retrieves component registration from database and finds the running object of each role. 2. Initializes the running object of every party. 3. Calls the fit method of the running object. 4. Calls the save_data method if needed. 5. Calls the export_model method if needed. In this section, we describe how to do Step 2-5. Many common interfaces are provided in python/federatedml/model_base.py • Override __init__ interface Specify the class of model parameter which is already defined in Step 1. Take hetero_lr_base.py as an example, the last line specifies the parameter class of the your model.  def __init__(self): super().__init__() self.model_name = 'HeteroLogisticRegression' self.model_param_name = 'HeteroLogisticRegressionParam' self.model_meta_name = 'HeteroLogisticRegressionMeta' self.mode = consts.HETERO self.aggregator = None self.cipher = None self.batch_generator = None self.gradient_loss_operator = None self.converge_procedure = None self.model_param = HeteroLogisticParam()  Note: This step is mandatory. If you do not assign the vale of self.model_param, you will not be able to access the value of the model parameter in function _init_model(self, params). • Override fit interface if needed The fit method holds the form as follows. def fit(self, train_data, validate_data):  Both train_data and validate_data (optional) are Tables from upstream components(DataTransform for example). The fit method is the entry point to launch the training of the modeling component or the feature engineering component. When starting a training task, this method will be called by model_base automatically. • Override the predict interface if needed The predict method holds the form of following. def predict(self, data_inst):  data_inst is a DTable. Similar to fit function, you can define the prediction procedure in the predict function for different roles. When starting a prediction task, this function will be called by model_base automatically. Meanwhile, in a training task, this function will also be called to predict training data and validation data (if exist). If you want to evaluate your prediction result via the evaluation component, it should be designed as the following format: • for the binary or multi-class classification task and the regression task, the result header should be: ["label", "predict_result", "predict_score", "predict_detail", "type"] • label: Provided label • predict_result: The prediction result. • predict_score: For a binary classification task, it is the score of label "1". For a multi-class classification, it is the score of the label with the highest probability. For a regression task, it is the same as the predict_result. • predict_detail: For a classification task, it contains the scores of each class. For a regression task, it is the predict_result. • type: The source of you input data, eg. train or test. It will be added by model_base automatically. • There are two Table return in a clustering task. The format of the first Table: ["cluster_sample_count", "cluster_inner_dist", "inter_cluster_dist"] • cluster_sample_count: The sample count of each cluster. • cluster_inner_dist: The inner(intra)-distance of each cluster. • inter_cluster_dist: The inter-distance between clusters. The format of the second Table:["predicted_cluster_index", "distance"] • predicted_cluster_index: Your predict label • distance: The distance between each sample to its center point. • Override transform interface if needed The transform function holds the following form. def transform(self, data_inst):  This function is used for feature-engineering components in prediction tasks. • Define your save_data interface so that fate-flow can obtain output data via this interface when it is needed. def save_data(self): return self.data_output  ### Step 5. Define the protobuf file required for model saving¶ #### define proto buffer¶ To use the trained model on different platforms, FATE use protobuf files to save the parameters and modeling result of a task. When developing your own module, you are supposed to create two proto files which define your model content in this folder. For more detail of protobuf, please refer to this tutorial The two proto files are 1. a file with "meta" as the suffix: Save the model result of a task. 2. a file with "param" as the suffix: Save the parameters of a task. After defining your proto files, use the script generate_py.sh to create the corresponding python file: bash generate_py.sh  #### Define export_model interface¶ Define your export_model interface so that fate-flow can obtain output model when needed. The format should be a dict contains both "Meta" and "Param" proto buffer generated. Here is an example showing how to export a model. def export_model(self): meta_obj = self._get_meta() param_obj = self._get_param() result = { self.model_meta_name: meta_obj, self.model_param_name: param_obj } return result  ### Step 6. Define Pipeline component for your module¶ Once it is wrapped into a Pipeline component, a module can be used by the FATE Pipeline API. To define a Pipeline component, follow these steps: 1. All components reside in this directory: fate_client/pipeline/component 2. Components should inherit common base class Component 3. As a good practice, components should have the same names as their corresponding modules 4. Components take in parameters during their initialization as defined in fate_client/pipeline/param, where a BaseParam and consts file are provided 5. Set attributes of the component input and output, including whether the module has output model, or/and the type of data output('single' vs. 'multi') Then you may use Pipeline to construct and initiate a job with the newly defined component. For the guide on Pipeline usage, please refer to fate_client/pipeline. ### Step 7. Restart fate flow service¶ When the above development steps are completed, the fate flow service needs to be restarted, otherwise the subsequent submission tasks may report some errors such as "the provider of the new component cannot be found". The fate flow service can also be started in debug mode, the start method: "python fate_flow_server.py --debug", The debug mode allows the modified code to take effect without restarting. ## Start a modeling task¶ After developing the component, you can launch a modeling task. The below section describes a simple example. ### 1. Upload data¶ Before starting a task, you need to load data from all the data providers. To do that, a configuration of the load_file needs to be prepared. Then run the following command: flow data upload -c upload_data.json  Note: This step is needed on every node which provides the training data (i.e. Guest and Host). ### 2. Start your modeling task¶ In this step, the dsl config file and the component config file should be prepared. Please make sure that the table_name and namespace in the conf file match with upload_data conf. Then run the following command: flow job submit -d${your_dsl_file.json} -c ${your_component_conf_json}  If you have defined Pipeline component for your module, you can also make a pipeline script and start your task by: python${your_pipeline.py}


### 3. Check log files¶

Now you can check out the training log in the path: $PROJECT_BASE/logs/${your jobid}

For more detail information about dsl config file and parameter config file, please refer to the directory examples/dsl/v2 .

Last update: 2022-08-26