Add SetFit model

1_Pooling/config.json

@@ -5,5 +5,6 @@
   "pooling_mode_max_tokens": false,
   "pooling_mode_mean_sqrt_len_tokens": false,
   "pooling_mode_weightedmean_tokens": false,
-  "pooling_mode_lasttoken": false
+  "pooling_mode_lasttoken": false,
+  "include_prompt": true
 }

README.md

@@ -8,19 +8,64 @@ tags:
 metrics:
 - accuracy
 widget:
-- text: Hello Jonathan, Thank you for your work on the Beta project.  I would like
-    for us to set up a meeting to discuss your work on the project.  You have completed
-    a few reports now and I have had some feedback I would like to share with you;
-    specifically the commentary you are providing and your business writing.  The
-    additional commentary you are providing makes it difficult to find the objective
-    facts of your findings while working with a tight deadline.  I would like to have
-    a discussion with you what ideas you may have to help make your reports more concise
-    so the team can meet their deadlines. You are investing considerable time and
-    effort in these reports and you have expressed your desire to be in an engineering
-    role in the future. Your work on these reports can certainly help you in achieving
-    your career goals.  I want to make sure you are successful. I'll send out a meeting
-    invite shortly. Thank you again Jonathan for all your work on this project.  I'm
-    looking forward to discussing this with you.
+- text: Dear Jonathan, I am writing to find out how things are going on the Beta project.
+    I understand that you are enjoying the role and finding new applications.I have
+    had some feedback from Terry confirming that you are doing well but there are
+    some improvement points that I would like to discuss with you. It has been noted
+    that your contributions are providing real value and they enjoy working with you,
+    however, some of this value is spoiled by a conversational tone and being a bit
+    verbose. In business correspondence it is essential that the facts are clear,
+    concise and distinguishable from opinion, otherwise the message may be lost (regardless
+    of how good it is).There are a number of significant reports required in the coming
+    weeks. Please could you ensure that you confirm with Terry the exact detail and
+    format required for specific reports and communication. He should be able to provide
+    templates and guidance to ensure that his requirements are met. I would also recommend
+    that you undertake a report-writing course, which should help you to ensure that
+    you convey your great ideas in the best possible way.I am keen to support you
+    to ensure the success of the project and your professional development. When I
+    return in 2 weeks I would like to have a conference call with you and Terry to
+    better understand how we can help you going forward.  Please could you respond
+    to confirm that you have received this email. Regards, William
+- text: 'Hi Jonathan, Thank you for your message. I am glad about your excitment on
+    this assignment that is important to us, and I hear your will to develop into
+    an engenier team leader role which I think is a topic that can be discuss.In order
+    to take you to that role, it is important to work on of your development area
+    that concern the way you report your analysis.You have a great talent to collect
+    data and get new creative ideas, and it is crucial to make you able to be more
+    experienced in business writing to make sure that you adress your conclusions
+    in a sharp and concise way, avoiding too much commentary.I propose you to write
+    down your current reports keeping those 2 objectives in mind: avoid too much commentary
+    and focus on the main data that support your conclusions.I suggest you get inspired
+    from other reports done internally, that will help you understand better the formalism
+    the report should have.Then, let is discuss together the outcome of your report,
+    and I would specially would like to know more about the many application you identify
+    for Beta Technology that may bring new business opportunity. Just a tip, quantify
+    your comments, always.See you soon, and we will have the opportunity to take the
+    time to discuss your development plan based on your capacity to be more straight
+    to the point in your reports.I am sure you will make a difference. Good luck,
+    William'
+- text: Hey Jonathan! I've been in touch with Terry, I'm so glad to hear how much
+    you are enjoying the Beta Project, I even hear you are hoping that this experience
+    will further your ambitions toward a Lead Engineer position! However, I understand
+    there has been some issues with your reports that Terry has brought up with you,
+    and I wanted to take a few minutes to discuss them.1) Opinion vs. FactsYour reports
+    contain a lot of insights about what the data means, and at times finding the
+    specific hard facts can be difficult.2) Level of DetailYou include every bit of
+    data that you can into your reports, which can make it difficult to take away
+    the larger picture.I want to encourage you to take these things away for the following
+    reasons:1) your reports are reviewed by everyone in upper management, including
+    the CEO! The opinions you have are great, but when evaluating documents the CEO
+    just needs to highest level, most important items. The nitty-gritty would fall
+    to another department2) as you have a desire to move up and be a Lead Engineer,
+    these kinds of reports will be more and more common. Keeping your thoughts organized
+    and well documented is going to become a very important skill to have.For your
+    next report I would like you to prepare a cover sheet that goes with the report.
+    This cover sheet should be a single page highlighting only the key facts of the
+    report. Your own opinions and analysis can be included, but let those who are
+    interested read it on their own time, the high level facts are key for the meeting
+    they will be presented in. I would also encourage you to make sure the rest of
+    the report has clearly defined headings and topics, so it is easy to find information
+    related to each item. I
 - text: Good Afternoon Jonathan, I hope you are well and the travelling is not too
     exhausting. I wanted to touch base with you to see how you are enjoying working
     with the Beta project team? I have been advised that you are a great contributor
