Heisenburger2000 commited on
Commit
d5ee2e0
·
verified ·
1 Parent(s): 8e88b3c

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +1 -15
README.md CHANGED
@@ -6,8 +6,6 @@
6
  [![arXiv](https://img.shields.io/badge/arXiv-2507.00087-B31B1B)](https://arxiv.org/abs/2507.00087) [![Windows Executable](https://img.shields.io/badge/Windows-GUI-green)](https://github.com/pFindStudio/pUniFind/releases) [![Bohrium](https://img.shields.io/badge/Web%20server-Bohrium%20App-00BFFF)](https://bohrium.dp.tech/apps/punifind)
7
  <!-- [![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/your-repo/pUniFind) -->
8
  <div style="text-align: center; line-height: 1.8; margin-bottom: 25px;">
9
- <a href="User_guide_chinese.md" style="margin-right: 15px;">中文用户手册</a> |
10
- <a href="User_guide.md" style="margin-left: 15px;">User Manual</a>
11
  </div>
12
 
13
 
@@ -34,22 +32,10 @@ For source code, Please see [GitHub](https://github.com/pFindStudio/pUniFind/tre
34
  - **2025/5/25** pUniFind repository Initial Release 🚀.
35
 
36
 
37
-
38
- ## 📊 Benchmark
39
- Details can be seen in our paper.
40
-
41
- ![](evaluation.png)
42
-
43
-
44
- ## 🛠️ Getting Started
45
-
46
- Please see our [user guide](User_guide.md).
47
-
48
-
49
  ## 🛠️ Technical Support
50
  Should you encounter any technical issues, suggestions, observe suboptimal performance, or identify inconsistencies between pUniFind results and our evaluation metrics, we welcome your feedback 🙏. We are looking for bad cases to further refine our model. We can improve performance in 50% of poor cases using our proprietary, complex methods, which is why we have not released them publicly. If you have any suggestions about our software, please do not hesitate to contact us. We are **actively** updating and refining our software, since the main author is **far** from graduation :(.
51
 
52
- If you encounter any issues running pUniFind, please first refer to the FAQ section in the [User Guide](User_guide.md). If your problem persists, priority support is available for user-reported issues through the following channels. We will respond to you as promptly as possible:
53
 
54
  **For technical inquiries:**
55
  1. **GitHub Issues**: [Open a new issue](https://github.com/pFindStudio/pUniFind/issues) with:
 
6
  [![arXiv](https://img.shields.io/badge/arXiv-2507.00087-B31B1B)](https://arxiv.org/abs/2507.00087) [![Windows Executable](https://img.shields.io/badge/Windows-GUI-green)](https://github.com/pFindStudio/pUniFind/releases) [![Bohrium](https://img.shields.io/badge/Web%20server-Bohrium%20App-00BFFF)](https://bohrium.dp.tech/apps/punifind)
7
  <!-- [![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/your-repo/pUniFind) -->
8
  <div style="text-align: center; line-height: 1.8; margin-bottom: 25px;">
 
 
9
  </div>
10
 
11
 
 
32
  - **2025/5/25** pUniFind repository Initial Release 🚀.
33
 
34
 
 
 
 
 
 
 
 
 
 
 
 
 
35
  ## 🛠️ Technical Support
36
  Should you encounter any technical issues, suggestions, observe suboptimal performance, or identify inconsistencies between pUniFind results and our evaluation metrics, we welcome your feedback 🙏. We are looking for bad cases to further refine our model. We can improve performance in 50% of poor cases using our proprietary, complex methods, which is why we have not released them publicly. If you have any suggestions about our software, please do not hesitate to contact us. We are **actively** updating and refining our software, since the main author is **far** from graduation :(.
37
 
38
+
39
 
40
  **For technical inquiries:**
41
  1. **GitHub Issues**: [Open a new issue](https://github.com/pFindStudio/pUniFind/issues) with: