pszemraj commited on
Commit
1d9bf24
1 Parent(s): 4bd1be6

remove inference

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