Mr-TD commited on
Commit
72c0475
1 Parent(s): bdd3eb5

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +5 -133
README.md CHANGED
@@ -39,138 +39,10 @@ GGML files are for CPU + GPU inference using [llama.cpp](https://github.com/gger
39
  ### Response:
40
  {response}
41
  ```
42
- ## Provided files
43
-
44
- | Name | Quant method | Bits | Size | Use case |
45
- | ---- | ---- | ---- | ---- | ---- | ----- |
46
- | Llama-2-7b-MOM_Summar.Q2_K.gguf | q2_K | 2 | 2.53 GB| New k-quant method. Uses GGML_TYPE_Q4_K for the attention.vw and feed_forward.w2 tensors, GGML_TYPE_Q2_K for the other tensors. |
47
- | Llama-2-7b-MOM_Summar.Q4_K_S.gguf | q4_K_S | 4 | 2.95 GB| New k-quant method. Uses GGML_TYPE_Q4_K for all tensors |
48
-
49
- ## Result Comparision
50
-
51
- | Quant Method | Transcript | Summary | Infrence Time |
52
- | ---- | ---- | ---- | ---- | ---- | ----- |
53
- | q2_k | {'date': '2023-03-08',
54
- 'time': '10:00 AM - 12:00 PM',
55
- 'attendess': ['Manager',
56
- 'Junior Developer 1',
57
- 'Junior Developer 2',
58
- 'Junior Developer 3',
59
- 'Junior Developer 4',
60
- 'Junior Developer 5',
61
- 'Technical Support Engineer'],
62
- 'transcript': ["Manager:Good morning team, let's start our daily standup meeting.",
63
- 'Junior Developer 1:Yesterday, I completed the feature implementation for task XYZ. Today, I plan to start working on bug fixes.',
64
- "Junior Developer 2:I've been working on refactoring the codebase. I've encountered some issues with unit tests, but I'm confident I can resolve them by this afternoon.",
65
- "Junior Developer 3:I've been working on the integration with the third-party API. I'm facing some challenges with the authentication process, but I'm exploring different solutions.",
66
- "Junior Developer 4:I've been writing documentation for the new feature. I'm almost done, and I plan to submit it for review by the end of the day.",
67
- "Junior Developer 5:I've been assisting users with technical issues. There's been a recent spike in support requests related to a specific feature. I'm working with the team to investigate the issue.",
68
- "Technical Support Engineer:I've been testing the new build and have identified a potential performance issue. I've reported it to the team, and we're looking into it.",
69
- 'Manager:Thank you for the updates. Does anyone have any roadblocks or issues they need assistance with?',
70
- "Junior Developer 3:I'm stuck with the API authentication. I've tried multiple approaches, but none of them seem to work.",
71
- "Technical Support Engineer:I've worked with this API before. Let me take a look and see if I can help.",
72
- "Manager:That's great. Thanks for stepping in. Junior Developer 3, please work with the Technical Support Engineer to resolve this issue.",
73
- 'Junior Developer 3:Thank you, I appreciate the assistance.',
74
- 'Manager:Are there any other updates or announcements?',
75
- "Junior Developer 2:I'd like to suggest we introduce unit testing for the new feature before it goes live. It will help us catch potential bugs early on.",
76
- "Manager:That's a great suggestion. We'll schedule a session to discuss this further and finalize the testing plan.",
77
- "Manager:Before we end, I'd like to remind everyone about the upcoming code review deadline. Please complete your reviews and provide feedback by the end of the week.",
78
- 'Attendess:Understood.',
79
- "Manager:Thank you, team. Let's continue the hard work and keep each other updated on our progress. See you all tomorrow for our next meeting."]} | **Key Points Discussed:**
80
-
81
- * Implementation of feature XYZ completed successfully.
82
- * Bug fixes are in progress today, with a focus on resolving issues encountered during refactoring codebase.
83
- * Integration with third-party API is underway and facing challenges related to authentication process.
84
- * Documentation for new feature is near completion, with plans to submit it by the end of the day.
85
- * Technical support requests have increased in recent days due to a specific issue affecting users' experience. The team is investigating the cause together.
86
- * Performance issues encountered during testing were reported and are being addressed.
87
-
88
- **Major Updates:**
89
-
90
- * New feature implementation complete, with documentation near completion for submission review by end of day.
91
- * Refactoring codebase in progress; unit tests identified as potential issue, to be resolved through exploration of alternative solutions.
92
- * Integration with third-party API facing authentication challenges and seeking technical support from the team.
93
- * Technical issues encountered due to a specific feature affect users' experience, investigated by all members for resolution.
94
- * Performance issue encountered during testing identified; being addressed by the team.
95
-
96
- **Priority Tasks:**
97
-
98
- * Completion of documentation submission review in progress (by end of day).
99
- * Implementation and completion of bug fixes in progress today.
100
- * Integration with third-party API facing authentication challenges, requiring technical support from all members for resolution.
101
- * Investigating the cause behind performance issues encountered during testing; to be addressed by team upon identification.
102
-
103
- **Current Tasks:**
104
-
105
- * Completion and submission of documentation review (by end of day).
106
- * Bug fixes in progress today with focus on resolving authentication challenges faced during refactoring codebase.
107
- * Integration with third-party API facing authentication issues, requiring technical support from all members for resolution.
108
- * Investigating the cause behind performance issue encountered during testing; to be addressed by team upon identification.
109
 
110
- **Completed Tasks:**
111
-
112
- * Implementation of feature XYZ complete (successfully).
113
- * Bug fixes in progress today with focus on resolving authentication issues faced during refactoring codebase.
114
- * Integration with third-party API facing authentication challenges, requiring technical support from all members for resolution.
115
- * Documentation near completion; to be submitted by end of day and reviewed upon completion (in progress).
116
- * Investigating the cause behind performance issue encountered during testing; to be addressed by team upon identification (ongoing).
117
-
118
- **Completed Tasks:**
119
-
120
- * Implementation of feature XYZ complete.
121
- * Bug fixes in progress today with focus on resolving authentication issues faced during refactoring codebase.
122
- * Integration with third-party API facing authentication challenges, requiring technical support from all members for resolution.
123
- * Documentation near completion; to be submitted by end of day and reviewed upon completion (in progress).
124
- * Investigating the cause behind performance issue encountered during testing; to be addressed by team upon identification (ongoing).
125
- | 5m41s |
126
- | q4_k_s | {'date': '2023-03-08',
127
- 'time': '10:00 AM - 12:00 PM',
128
- 'attendess': ['Manager',
129
- 'Junior Developer 1',
130
- 'Junior Developer 2',
131
- 'Junior Developer 3',
132
- 'Junior Developer 4',
133
- 'Junior Developer 5',
134
- 'Technical Support Engineer'],
135
- 'transcript': ["Manager:Good morning team, let's start our daily standup meeting.",
136
- 'Junior Developer 1:Yesterday, I completed the feature implementation for task XYZ. Today, I plan to start working on bug fixes.',
137
- "Junior Developer 2:I've been working on refactoring the codebase. I've encountered some issues with unit tests, but I'm confident I can resolve them by this afternoon.",
138
- "Junior Developer 3:I've been working on the integration with the third-party API. I'm facing some challenges with the authentication process, but I'm exploring different solutions.",
139
- "Junior Developer 4:I've been writing documentation for the new feature. I'm almost done, and I plan to submit it for review by the end of the day.",
140
- "Junior Developer 5:I've been assisting users with technical issues. There's been a recent spike in support requests related to a specific feature. I'm working with the team to investigate the issue.",
141
- "Technical Support Engineer:I've been testing the new build and have identified a potential performance issue. I've reported it to the team, and we're looking into it.",
142
- 'Manager:Thank you for the updates. Does anyone have any roadblocks or issues they need assistance with?',
143
- "Junior Developer 3:I'm stuck with the API authentication. I've tried multiple approaches, but none of them seem to work.",
144
- "Technical Support Engineer:I've worked with this API before. Let me take a look and see if I can help.",
145
- "Manager:That's great. Thanks for stepping in. Junior Developer 3, please work with the Technical Support Engineer to resolve this issue.",
146
- 'Junior Developer 3:Thank you, I appreciate the assistance.',
147
- 'Manager:Are there any other updates or announcements?',
148
- "Junior Developer 2:I'd like to suggest we introduce unit testing for the new feature before it goes live. It will help us catch potential bugs early on.",
149
- "Manager:That's a great suggestion. We'll schedule a session to discuss this further and finalize the testing plan.",
150
- "Manager:Before we end, I'd like to remind everyone about the upcoming code review deadline. Please complete your reviews and provide feedback by the end of the week.",
151
- 'Attendess:Understood.',
152
- "Manager:Thank you, team. Let's continue the hard work and keep each other updated on our progress. See you all tomorrow for our next meeting."]} |
153
- **Key Points Discussed in Standup Meeting**
154
-
155
- * **Completed Tasks:** Junior Developer 1 completed feature implementation, Junior Developer 2 refactored codebase and worked on unit tests.
156
- * **Current Priorities:** Junior Developers are working on bug fixes (Junior Developer 1), API integration issues (Junior Developer 3) and documentation for the new feature (Junior Developer 4).
157
- * **Support Requests:** A spike in support requests related to a specific feature has been identified. Junior Developers are working with Technical Support Engineer to investigate.
158
- * **Performance Issue Identified:** A potential performance issue was reported and is being investigated by the team.
159
- * **Upcoming Deadlines:** Code reviews for new features must be completed by end of week.
160
-
161
- ### Meeting highlights include:
162
- * Unit testing will be introduced to enhance feature quality before launch (Junior Developer 2).
163
- * Technical Support Engineer offered assistance with API authentication issue (Junior Developer3).
164
- * Code reviews for new features are due by end of week.
165
-
166
- **Major Updates:**
167
- No major updates were reported during the meeting.
168
-
169
- **Priority Tasks:** Junior Developers will continue working on bug fixes, unit testing and documentation. Technical Support Engineer is assisting with API authentication issue. Code reviews for new features are due by end of week.
170
-
171
- **Completed Tasks:** Feature implementation (Junior Developer 1), codebase refactoring (Junior Developer2) and documentation writing (Junior Developer4).
172
-
173
- **Current Priorities:** Bug fixes, API integration issues resolution and unit testing for new features. Support investigation of spike in support requests related to a specific feature. Performance issue investigation. Code reviews for new features by end of week.
174
 
175
- **Priority Tasks:** Resolve API authentication issue (Junior Developer3), finalize code review plan for new features and schedule unit testing session (Junior Developers 2). Investigate performance issue with Technical Support Engineer (Manager, Junior Developer4). Complete code reviews by end of week.
176
- | 4m30s |
 
 
 
39
  ### Response:
40
  {response}
41
  ```
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
42
 
43
+ ## Provided files
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
44
 
45
+ | Name | Quant method | Bits | Size | Use case |
46
+ |-------------------------------------|--------------|------|--------|-----------------------------------------------------------------|
47
+ | Llama-2-7b-MOM_Summar.Q2_K.gguf | q2_K | 2 | 2.53 GB| New k-quant method. Uses GGML_TYPE_Q4_K for the attention.vw and feed_forward.w2 tensors, GGML_TYPE_Q2_K for the other tensors. |
48
+ | Llama-2-7b-MOM_Summar.Q4_K_S.gguf | q4_K_S | 4 | 2.95 GB| New k-quant method. Uses GGML_TYPE_Q4_K for all tensors |