Losing tasks while reloading page.

[smanjil (Manjil Shrestha)]

Hi,

I am using ner.manual right now. It loads fine at the first page load.
But, when I hit reload, the page says “No tasks available.”
Is it the normal behavior of prodigy, or is something unusual happening?

Any help would be appreciated.

Thank you!

[ines (Ines Montani)]

How many examples are there in your stream? If your stream only consists of one batch, what you're seeing makes sense – see this thread for background on this:

@ines

Yes, this is currently expected, because on each load, the app makes a request to the server and asks for the next batch (by default, the batch size is 10). The annotated tasks are sent back to the server periodically, so when a new batch is requested, Prodigy can’t yet know whether a question that was previously sent out was already annotated or not. (Annotating all sentences / examples is also a pretty specific goal that only applies to some use cases and data streams.)

If it’s important to you that all sentences are annotated, and you do want to handle cases where the annotator refreshes their browser, you ideally want to reconcile the questions/answers at the end of a session, and compare the _task_hash to find examples in your data that you don’t have an answer for in the dataset. You can either do this in a custom recipe within the stream generator, or as a separate session that you run after the previous one finished.

By default, Prodigy won't just loop over your data infinitely either – because in most cases, this isn't really useful and there should be a clear indicator that all batches have been sent out. But Prodigy's streams are Python generators, so you could just use your own script that re-populates the stream once it's exhausted and pipe that forward into the recipe. See this section on custom loaders for an example.

[smanjil (Manjil Shrestha)]

"batch_size": 1 in "prodigy.json" makes sense