Commit
•
7ec777a
1
Parent(s):
4c7bb25
Update README.md
Browse files
README.md
CHANGED
|
@@ -34,6 +34,10 @@ AISAK undergoes rigorous testing across diverse input data types, consistently d
|
|
| 34 |
- While AISAK demonstrates proficiency in text generation, it might not be the most suitable option for tasks that necessitate domain-specific knowledge.
|
| 35 |
- The model's performance could exhibit variations when confronted with highly specialized or out-of-domain textual data.
|
| 36 |
|
|
|
|
|
|
|
|
|
|
|
|
|
| 37 |
### Caveats:
|
| 38 |
|
| 39 |
- It is recommended for users to double-check important decisions relying on AISAK's predictions, particularly in high-stakes scenarios.
|
|
|
|
| 34 |
- While AISAK demonstrates proficiency in text generation, it might not be the most suitable option for tasks that necessitate domain-specific knowledge.
|
| 35 |
- The model's performance could exhibit variations when confronted with highly specialized or out-of-domain textual data.
|
| 36 |
|
| 37 |
+
|
| 38 |
+
### Deployment:
|
| 39 |
+
|
| 40 |
+
I am currently having trouble deploying the model in a conversational instance with conversational history and context. At the current moment it's only been tested as a Q/A, if no knowledge of the previous input OR output, if anyone knows how to solve this setback, please do contact me at mandelakorilogan@gmail.com.
|
| 41 |
### Caveats:
|
| 42 |
|
| 43 |
- It is recommended for users to double-check important decisions relying on AISAK's predictions, particularly in high-stakes scenarios.
|