mirror of
https://github.com/explosion/spaCy.git
synced 2024-12-26 09:56:28 +03:00
Typo fix in Language.replace_listeners
docs (#12823)
* modified: spacy/language.py - corrected typo in docstring for :method:`Language.replace_listeners` - added noqa comment on unused local variable assignment in :method:`Language.from_config` as I wasn't sure if it should be unassigned modified: website/docs/api/language.mdx - corrected typo in `Language.replace_listeners` markdown * modified: spacy/language.py - removed noqa comment --------- Co-authored-by: Ian Thompson <ian.thompson@hrblock.com>
This commit is contained in:
parent
0566c3a166
commit
ef20e114e0
|
@ -1958,7 +1958,7 @@ class Language:
|
||||||
useful when training a pipeline with components sourced from an existing
|
useful when training a pipeline with components sourced from an existing
|
||||||
pipeline: if multiple components (e.g. tagger, parser, NER) listen to
|
pipeline: if multiple components (e.g. tagger, parser, NER) listen to
|
||||||
the same tok2vec component, but some of them are frozen and not updated,
|
the same tok2vec component, but some of them are frozen and not updated,
|
||||||
their performance may degrade significally as the tok2vec component is
|
their performance may degrade significantly as the tok2vec component is
|
||||||
updated with new data. To prevent this, listeners can be replaced with
|
updated with new data. To prevent this, listeners can be replaced with
|
||||||
a standalone tok2vec layer that is owned by the component and doesn't
|
a standalone tok2vec layer that is owned by the component and doesn't
|
||||||
change if the component isn't updated.
|
change if the component isn't updated.
|
||||||
|
|
|
@ -856,7 +856,7 @@ token-to-vector embedding component like [`Tok2Vec`](/api/tok2vec) or
|
||||||
training a pipeline with components sourced from an existing pipeline: if
|
training a pipeline with components sourced from an existing pipeline: if
|
||||||
multiple components (e.g. tagger, parser, NER) listen to the same
|
multiple components (e.g. tagger, parser, NER) listen to the same
|
||||||
token-to-vector component, but some of them are frozen and not updated, their
|
token-to-vector component, but some of them are frozen and not updated, their
|
||||||
performance may degrade significally as the token-to-vector component is updated
|
performance may degrade significantly as the token-to-vector component is updated
|
||||||
with new data. To prevent this, listeners can be replaced with a standalone
|
with new data. To prevent this, listeners can be replaced with a standalone
|
||||||
token-to-vector layer that is owned by the component and doesn't change if the
|
token-to-vector layer that is owned by the component and doesn't change if the
|
||||||
component isn't updated.
|
component isn't updated.
|
||||||
|
|
Loading…
Reference in New Issue
Block a user