# Training NER model with prodigy

**URL:** <https://support.prodi.gy/t/training-ner-model-with-prodigy/3306>\
**Category:** Uncategorized\
**Tags:** usage, ner, spacy\
**Created:** [August 19, 2020, 2:31pm UTC](https://support.prodi.gy/t/training-ner-model-with-prodigy/3306 "2020-08-19T14:31:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mihaivinaga](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/mihaivinaga/32/1180_2.png) [@mihaivinaga](https://support.prodi.gy/u/mihaivinaga)\
**Post date:** [August 19, 2020, 2:31pm UTC](https://support.prodi.gy/t/training-ner-model-with-prodigy/3306/1 "2020-08-19T14:31:32Z")

</div>

Hello,

We are a company that uses prodigy for our tagging and training of NER models. I have two questions regarding the usage of prodigy:

1. Is there a way to test which parameters are best suited for a certain dataset when training it. Does prodigy have a tool in which we specify a dataset and after running a command it lets you know what are the best values for parameters like **losses** or **batch size**
2. prodigy seems limited when it comes to customising the way you train your model, I was wondering what do you guys recommend when training a model for production, prodigy or a python script?

Thanks you @ines for your support and patience!

---

<div class="post-metadata">

**Author:** ![honnibal](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/honnibal/32/35_2.png) [@honnibal](https://support.prodi.gy/u/honnibal)\
**Post date:** [August 21, 2020, 12:11pm UTC](https://support.prodi.gy/t/training-ner-model-with-prodigy/3306/2 "2020-08-21T12:11:30Z")

</div>

Hi @mihaivinaga,

It's always difficult to decide where to limit the scope of a tool. On the one hand, it's useful to do things in one place rather than assembling a workflow out of many pieces, and so it's tempting to put in features that a high percentage of users will use in their workflows. But on the other hand, it's good for tools to stay more limited, as no one tool can be the best at everything.

For hyper-parameter optimisation, we see this as a topic that's continuing to develop, and it's also one that requires integration into a remote execution environment, because you want to use multiple machines to execute the hyper-parameter search in parallel. We therefore have not implemented any hyper-parameter search into Prodigy. We recommend exploring Polyaxon and Ray as different approaches to hyper-parameter tuning and experiment management. [Polyaxon](https://polyaxon.com) is more of a full-featured environment, while [Ray](https://ray.io) is a smaller tool that gives you primitives to code solutions yourself.

The `prodigy train` command was shaped by similar considerations. We did decide it was worth the convenience to have a simple train command to train directly from the database. But we haven't tried to cover every use-case, and you can easily replace the command with your own scripts (or export your data using `data-to-spacy` and train with `spacy train` directly). We recommend doing that for many situations, for example running training tasks under automation, which would normally be the right process for production deployments.