Update README.md
Browse files
README.md
CHANGED
@@ -21,11 +21,11 @@ For fast inference use of this model, we would recommend using the 'quantized to
|
|
21 |
|
22 |
## Usage Tips
|
23 |
|
24 |
-
-- Automatic (ast.literal_eval) conversion of the llm output to a python list is often complicated by the presence of '"' (ascii 34 double quotes) and "'" (ascii 39 single quote). We have provided a straightforward string remediation handler in [llmware](https://www.github.com/llmware-ai/llmware.git) that automatically remediates and provides a well-formed Python
|
25 |
|
26 |
-
-- If you are looking for a single output point, try the params "brief description (1)"
|
27 |
|
28 |
-
-- If the document has a lot of financial points, try the params "financial data points (5)"
|
29 |
|
30 |
-- Param counts are an experimental feature, but work reasonably well to guide the scope of the model's output length. At times, the model's attempt to match the target number of output points will result in some repetitive points.
|
31 |
|
@@ -72,7 +72,7 @@ For fast inference use of this model, we would recommend using the 'quantized to
|
|
72 |
output_only = ast.literal_eval(llm_string_output)
|
73 |
print("success - converted to python dictionary automatically")
|
74 |
except:
|
75 |
-
# note: rules-based conversion may be required - see
|
76 |
# for good example of post-processing conversion script
|
77 |
|
78 |
print("fail - could not convert to python dictionary automatically - ", llm_string_output)
|
|
|
21 |
|
22 |
## Usage Tips
|
23 |
|
24 |
+
-- Automatic (ast.literal_eval) conversion of the llm output to a python list is often complicated by the presence of '"' (ascii 34 double quotes) and "'" (ascii 39 single quote). We have provided a straightforward string remediation handler in [llmware](https://www.github.com/llmware-ai/llmware.git) that automatically remediates and provides a well-formed Python list. We have tried multiple ways to handle 34/39 in training - and each has a set of trade-offs - we will continue to look for ways to better automate in future releases of the model.
|
25 |
|
26 |
+
-- If you are looking for a single output point, try the params: "brief description (1)"
|
27 |
|
28 |
+
-- If the document has a lot of financial points, try the params "financial data points" or "financial data points (5)"
|
29 |
|
30 |
-- Param counts are an experimental feature, but work reasonably well to guide the scope of the model's output length. At times, the model's attempt to match the target number of output points will result in some repetitive points.
|
31 |
|
|
|
72 |
output_only = ast.literal_eval(llm_string_output)
|
73 |
print("success - converted to python dictionary automatically")
|
74 |
except:
|
75 |
+
# note: rules-based conversion may be required - see comment above - and remediation script @ https://www.github.com/llmware-ai/llmware/blobs/main/llmware/models.py - ModelCatalog.remediate_function_call_string()
|
76 |
# for good example of post-processing conversion script
|
77 |
|
78 |
print("fail - could not convert to python dictionary automatically - ", llm_string_output)
|