Update README.md
Browse files
README.md
CHANGED
|
@@ -6,7 +6,6 @@
|
|
| 6 |
|
| 7 |
**Dataset:** bitext/Bitext-customer-support-llm-chatbot-training-dataset
|
| 8 |
|
| 9 |
-
**Quantization:** Applied FP16 for optimized inference
|
| 10 |
|
| 11 |
**Training Device:** CUDA (GPU)
|
| 12 |
|
|
@@ -108,13 +107,6 @@ Expected Output:
|
|
| 108 |
Issue: How do I cancel my order?
|
| 109 |
Resolution: Log into the portal and cancel it there.
|
| 110 |
```
|
| 111 |
-
# Quantization & Optimization
|
| 112 |
-
Quantization: Applied FP16 using PyTorch’s .half() post-training for faster inference and reduced model size (~279MB from ~558MB).
|
| 113 |
-
Optimization: Trained with mixed precision (FP16) on CUDA, further quantized for deployment efficiency.
|
| 114 |
-
Usage
|
| 115 |
-
Input: Text representing a customer support issue (e.g., "Customer: My payment isn’t going through, help!")
|
| 116 |
-
|
| 117 |
-
Output: Text providing an actionable resolution (e.g., "Check your card details and try again.")
|
| 118 |
|
| 119 |
# Limitations
|
| 120 |
Model may struggle with issues requiring specific resolutions not well-represented in the training data (e.g., time-related queries like "When can I call support?").
|
|
@@ -122,4 +114,3 @@ Resolution extraction relied on heuristics, potentially missing nuanced answers
|
|
| 122 |
# Future Improvements
|
| 123 |
Refine resolution extraction with more advanced NLP techniques or manual curation.
|
| 124 |
Fine-tune on additional customer support datasets for broader coverage.
|
| 125 |
-
Evaluate with formal metrics (e.g., ROUGE) for quantitative performance.
|
|
|
|
| 6 |
|
| 7 |
**Dataset:** bitext/Bitext-customer-support-llm-chatbot-training-dataset
|
| 8 |
|
|
|
|
| 9 |
|
| 10 |
**Training Device:** CUDA (GPU)
|
| 11 |
|
|
|
|
| 107 |
Issue: How do I cancel my order?
|
| 108 |
Resolution: Log into the portal and cancel it there.
|
| 109 |
```
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 110 |
|
| 111 |
# Limitations
|
| 112 |
Model may struggle with issues requiring specific resolutions not well-represented in the training data (e.g., time-related queries like "When can I call support?").
|
|
|
|
| 114 |
# Future Improvements
|
| 115 |
Refine resolution extraction with more advanced NLP techniques or manual curation.
|
| 116 |
Fine-tune on additional customer support datasets for broader coverage.
|
|
|