@@ -37,58 +82,21 @@ widget:
     your reports before submitting to ensure they are clear and consise with only
     the technical information needed,Let me know your thoughts. Many thanks again
     and well done for all your hard work. Kind regards William
-- text: 'Hi Jonathan, I am glad to hear that you are enjoying your job,  traveling
-    and learning more about the Beta ray technology. I wanted to share some feedback
-    with you that I received. I want to help you be able to advance in your career
-    and I feel that this feedback will be helpful. I am excited that you are will
-    to share your perspectives on the findings, however if you could focus on the
-    data portion first, and highlight the main points, that would be really beneficial
-    to your audience. By being more concise it will allow the potential customers
-    and then CEO to focus on the facts of the report, which will allow them to make
-    a decision for themselves. I understand that this is probably a newer to writing
-    the reports, and I don''t think that anyone has shown you an example of how the
-    reports are usually written, so I have sent you some examples for you to review.
-    I think that you are doing a good job learning and with this little tweak in the
-    report writing you will be able to advance in your career. In order to help you,
-    if you don''t mind, I would like to review the report before you submit it and
-    then we can work together to ensure it will be a great report. I understand that
-    you really enjoy providing your perspectives on the technology and recommendations
-    on how it can be used, so we will find a spot for that in the report as well,
-    but perhaps in a different section. Thank you so much for your time today and
-    I look forward to working with you. '
-- text: Hi Jonathan, Good to hear you are enjoying the work. I would like to discuss
-    with you feedback on your assignment and the reports you are producing. It is
-    very important to understand the stakeholders who will be reading your report.
-    You may have gathered a lot of good information BUT do not put them all on your
-    reports. The report should state facts and not your opinions. Create reports for
-    the purpose and for the audience. I would also suggest that you reach out to Terry
-    to understand what information is needed on the reports you produce.Having said
-    that, the additional insights you gathered are very important too. Please add
-    them to our knowledge repository and share with the team. It will be a great sharing
-    and learning experience. You are very valuable in your knowledge and I think that
-    it would benefit you and the organization tremendously when you are to channelize
-    your insights and present the facts well. I would encourage you to enroll for
-    the business writing training course. Please choose a date from the learning calendar
-    and let me know. Regards, William
-- text: Hi Jonathan, I understand you have been quite involved with the Beta Project.
-    Your experience is paying off as you are often finding improvements the product
-    team did not even know they needed.  I wanted to share some feedback I got from
-    one of your colleagues regarding your reports. Your enthusiasm for this project
-    is infectious and I love to see this level of engagement. However, we also want
-    to be mindful of the end users of the reports you are preparing. In these projects,
-    deadlines often move at a fast pace. In order to ensure the project can stay on
-    time, it is important to focus on inputting mainly facts when writing these reports.
-    You offer a unique perspective and your insights are greatly appreciated. I would
-    love to discuss your ideas with you in separate meetings outside of this project.
-    I understand you are having to compile and organize a large amount of information.
-    I appreciate how overwhelming this can feel at times. When these reports are completed,
-    they are reviewed by our CEO and other key stakeholders. To ensure we are respecting
-    their time, we want these reports to by concise and well organized. I would like
-    you to set up some time with Terry to go over his approach to these reports and
-    his writing style. Once I am back from assignment I will set up time to review
-    how this meeting went and discuss other ideas you may have. I greatly appreciate
-    your efforts on this project and positive attitude. With the above mentioned areas
-    of opportunity, I know this project will continue to run smoothly. Thanks.
+- text: 'Jonathan, First I want to thank you for your help with the Beta project.  However,  it
+    has been brought to my attention that perhaps ABC-5 didn''t do enough to prepare
+    you for the extra work and I would like to discuss some issues. The nature of
+    these reports requires them to be technical in nature.  Your insights are very
+    valuable and much appreciated but as the old line goes "please give me just the
+    facts".  Given the critical nature of the information you are providing I can''t
+    stress the importance of concise yet detail factual reports.  I would like to
+    review your reports as a training exercise to help you better meet the team requirements.  Given
+    that there are some major reports coming up in the immediate future, I would like
+    you to review some training options and then present a report for review.  Again
+    your insights are appreciated but we need to make sure we are presenting the end-use
+    with only the information they need to make a sound business decision. I also
+    understand you would like to grow into a leadership position so I would like to
+    discuss how successfully implementing these changes would be beneficial in demonstrating
+    an ability to grow and take on new challenges. '
 pipeline_tag: text-classification
 inference: true
 base_model: sentence-transformers/all-MiniLM-L6-v2
