Librarian Bot: Add base_model information to model
Browse filesThis pull request aims to enrich the metadata of your model by adding [`facebook/bart-large`](https://huggingface.co/facebook/bart-large) as a `base_model` field, situated in the `YAML` block of your model's `README.md`.
How did we find this information? We performed a regular expression match on your `README.md` file to determine the connection.
**Why add this?** Enhancing your model's metadata in this way:
- **Boosts Discoverability** - It becomes straightforward to trace the relationships between various models on the Hugging Face Hub.
- **Highlights Impact** - It showcases the contributions and influences different models have within the community.
For a hands-on example of how such metadata can play a pivotal role in mapping model connections, take a look at [librarian-bots/base_model_explorer](https://huggingface.co/spaces/librarian-bots/base_model_explorer).
This PR comes courtesy of [Librarian Bot](https://huggingface.co/librarian-bot). If you have any feedback, queries, or need assistance, please don't hesitate to reach out to [@davanstrien](https://huggingface.co/davanstrien).
If you want to automatically add `base_model` metadata to more of your modes you can use the [Librarian Bot](https://huggingface.co/librarian-bot) [Metadata Request Service](https://huggingface.co/spaces/librarian-bots/metadata_request_service)!
@@ -1,11 +1,26 @@
|
|
1 |
---
|
2 |
language: en
|
3 |
-
datasets:
|
4 |
-
- Short-Answer-Feedback/saf_communication_networks_english
|
5 |
tags:
|
6 |
- generated_from_trainer
|
|
|
|
|
7 |
widget:
|
8 |
-
- text:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
9 |
---
|
10 |
|
11 |
# bart-finetuned-saf-communication-networks
|
|
|
1 |
---
|
2 |
language: en
|
|
|
|
|
3 |
tags:
|
4 |
- generated_from_trainer
|
5 |
+
datasets:
|
6 |
+
- Short-Answer-Feedback/saf_communication_networks_english
|
7 |
widget:
|
8 |
+
- text: 'Answer: In TCP there is a Sequence Number field to identify packets individually
|
9 |
+
for reliability. There is no Sequence Number in UDP. The UDP header does not have
|
10 |
+
an options field, while the TCP header does. In TCP there is an Advertised Window
|
11 |
+
field for the Sliding Window Protocol for Flow Control. There is no Flow Control
|
12 |
+
and therefore no Advertised Window field in UDP. In TCP there there is only a
|
13 |
+
Data Offset field that specifies the header length. In UDP the whole Packet Length
|
14 |
+
is transmitted. Reference: Possible Differences : The UPD header (8 bytes) is
|
15 |
+
much shorter than the TCP header (20-60 bytes) The UDP header has a fixed length
|
16 |
+
while the TCP header has a variable length Fields contained in the TCP header
|
17 |
+
and not the UDP header : -Sequence number -Acknowledgment number -Reserved -Flags/Control
|
18 |
+
bits -Advertised window -Urgent Pointer -Options + Padding if the options are
|
19 |
+
UDP includes the packet length (data + header) while TCP has the header length/data
|
20 |
+
offset (just header) field instead The sender port field is optional in UDP, while
|
21 |
+
the source port in TCP is necessary to establish the connection Question: State
|
22 |
+
at least 4 of the differences shown in the lecture between the UDP and TCP headers.'
|
23 |
+
base_model: facebook/bart-large
|
24 |
---
|
25 |
|
26 |
# bart-finetuned-saf-communication-networks
|