Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents


Introduction

All test results and logs have been pushed to Akraino NEXUS:

https://nexus.akraino.org/content/sites/logs/fate/job/Fate_test/15/

Running Unit tests

A script to run all the unittests has been provided in ./python/federatedml/test folder.

...

All the unit tests shall pass if FATE is installed properly.


Pipeline Examples


Introduction

We provide some example scripts of running FATE jobs with FATE-Pipeline.

...

  1. (optional) create virtual env

    python -m venv venv
    source venv/bin/activate
    pip install -U pip

  2. install fate_client

    # this step installs FATE-Pipeline, FATE-Flow CLI v2, and FATE-Flow SDK
    pip install fate_client
    pipeline init --help
  3. configure server information

    # configure by conf file
    pipeline init -c pipeline/config.yaml
    # alternatively, input real ip address and port info to initialize pipeline
    # optionally, set log directory for Pipeline
    pipeline init --ip 127.0.0.1 --port 9380 --log-directory ./logs
  4. upload data with FATE-Pipeline

    #  upload demo data to FATE data storage, optionally provide path to where deployed examples/data locates
    
    python demo/pipeline-upload.py --base /data/projects/fate

    If upload job is invoked correctly, job id will be printed to terminal and an upload bar is shown. If FATE-Board is available, job progress can be monitored on Board as well.

    UPLOADING:||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||100.00%
    2020-11-02 15:37:01.030 | INFO     | pipeline.utils.invoker.job_submitter:monitor_job_status:121 - Job id is 2020110215370091210977
    Job is still waiting, time elapse: 0:00:01
    Running component upload_0, time elapse: 0:00:09
    2020-11-02 15:37:13.410 | INFO     | pipeline.utils.invoker.job_submitter:monitor_job_status:129 - Job is success!!! Job id is 2020110215370091210977
    

...