Add evaluation results on the kmfoda--booksum config of kmfoda/booksum
Browse filesBeep boop, I am a bot from Hugging Face's automatic model evaluator 👋!\
Your model has been evaluated on the kmfoda--booksum config of the [kmfoda/booksum](https://huggingface.co/datasets/kmfoda/booksum) dataset by
@pszemraj
, using the predictions stored [here](https://huggingface.co/datasets/autoevaluate/autoeval-staging-eval-project-kmfoda__booksum-d9df6ac3-10825454).\
Accept this pull request to see the results displayed on the [Hub leaderboard](https://huggingface.co/spaces/autoevaluate/leaderboards?dataset=kmfoda/booksum).\
Evaluate your model on more datasets [here](https://huggingface.co/spaces/autoevaluate/model-evaluator?dataset=kmfoda/booksum).
README.md
CHANGED
@@ -10,58 +10,201 @@ datasets:
|
|
10 |
metrics:
|
11 |
- rouge
|
12 |
widget:
|
13 |
-
- text:
|
14 |
-
|
15 |
-
|
16 |
-
|
17 |
-
|
18 |
-
|
19 |
-
|
20 |
-
|
21 |
-
|
22 |
-
|
23 |
-
|
24 |
-
|
25 |
-
|
26 |
-
|
27 |
-
|
28 |
-
|
29 |
-
|
30 |
-
|
31 |
-
|
32 |
-
|
33 |
-
|
34 |
-
|
35 |
-
|
36 |
-
|
37 |
-
|
38 |
-
|
39 |
-
|
40 |
-
|
41 |
-
|
42 |
-
|
43 |
-
|
44 |
-
|
45 |
-
|
46 |
-
|
47 |
-
|
48 |
-
|
49 |
-
|
50 |
-
|
51 |
-
|
52 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
53 |
inference:
|
54 |
parameters:
|
55 |
max_length: 64
|
56 |
min_length: 8
|
57 |
no_repeat_ngram_size: 3
|
58 |
-
early_stopping:
|
59 |
repetition_penalty: 3.5
|
60 |
length_penalty: 0.3
|
61 |
-
encoder_no_repeat_ngram_size
|
62 |
-
num_beams
|
63 |
-
|
64 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
65 |
---
|
66 |
|
67 |
# Longformer Encoder-Decoder (LED) for Narrative-Esque Long Text Summarization
|
|
|
10 |
metrics:
|
11 |
- rouge
|
12 |
widget:
|
13 |
+
- text: large earthquakes along a given fault segment do not occur at random intervals
|
14 |
+
because it takes time to accumulate the strain energy for the rupture. The rates
|
15 |
+
at which tectonic plates move and accumulate strain at their boundaries are approximately
|
16 |
+
uniform. Therefore, in first approximation, one may expect that large ruptures
|
17 |
+
of the same fault segment will occur at approximately constant time intervals.
|
18 |
+
If subsequent main shocks have different amounts of slip across the fault, then
|
19 |
+
the recurrence time may vary, and the basic idea of periodic mainshocks must be
|
20 |
+
modified. For great plate boundary ruptures the length and slip often vary by
|
21 |
+
a factor of 2. Along the southern segment of the San Andreas fault the recurrence
|
22 |
+
interval is 145 years with variations of several decades. The smaller the standard
|
23 |
+
deviation of the average recurrence interval, the more specific could be the long
|
24 |
+
term prediction of a future mainshock.
|
25 |
+
example_title: earthquakes
|
26 |
+
- text: " A typical feed-forward neural field algorithm. Spatiotemporal coordinates\
|
27 |
+
\ are fed into a neural network that predicts values in the reconstructed domain.\
|
28 |
+
\ Then, this domain is mapped to the sensor domain where sensor measurements are\
|
29 |
+
\ available as supervision. Class and Section Problems Addressed Generalization\
|
30 |
+
\ (Section 2) Inverse problems, ill-posed problems, editability; symmetries. Hybrid\
|
31 |
+
\ Representations (Section 3) Computation & memory efficiency, representation\
|
32 |
+
\ capacity, editability: Forward Maps (Section 4) Inverse problems Network Architecture\
|
33 |
+
\ (Section 5) Spectral bias, integration & derivatives. Manipulating Neural Fields\
|
34 |
+
\ (Section 6) Edit ability, constraints, regularization. Table 2: The five classes\
|
35 |
+
\ of techniques in the neural field toolbox each addresses problems that arise\
|
36 |
+
\ in learning, inference, and control. (Section 3). We can supervise reconstruction\
|
37 |
+
\ via differentiable forward maps that transform Or project our domain (e.g, 3D\
|
38 |
+
\ reconstruction via 2D images; Section 4) With appropriate network architecture\
|
39 |
+
\ choices, we can overcome neural network spectral biases (blurriness) and efficiently\
|
40 |
+
\ compute derivatives and integrals (Section 5). Finally, we can manipulate neural\
|
41 |
+
\ fields to add constraints and regularizations, and to achieve editable representations\
|
42 |
+
\ (Section 6). Collectively, these classes constitute a 'toolbox' of techniques\
|
43 |
+
\ to help solve problems with neural fields There are three components in a conditional\
|
44 |
+
\ neural field: (1) An encoder or inference function \u20AC that outputs the conditioning\
|
45 |
+
\ latent variable 2 given an observation 0 E(0) =2. 2 is typically a low-dimensional\
|
46 |
+
\ vector, and is often referred to aS a latent code Or feature code_ (2) A mapping\
|
47 |
+
\ function 4 between Z and neural field parameters O: Y(z) = O; (3) The neural\
|
48 |
+
\ field itself $. The encoder \u20AC finds the most probable z given the observations\
|
49 |
+
\ O: argmaxz P(2/0). The decoder maximizes the inverse conditional probability\
|
50 |
+
\ to find the most probable 0 given Z: arg- max P(Olz). We discuss different encoding\
|
51 |
+
\ schemes with different optimality guarantees (Section 2.1.1), both global and\
|
52 |
+
\ local conditioning (Section 2.1.2), and different mapping functions Y (Section\
|
53 |
+
\ 2.1.3) 2. Generalization Suppose we wish to estimate a plausible 3D surface\
|
54 |
+
\ shape given a partial or noisy point cloud. We need a suitable prior over the\
|
55 |
+
\ sur- face in its reconstruction domain to generalize to the partial observations.\
|
56 |
+
\ A neural network expresses a prior via the function space of its architecture\
|
57 |
+
\ and parameters 0, and generalization is influenced by the inductive bias of\
|
58 |
+
\ this function space (Section 5)."
|
59 |
+
example_title: scientific paper
|
60 |
+
- text: ' the big variety of data coming from diverse sources is one of the key properties
|
61 |
+
of the big data phenomenon. It is, therefore, beneficial to understand how data
|
62 |
+
is generated in various environments and scenarios, before looking at what should
|
63 |
+
be done with this data and how to design the best possible architecture to accomplish
|
64 |
+
this The evolution of IT architectures, described in Chapter 2, means that the
|
65 |
+
data is no longer processed by a few big monolith systems, but rather by a group
|
66 |
+
of services In parallel to the processing layer, the underlying data storage has
|
67 |
+
also changed and became more distributed This, in turn, required a significant
|
68 |
+
paradigm shift as the traditional approach to transactions (ACID) could no longer
|
69 |
+
be supported. On top of this, cloud computing is becoming a major approach with
|
70 |
+
the benefits of reducing costs and providing on-demand scalability but at the
|
71 |
+
same time introducing concerns about privacy, data ownership, etc In the meantime
|
72 |
+
the Internet continues its exponential growth: Every day both structured and unstructured
|
73 |
+
data is published and available for processing: To achieve competitive advantage
|
74 |
+
companies have to relate their corporate resources to external services, e.g.
|
75 |
+
financial markets, weather forecasts, social media, etc While several of the sites
|
76 |
+
provide some sort of API to access the data in a more orderly fashion; countless
|
77 |
+
sources require advanced web mining and Natural Language Processing (NLP) processing
|
78 |
+
techniques: Advances in science push researchers to construct new instruments
|
79 |
+
for observing the universe O conducting experiments to understand even better
|
80 |
+
the laws of physics and other domains. Every year humans have at their disposal
|
81 |
+
new telescopes, space probes, particle accelerators, etc These instruments generate
|
82 |
+
huge streams of data, which need to be stored and analyzed. The constant drive
|
83 |
+
for efficiency in the industry motivates the introduction of new automation techniques
|
84 |
+
and process optimization: This could not be done without analyzing the precise
|
85 |
+
data that describe these processes. As more and more human tasks are automated,
|
86 |
+
machines provide rich data sets, which can be analyzed in real-time to drive efficiency
|
87 |
+
to new levels. Finally, it is now evident that the growth of the Internet of Things
|
88 |
+
is becoming a major source of data. More and more of the devices are equipped
|
89 |
+
with significant computational power and can generate a continuous data stream
|
90 |
+
from their sensors. In the subsequent sections of this chapter, we will look at
|
91 |
+
the domains described above to see what they generate in terms of data sets. We
|
92 |
+
will compare the volumes but will also look at what is characteristic and important
|
93 |
+
from their respective points of view. 3.1 The Internet is undoubtedly the largest
|
94 |
+
database ever created by humans. While several well described; cleaned, and structured
|
95 |
+
data sets have been made available through this medium, most of the resources
|
96 |
+
are of an ambiguous, unstructured, incomplete or even erroneous nature. Still,
|
97 |
+
several examples in the areas such as opinion mining, social media analysis, e-governance,
|
98 |
+
etc, clearly show the potential lying in these resources. Those who can successfully
|
99 |
+
mine and interpret the Internet data can gain unique insight and competitive advantage
|
100 |
+
in their business An important area of data analytics on the edge of corporate
|
101 |
+
IT and the Internet is Web Analytics.'
|
102 |
+
example_title: data science textbook
|
103 |
+
- text: "Transformer-based models have shown to be very useful for many NLP tasks.\
|
104 |
+
\ However, a major limitation of transformers-based models is its O(n^2)O(n 2)\
|
105 |
+
\ time & memory complexity (where nn is sequence length). Hence, it's computationally\
|
106 |
+
\ very expensive to apply transformer-based models on long sequences n > 512n>512.\
|
107 |
+
\ Several recent papers, e.g. Longformer, Performer, Reformer, Clustered attention\
|
108 |
+
\ try to remedy this problem by approximating the full attention matrix. You can\
|
109 |
+
\ checkout \U0001F917's recent blog post in case you are unfamiliar with these\
|
110 |
+
\ models.\nBigBird (introduced in paper) is one of such recent models to address\
|
111 |
+
\ this issue. BigBird relies on block sparse attention instead of normal attention\
|
112 |
+
\ (i.e. BERT's attention) and can handle sequences up to a length of 4096 at a\
|
113 |
+
\ much lower computational cost compared to BERT. It has achieved SOTA on various\
|
114 |
+
\ tasks involving very long sequences such as long documents summarization, question-answering\
|
115 |
+
\ with long contexts.\nBigBird RoBERTa-like model is now available in \U0001F917\
|
116 |
+
Transformers. The goal of this post is to give the reader an in-depth understanding\
|
117 |
+
\ of big bird implementation & ease one's life in using BigBird with \U0001F917\
|
118 |
+
Transformers. But, before going into more depth, it is important to remember that\
|
119 |
+
\ the BigBird's attention is an approximation of BERT's full attention and therefore\
|
120 |
+
\ does not strive to be better than BERT's full attention, but rather to be more\
|
121 |
+
\ efficient. It simply allows to apply transformer-based models to much longer\
|
122 |
+
\ sequences since BERT's quadratic memory requirement quickly becomes unbearable.\
|
123 |
+
\ Simply put, if we would have \u221E compute & \u221E time, BERT's attention\
|
124 |
+
\ would be preferred over block sparse attention (which we are going to discuss\
|
125 |
+
\ in this post).\nIf you wonder why we need more compute when working with longer\
|
126 |
+
\ sequences, this blog post is just right for you!\nSome of the main questions\
|
127 |
+
\ one might have when working with standard BERT-like attention include:\nDo all\
|
128 |
+
\ tokens really have to attend to all other tokens? Why not compute attention\
|
129 |
+
\ only over important tokens? How to decide what tokens are important? How to\
|
130 |
+
\ attend to just a few tokens in a very efficient way? In this blog post, we will\
|
131 |
+
\ try to answer those questions.\nWhat tokens should be attended to? We will give\
|
132 |
+
\ a practical example of how attention works by considering the sentence 'BigBird\
|
133 |
+
\ is now available in HuggingFace for extractive question answering'. In BERT-like\
|
134 |
+
\ attention, every word would simply attend to all other tokens.\nLet's think\
|
135 |
+
\ about a sensible choice of key tokens that a queried token actually only should\
|
136 |
+
\ attend to by writing some pseudo-code. Will will assume that the token available\
|
137 |
+
\ is queried and build a sensible list of key tokens to attend to.\n>>> # let's\
|
138 |
+
\ consider following sentence as an example >>> example = ['BigBird', 'is', 'now',\
|
139 |
+
\ 'available', 'in', 'HuggingFace', 'for', 'extractive', 'question', 'answering']\n\
|
140 |
+
>>> # further let's assume, we're trying to understand the representation of 'available'\
|
141 |
+
\ i.e. >>> query_token = 'available' >>> # We will initialize an empty `set` and\
|
142 |
+
\ fill up the tokens of our interest as we proceed in this section. >>> key_tokens\
|
143 |
+
\ = [] # => currently 'available' token doesn't have anything to attend Nearby\
|
144 |
+
\ tokens should be important because, in a sentence (sequence of words), the current\
|
145 |
+
\ word is highly dependent on neighboring past & future tokens. This intuition\
|
146 |
+
\ is the idea behind the concept of sliding attention."
|
147 |
+
example_title: bigbird blog intro
|
148 |
+
- text: 'The majority of available text summarization datasets include short-form
|
149 |
+
source documents that lack long-range causal and temporal dependencies, and often
|
150 |
+
contain strong layout and stylistic biases. While relevant, such datasets will
|
151 |
+
offer limited challenges for future generations of text summarization systems.
|
152 |
+
We address these issues by introducing BookSum, a collection of datasets for long-form
|
153 |
+
narrative summarization. Our dataset covers source documents from the literature
|
154 |
+
domain, such as novels, plays and stories, and includes highly abstractive, human
|
155 |
+
written summaries on three levels of granularity of increasing difficulty: paragraph-,
|
156 |
+
chapter-, and book-level. The domain and structure of our dataset poses a unique
|
157 |
+
set of challenges for summarization systems, which include: processing very long
|
158 |
+
documents, non-trivial causal and temporal dependencies, and rich discourse structures.
|
159 |
+
To facilitate future work, we trained and evaluated multiple extractive and abstractive
|
160 |
+
summarization models as baselines for our dataset.'
|
161 |
+
example_title: BookSum Abstract
|
162 |
inference:
|
163 |
parameters:
|
164 |
max_length: 64
|
165 |
min_length: 8
|
166 |
no_repeat_ngram_size: 3
|
167 |
+
early_stopping: true
|
168 |
repetition_penalty: 3.5
|
169 |
length_penalty: 0.3
|
170 |
+
encoder_no_repeat_ngram_size: 3
|
171 |
+
num_beams: 4
|
172 |
+
model-index:
|
173 |
+
- name: pszemraj/led-base-book-summary
|
174 |
+
results:
|
175 |
+
- task:
|
176 |
+
type: summarization
|
177 |
+
name: Summarization
|
178 |
+
dataset:
|
179 |
+
name: kmfoda/booksum
|
180 |
+
type: kmfoda/booksum
|
181 |
+
config: kmfoda--booksum
|
182 |
+
split: test
|
183 |
+
metrics:
|
184 |
+
- name: ROUGE-1
|
185 |
+
type: rouge
|
186 |
+
value: 33.4536
|
187 |
+
verified: true
|
188 |
+
- name: ROUGE-2
|
189 |
+
type: rouge
|
190 |
+
value: 5.2232
|
191 |
+
verified: true
|
192 |
+
- name: ROUGE-L
|
193 |
+
type: rouge
|
194 |
+
value: 16.2044
|
195 |
+
verified: true
|
196 |
+
- name: ROUGE-LSUM
|
197 |
+
type: rouge
|
198 |
+
value: 29.9765
|
199 |
+
verified: true
|
200 |
+
- name: loss
|
201 |
+
type: loss
|
202 |
+
value: 3.1985862255096436
|
203 |
+
verified: true
|
204 |
+
- name: gen_len
|
205 |
+
type: gen_len
|
206 |
+
value: 191.9783
|
207 |
+
verified: true
|
208 |
---
|
209 |
|
210 |
# Longformer Encoder-Decoder (LED) for Narrative-Esque Long Text Summarization
|