federatedai / fate-board Goto Github PK

1. The last round of bug repair;

2. Secure Boost tree zooming method optimization, display content modification;

3. Selection feature selection (from chart to table) to separate guest and host data;

4. Redraw dashboard;

5. Running, dashboard, detail pages polling for query data;

6. Workflow is displayed according to the role: guest, host or arbiter are grayed out in the workflow, and component names are not displayed.

update service.sh

Extend the waiting time from 8s to 20s

Deploy FATE-Board on K8s, use ingress-nginx for TLS certificate termination.

When I open fateboard's URL, I got some error information.

ERROR: 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.

Hi, I'd like to report a bug.

In

This only works fine in the standalone deployment. (That is, the parent directory of the fate-flow and the fate-board is the same),
In the following situation, it will trigger a File doesn't exist! exception when the user wants to download the dsl/runtime conf in the job details dashboard. Please see the pic follows.

1. In the kube-fate docker-compose deployment: the fate-flow and fate-board are not in the same container.
2. In the standalone deployment: If the user runs the spring-boot application in another directory(not the /standalone_fate_install_1.7.0_release/fateboard directory )

Since the dsl and the runtime conf have already been stored in the table t_job, I'd like to suggest getting them from the database. If this makes scene, May I submit a PR?

1.support PSI display in evaluation component
2.Support confusion matrix display

Displays the anonymous corresponding to the field

update dependency version for security

我们在自己的系统内调用fate-board接口，fate-board版本为1.5.0 浏览器报跨域错误。
跨域报错信息如下：
/job/query/page/new' from origin 'null' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
请问这个如何解决呢，我看了下fate-board代码，也没找到相关的跨域配置呢。
谢谢

The presentation is similar to SSHE LR component

update to new version 1.6.0

Optimize the display

i just download fateboard from github.but my echart can't work. Is the newest version in master branch?

Optimization for wss protocal

Structural arrangement and rewrite partial component

There are new functions of 1.4.0 version:
1.Pearson correlation
2.Homo secureboost
3.GLM-stepwise
4.Hetero LR : one_vs_rest

Can I modify the default port of fate-board (8080) to something else?

e.g. 80

support more display of algorithm components

• Add model visualization of new algorithm components：Hetero/Homo Data Split, Table reader, Data Statistic, PSI，Hetero Fastsecureboost，Hetero Kmeans

  • Hetero/Homo Data Split：Visualize dataset split results (training/validate/test)
  • Table reader：read in the original modeling data and output data overview
  • Data Statistic：display statistical indicators of each variable
  • PSI：PSI detailed data display for each variable
  • Hetero Fastsecureboost：fast secureboost model visualization in layered-mode and mixed-mode
  • Hetero Kmeans：visualization of sample clustering results

• Feature selection：supports connection with the output models of Data Statistic, PSI, SecureBoost, and other components for feature selection

• Feature binning：Support binning visualization without calculating the iv value, and increase the display of the number of bins

• Evaluation：Supports visualization of cluster model evaluation results

• Hetero secureboost：Supports visualization of Completely SecureBoost models

• Evaluation：Supports visualization of cluster model evaluation results

• Support downloading model and data of algorithm components from FATEBoard（Feature Binning，Feature Selection，Secureboost，LR，Evaluation）

• The page supports partial data refresh and global data refresh to update the data in the iteration

• Support retry for failed or canceled job

• Data input port of the component supports separate access according to train/validate

• Job list optimization：search, filter, and sort optimization

• Significantly improve page fluency when the amount of data is large

• Optimize the log pull method and improve efficiency

• Enhance safety check

• Interface optimization

• Data decoupling：separate the relationship between presentation, interaction, and data of the page

• Interaction logic decoupling：Disassembly and refinement of complex functional logic

• Improve the cohesion and reusability of components and tools

Update display for leaf in the tree view.

• Modify the display of DAG diagram

Hi, I wanted to know is there an English version available for Federated AI Ecosystem white paper?

I run on a standalone mode, i able to run jobs successfully. Log are showing up in the fateboard, but i can't see the dashboard diagrams. There is no error in browser console. Any idea why?

Add union component which support data merging

Update source code of front-end

单机版sqlite ，登录界面的用户名密码是什么呀？

Is it possible to submit new job from the board, and if so what is required ?

Update the condition to pull logs.

The impact module includes DAG and PANEL

1.Update the transparency effect of tree.
2.Add tags for ks curve line

It seems in recently updates only the built version of frontend code has been updated in FATE-Board/src/main/resources/static/ and the source code in FATE-Board/static/ hasn't been updated for a while.

There has no data-output port in data-statistic componet

Password is unencrypted when sign in.

1. Format component parameters and truncate component decimal point;

2. Secure Boost-tree graph;

3. Secure Boost-the importance of features;

4. Search and sort the job table page;

5. Waiting task cancel;

6. Workflow is differentiated by roles: guest, host or arbiter components that are not running by their own side are ashed on the workflow, and the name of the component is not displayed;

7. Component shape, running state (success or failure), dynamic effect of running state change;

8. Input and output ports of components: separate data from model input and output.

when i start fateboard on standalone mode i get below error

fateboard could be deploy with following directory structure:

fateboard/
  fateboard.jar
  conf/
    application.properties
    ssh.properties

It maybe a good idea to generate this structure in maven package phase by simply add this configuration to pom.xml:

<plugins>
...
    <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-dependency-plugin</artifactId>
        <version>2.10</version>
        <executions>
            <execution>
                <id>copy-dependencies</id>
                <phase>package</phase>
                <goals>
                    <goal>copy-dependencies</goal>
                </goals>
                <configuration>
                    <outputDirectory>${project.build.directory}/lib</outputDirectory>
                </configuration>
            </execution>
            <!-- code added start -->
            <execution>
                <id>copy-packaged</id>
                <phase>package</phase>
                <goals>
                    <goal>copy</goal>
                </goals>
                <configuration>
                    <artifactItems>
                        <artifactItem>
                            <groupId>${project.groupId}</groupId>
                            <artifactId>${project.artifactId}</artifactId>
                            <version>${project.version}</version>
                            <type>${project.packaging}</type>
                            <destFileName>fateboard.jar</destFileName>
                        </artifactItem>
                    </artifactItems>
                    <outputDirectory>${project.build.directory}/fateboard</outputDirectory>
                </configuration>
            </execution>
        </executions>
    </plugin>
    <plugin>
        <artifactId>maven-resources-plugin</artifactId>
        <version>3.1.0</version>
        <executions>
            <execution>
                <id>copy-resources</id>
                <!-- here the phase you need -->
                <phase>package</phase>
                <goals>
                    <goal>copy-resources</goal>
                </goals>
                <configuration>
                    <outputDirectory>${basedir}/target/fateboard/conf</outputDirectory>
                    <resources>
                        <resource>
                            <directory>src/main/resources</directory>
                            <includes>
                                <include>application.properties</include>
                                <include>ssh.properties</include>
                            </includes>
                        </resource>
                    </resources>
                </configuration>
            </execution>
        </executions>
    </plugin>
    <!-- code added end -->
</plugins>

We get feteboard dir after package phase:

I notice a small problem in the fateboard of FATE 1.5.2.version
When you click into the data output of homo nn component in the board,
you can see some predict-scores are more than 1.0,
For example:
If a predict scores is '8.940696716308..e-8', you will get '8.940696' only .
Here is the picture:

Look like that it just cuts off the string according to the length.
I am not sure this problem still exists in the 1.6.x,
can someone have a check?

https://github.com/FederatedAI/FATE-Board#frequently-asked-questions

“The default log lookup path is /data/projects/fate/python/logs/.”
The new version of path is /data/projects/fate/logs/

1. New components:

• Heterogeneous feature correlation component: visualizing the correlation matrix  diagram，filtering by role or variable, and scaling of diagram
• Upload component: uploading data, and supporting for viewing data output
• Download component: downloading data, and supporting for viewing data output
• LocalBaseline component: A LR component based on Sklearn run to compare the performance  of Federated LR

2. Component optimization：

• Secureboost: Visual enhancement of secureboost tree diagrams, and support for scaling  and dragging trees
• Federated Sample: Filtering by label to display the table content
• Model output of some components supports global fuzzy search
• Model output of some components supports for table column sorting
• Model output of some components supports multi-host visualization and filtering by role,  and adds variable mapping
• Optimize cross-validation curves and loss curves  support visualization and interaction  of  large data volumes, and support for manual refresh during operation

3. Update the resources for the front-end.

4. Others:

• Job detail page redesign, and support for workflow scaling and dragging, and optimize  parameter  display
• Add job note and support for description and classification
• Log load optimization

在/fate-board/resources-front-end 目录下执行”npm run dev/build“ 命令 出错：

1. ERROR:

解决：

修改： .TTF -> .ttf

2. ERROR

解决：

修改： combination.vue -> Combination.vue

Change board version 1.2.1 to 1.3.0 to match the version for FATE.

Add parameter field display

Hi, Is it possible to add a customized prefix to the Server-side?
In our scenario, we route requests base on the URL rather than the hostname, assumes we have a gateway and two fateboard services as follows:

          ---->  fateboard1
gateway -|
          ---->  fateboard2

we use the following URLs to access fatebord1 and fateboard2 respectively：

• http://gateway.domain/fateboard1
• http://gateway.domain/fateboard2

Before forwarding the request, the gateway needs to rewrite the URL from /fateboard1 to /, and then send the request to fateboard1. However, the further requests triggered by the JS will be sent to an address without fatebord* pattern, for example, "http://gateway.domain/ssh". Resulting in the gateway can't forward this request correctly.

The ideal solution is to add a variable to the routing policy like ${prefix}/, if the prefix is empty, then the use /.
If the prefix is fateboard1, then use /fateboard1/ as the root. So that the rewrite could be avoided and further request can contain the fatebord* part.

• Update display of front-end

1.Update the transparency effect of tree.
2.Add tags for ks curve line

fix the security problem caused by druid datasource

1.Optimize discriptions for fateboard
2.Add chinese document of readme
3.Add new document of deploy

Adjust the descriptions about the command of using fateboard.