move SDK
#23
by JaredforReal - opened
README.md
CHANGED
|
@@ -59,6 +59,10 @@ For speed, we compared different OCR methods under identical hardware and testin
|
|
| 59 |
|
| 60 |
## Usage
|
| 61 |
|
|
|
|
|
|
|
|
|
|
|
|
|
| 62 |
### vLLM
|
| 63 |
|
| 64 |
1. run
|
|
@@ -200,9 +204,6 @@ GLM-OCR currently supports two types of prompt scenarios:
|
|
| 200 |
|
| 201 |
⚠️ Note: When using information extraction, the output must strictly adhere to the defined JSON schema to ensure downstream processing compatibility.
|
| 202 |
|
| 203 |
-
## GLM-OCR SDK
|
| 204 |
-
|
| 205 |
-
We provide an easy-to-use SDK for using GLM-OCR more efficiently and conveniently. please check our [github](https://github.com/zai-org/GLM-OCR) to get more detail.
|
| 206 |
|
| 207 |
## Acknowledgement
|
| 208 |
|
|
|
|
| 59 |
|
| 60 |
## Usage
|
| 61 |
|
| 62 |
+
## GLM-OCR SDK
|
| 63 |
+
|
| 64 |
+
We provide an easy-to-use SDK for using GLM-OCR more efficiently and conveniently. please check our [github](https://github.com/zai-org/GLM-OCR) to get more detail.
|
| 65 |
+
|
| 66 |
### vLLM
|
| 67 |
|
| 68 |
1. run
|
|
|
|
| 204 |
|
| 205 |
⚠️ Note: When using information extraction, the output must strictly adhere to the defined JSON schema to ensure downstream processing compatibility.
|
| 206 |
|
|
|
|
|
|
|
|
|
|
| 207 |
|
| 208 |
## Acknowledgement
|
| 209 |
|