Auto Save

[ines (Ines Montani)]

Thanks!

@taavi

the UI calls “get_questions” before it calls “give_answers”

The very first request always needs to be get_questions, because there needs to be a queue of questions. After that, the app tries to make sure there are always enough questions in the queue so that the annotator never hits a block or needs to wait long for the next batch. Also see my comments on this from earlier in the thread:

@ines

For your scenario, there’s still a more problem that’s more difficult to solve in general: you cannot know how long the requests will take. While the answer is sent back, a new batch will already be requested (also since the queue is empty) and it will most likely arrive before the answer is received, stored in the database and retrieved from there in your stream.

Prodigy tries its best to always make sure that there are enough questions – after all, annotation can be pretty fast and the annotator should never see a “Loading…” message in between. You could probably work around that by just waiting to yield out the next task until you have the previous one – but once you’ve implemented that, you might find that it creates a pretty frustrating annotation exprience.

@taavi

By default whenever you close the browser or refresh, examples that were previously shown are lost forever, since the stream will just pull the next one

Yes, in that case (at least if you want to handle everything in a single session), you probably want your stream to be an infinite loop that keeps repeating the stream until all examples are confirmed to be in the dataset. See here for an example.