Creating an "ner" object with provided "moves" not possible #10443
Replies: 1 comment 2 replies
-
It looks like the type annotation might be off for that field - it seems like it's supposed to be a list of strings but is annotated as a TransitionSystem, which as the error points out isn't serializable (and thus shouldn't be in a config). To step back a little, is there a reason you aren't just sourcing the component? You should not need to copy components bit by bit like that. If there is some reason you are copying the component, note that if you leave moves empty it will automatically be generated based on your data, which is almost always the right thing to do. Configs in general have default values, so you only need to specify things if you don't like the defaults. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
How to reproduce the behaviour
I'm trying to initialize a copy EntityRecognizer of an old one, but in using the component factory structure we have to provide initialization information through a
config
. I think the critical thing to provide would be the moves and the model, but not sure how to properly provide either.Beta Was this translation helpful? Give feedback.
All reactions