@@ -104,7 +112,7 @@ model-index:
       split: test
     metrics:
     - type: accuracy
-      value: 0.7692307692307693
+      value: 0.6153846153846154
       name: Accuracy
 ---
 
@@ -146,7 +154,7 @@ The model has been trained using an efficient few-shot learning technique that i
 ### Metrics
 | Label   | Accuracy |
 |:--------|:---------|
-| **all** | 0.7692   |
+| **all** | 0.6154   |
 
 ## Uses
 
@@ -164,9 +172,9 @@ Then you can load this model and run inference.
 from setfit import SetFitModel
 
 # Download from the 🤗 Hub
-model = SetFitModel.from_pretrained("sijan1/empathy_model")
+model = SetFitModel.from_pretrained("diegofiggie/empathy_model")
 # Run inference
-preds = model("Hello Jonathan, Thank you for your work on the Beta project.  I would like for us to set up a meeting to discuss your work on the project.  You have completed a few reports now and I have had some feedback I would like to share with you; specifically the commentary you are providing and your business writing.  The additional commentary you are providing makes it difficult to find the objective facts of your findings while working with a tight deadline.  I would like to have a discussion with you what ideas you may have to help make your reports more concise so the team can meet their deadlines. You are investing considerable time and effort in these reports and you have expressed your desire to be in an engineering role in the future. Your work on these reports can certainly help you in achieving your career goals.  I want to make sure you are successful. I'll send out a meeting invite shortly. Thank you again Jonathan for all your work on this project.  I'm looking forward to discussing this with you.")
+preds = model("Jonathan, First I want to thank you for your help with the Beta project.  However,  it has been brought to my attention that perhaps ABC-5 didn't do enough to prepare you for the extra work and I would like to discuss some issues. The nature of these reports requires them to be technical in nature.  Your insights are very valuable and much appreciated but as the old line goes \"please give me just the facts\".  Given the critical nature of the information you are providing I can't stress the importance of concise yet detail factual reports.  I would like to review your reports as a training exercise to help you better meet the team requirements.  Given that there are some major reports coming up in the immediate future, I would like you to review some training options and then present a report for review.  Again your insights are appreciated but we need to make sure we are presenting the end-use with only the information they need to make a sound business decision. I also understand you would like to grow into a leadership position so I would like to discuss how successfully implementing these changes would be beneficial in demonstrating an ability to grow and take on new challenges. ")
 ```
 
 <!--
@@ -210,7 +218,7 @@ preds = model("Hello Jonathan, Thank you for your work on the Beta project.  I w
 - num_epochs: (1, 1)
 - max_steps: -1
 - sampling_strategy: oversampling
-- num_iterations: 40
+- num_iterations: 20
 - body_learning_rate: (2e-05, 2e-05)
 - head_learning_rate: 2e-05
 - loss: CosineSimilarityLoss
@@ -224,19 +232,17 @@ preds = model("Hello Jonathan, Thank you for your work on the Beta project.  I w
 - load_best_model_at_end: False
 
 ### Training Results
-| Epoch  | Step | Training Loss | Validation Loss |
-|:------:|:----:|:-------------:|:---------------:|
-| 0.025  | 1    | 0.0001        | -               |
-| 2.5    | 50   | 0.0001        | -               |
-| 0.0667 | 1    | 0.0           | -               |
+| Epoch | Step | Training Loss | Validation Loss |
+|:-----:|:----:|:-------------:|:---------------:|
+| 0.1   | 1    | 0.1814        | -               |
 
 ### Framework Versions
-- Python: 3.10.12
+- Python: 3.10.9
 - SetFit: 1.0.3
-- Sentence Transformers: 2.3.1
-- Transformers: 4.35.2
-- PyTorch: 2.1.0+cu121
-- Datasets: 2.17.0
+- Sentence Transformers: 2.4.0
+- Transformers: 4.38.1
+- PyTorch: 2.2.1+cpu
+- Datasets: 2.17.1
 - Tokenizers: 0.15.2
 
 ## Citation

config.json

@@ -19,7 +19,7 @@
   "pad_token_id": 0,
   "position_embedding_type": "absolute",
   "torch_dtype": "float32",
-  "transformers_version": "4.35.2",
+  "transformers_version": "4.38.1",
   "type_vocab_size": 2,
   "use_cache": true,
   "vocab_size": 30522

config_sentence_transformers.json

@@ -3,5 +3,7 @@
     "sentence_transformers": "2.0.0",
     "transformers": "4.6.1",
     "pytorch": "1.8.1"
-  }
+  },
+  "prompts": {},
+  "default_prompt_name": null
 }

model.safetensors

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:10c52449c6d8588cde86537019ddba56c3bff699572e63965cbc08cb41424977
+oid sha256:40ea396ded07693a46677f5a7842b4da49a16f5dc48f4d992aac11877affad9b
 size 90864192

model_head.pkl

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:be3b704a64e250dd303e0cd01a10a8bdf22e73be36880eef318adee146fa34af
-size 3935
+oid sha256:3179b7cf4f42b0be7cd3fab59bbc7a5ea292ee4ba5aaf986f4036344c3b1ab55
+size 3813

special_tokens_map.json

@@ -1,7 +1,37 @@
 {
-  "cls_token": "[CLS]",
-  "mask_token": "[MASK]",
-  "pad_token": "[PAD]",
-  "sep_token": "[SEP]",
-  "unk_token": "[UNK]"
+  "cls_token": {
+    "content": "[CLS]",
+    "lstrip": false,
+    "normalized": false,
+    "rstrip": false,
+    "single_word": false
+  },
+  "mask_token": {
+    "content": "[MASK]",
+    "lstrip": false,
+    "normalized": false,
+    "rstrip": false,
+    "single_word": false
+  },
+  "pad_token": {
+    "content": "[PAD]",
+    "lstrip": false,
+    "normalized": false,
+    "rstrip": false,
+    "single_word": false
+  },
+  "sep_token": {
+    "content": "[SEP]",
+    "lstrip": false,
+    "normalized": false,
+    "rstrip": false,
+    "single_word": false
+  },
+  "unk_token": {
+    "content": "[UNK]",
+    "lstrip": false,
+    "normalized": false,
+    "rstrip": false,
+    "single_word": false
+  }
 }