Update README.md
Browse files
README.md
CHANGED
|
@@ -29,10 +29,12 @@ To construct a specialized knowledge database for emerging contaminants usage cl
|
|
| 29 |
1. Install Navicat on your computer and upload the **invitrodb_v4_3.sql** and **pubchemlite_exposomics_20251226.sql** databases.
|
| 30 |
2. Deploy Docker and Dify. Set the Docker engine according to **dockerengine_setting.txt**.
|
| 31 |
3. Create a custom tool named **sql_executor_pubchemlite_invitrodb_en** on the Dify platform. The detailed information for the schema tool is stored in **schema_tool.txt**. Note that you need to modify the URL address to your local address.
|
| 32 |
-
4.
|
| 33 |
-
5.
|
| 34 |
-
6.
|
| 35 |
-
7.
|
|
|
|
|
|
|
| 36 |
|
| 37 |
## System Architecture & Components
|
| 38 |
### Core Databases Deployment
|
|
@@ -56,7 +58,7 @@ The system integrates three core databases with differentiated deployment strate
|
|
| 56 |
2. Import dataset (50,000+ chemicals with IUPAC names and categories from the Norman database).
|
| 57 |
3. Connect the dataset to a FastGPT application and configure prompts (consistent with Few-shot prompts).
|
| 58 |
4. Publish the application and export the API key for subsequent calls.
|
| 59 |
-
- **
|
| 60 |
- Resolves API incompatibility between FastGPT and Dify.
|
| 61 |
- Deployment steps: Create `docker-compose.yml` for FDA → Run `docker-compose up -d` in the configuration file directory to deploy the plugin.
|
| 62 |
- **Dify External Knowledge Base Connection**: Link the trained FastGPT knowledge base to Dify by importing the FastGPT API key and knowledge base ID.
|
|
|
|
| 29 |
1. Install Navicat on your computer and upload the **invitrodb_v4_3.sql** and **pubchemlite_exposomics_20251226.sql** databases.
|
| 30 |
2. Deploy Docker and Dify. Set the Docker engine according to **dockerengine_setting.txt**.
|
| 31 |
3. Create a custom tool named **sql_executor_pubchemlite_invitrodb_en** on the Dify platform. The detailed information for the schema tool is stored in **schema_tool.txt**. Note that you need to modify the URL address to your local address.
|
| 32 |
+
4. Train the knowledge base on the FastGPT platform. The knowledge base file is **knowledge_database_input_iupac.csv**.
|
| 33 |
+
5. Deploy the FDA **docker-compose.yml** and import the external knowledge base into Dify.
|
| 34 |
+
6. On the Dify platform, select Import DSL File and upload the **dify_CECs_annotating.yml**.
|
| 35 |
+
7. Before using this agent, you need to run Docker and the **step1_pubchemlite_invitrodb_to_dify_en.py** code. Note that in **step1_pubchemlite_invitrodb_to_dify_en.py**, the DB_CONFIGS needs to be modified to the username and password of your local SQL database.
|
| 36 |
+
8. Once the setup is complete, you can start running.
|
| 37 |
+
9. For batch queries, you can run the mini-program **step2_CECs_annotating_agent_v1.0.py**.
|
| 38 |
|
| 39 |
## System Architecture & Components
|
| 40 |
### Core Databases Deployment
|
|
|
|
| 58 |
2. Import dataset (50,000+ chemicals with IUPAC names and categories from the Norman database).
|
| 59 |
3. Connect the dataset to a FastGPT application and configure prompts (consistent with Few-shot prompts).
|
| 60 |
4. Publish the application and export the API key for subsequent calls.
|
| 61 |
+
- **FastGPT-Dify Adaptor (FDA) Plugin**
|
| 62 |
- Resolves API incompatibility between FastGPT and Dify.
|
| 63 |
- Deployment steps: Create `docker-compose.yml` for FDA → Run `docker-compose up -d` in the configuration file directory to deploy the plugin.
|
| 64 |
- **Dify External Knowledge Base Connection**: Link the trained FastGPT knowledge base to Dify by importing the FastGPT API key and knowledge base ID.
|