You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow to specify task IDs instead of annotation IDs as the training data source. To do this I think it would be easiest to look up the (or are there multiple?) annotation ID for a specific task ID and continue to use that. This way, no changes in the worker should be needed. (@fm3 Could you comment on whether that's possible?)
Take into account task bounding boxes and not only user bounding boxes
Context
Specific to long-running jobs (set jobsEnabled=true in application.conf)
Training data for model trainings is often created using tasks. It should be possible to start a training from these.
The text was updated successfully, but these errors were encountered:
Sounds good! Yes, there may be multiple annotation ids per task. We should also decide if only “finished” instances should be used, or also “active” ones.
Detailed Description
As far as I can see two things are missing:
Context
jobsEnabled=true
inapplication.conf
)Training data for model trainings is often created using tasks. It should be possible to start a training from these.
The text was updated successfully, but these errors were encountered: