svercoutere
commited on
Commit
•
3508d6a
1
Parent(s):
bd30ccf
Create README.md
Browse files
README.md
ADDED
@@ -0,0 +1,57 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
---
|
2 |
+
license: mit
|
3 |
+
language:
|
4 |
+
- nl
|
5 |
+
tags:
|
6 |
+
- abb
|
7 |
+
- agentschap binnenlands bestuur
|
8 |
+
- lblod
|
9 |
+
---
|
10 |
+
# Custum ML model for BPMN-similarity using spektral and keras.
|
11 |
+
|
12 |
+
## Overview
|
13 |
+
This project aims to create embeddings for BPMN files to facilitate tasks like search, similarity, and clustering. The embeddings capture both the semantics and structure of BPMN files, allowing for effective retrieval and comparison of similar BPMN diagrams.
|
14 |
+
|
15 |
+
## Important Note
|
16 |
+
The current model uses embeddings created by the paraphrase-multilingual-MiniLM-L12-v2 with an embedding dimension of 384. Using a different sentence-transformer will result in unexpected behavior. Ensure to use the correct sentence-transformer with the kerasEmbedder and adjust the 'dims' parameter in mu-search accordingly.
|
17 |
+
|
18 |
+
## Motivation
|
19 |
+
The goal is to:
|
20 |
+
|
21 |
+
Capture the semantics of BPMN files, making similar BPMN files have similar embeddings.
|
22 |
+
Capture the structure of BPMN files, making structurally similar BPMN files have similar embeddings.
|
23 |
+
Enable measuring the similarity between two BPMN diagrams by estimating the number of changes needed to transform one into another (trained on Minimum Edit Distance).
|
24 |
+
|
25 |
+
## Design Choices:
|
26 |
+
Preprocessing BPMN Files: Adjust the input size to fit the fixed input size of embedding models or handle large inputs by splitting them into smaller parts.
|
27 |
+
Encoding Structure: Use graph embedding techniques (e.g., GNNs, GCNs) to encode the structure of BPMN diagrams.
|
28 |
+
Graph Representation: Convert BPMN diagrams into graph representations using NetworkX.
|
29 |
+
Node and Edge Information: Extract labels and documentation fields from nodes and edges, converting them into numerical vectors using pre-trained embeddings or custom-trained embeddings.
|
30 |
+
|
31 |
+
## Current Approach:
|
32 |
+
Convert BPMN Files to Graphs: Use NetworkX to represent BPMN files as graphs.
|
33 |
+
Node and Edge Embeddings: Use pre-trained embeddings to create vector representations of nodes and edges.
|
34 |
+
Graph Embedding: Use these embeddings as features for a GNN or GCN model (e.g., Spektral) to create a single embedding for each BPMN file.
|
35 |
+
|
36 |
+
## Similarity Model Specifics:
|
37 |
+
Input: two BPMN files: (Batchsize, nodes, node_features) and Adjacency matrix
|
38 |
+
Similarity Calculation: Uses precomputed embeddings and cosine similarity to rank BPMN files based on query similarity.
|
39 |
+
Efficiency: Designed to handle large volumes of BPMN files and queries efficiently.
|
40 |
+
|
41 |
+
## Shortcomings:
|
42 |
+
Data Availability: Lack of sufficient BPMN files within ABB, we trained on the data of [camunda/bpmn-for-research](https://github.com/camunda/bpmn-for-research) by converting the BPMN files to Networkx graphs and measuring the Minimum Edit Distance between random pairs.
|
43 |
+
Minimum Edit Distance: **Does this translate to perceived similarity?** It might require a different approach. Training data in the form of (BPMN, BPMN, similarity) is needed. If user interactions can be captured, this might be a better approach for gauging perceived similarity or general 'useful' similarity.
|
44 |
+
|
45 |
+
## Future Steps:
|
46 |
+
Gather more BPMN files from the correct domain (OPH).
|
47 |
+
Train custom text embeddings for nodes and edges (e.g., using [robbert-2023-dutch-base-abb](https://huggingface.co/svercoutere/robbert-2023-dutch-base-abb)).
|
48 |
+
Validate and refine the current model with new data.
|
49 |
+
Potentially merge the graph and text models into a unified architecture.
|
50 |
+
|
51 |
+
### Suggestions:
|
52 |
+
Data Collection: Store search results and user interactions anonymously to gather diverse query data.
|
53 |
+
User Interaction Analysis: Use interaction data to train models for better search result ranking.
|
54 |
+
|
55 |
+
### Requirements for future steps:
|
56 |
+
A large and varied dataset of BPMN files to ensure the model generalizes well.
|
57 |
+
Real user interactions (recommendation interface based on BPMN-BPMN: user uploads file -> what suggestion did he interact with) to validate and improve the model's effectiveness.
|