-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make AI Model Training work with tasks #8265
Comments
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. |
Maybe add a warning for each unfinished task? This way we can allow both and thus this feature is more flexible 🤔 |
I would vote to only use finished instances (and show a warning that there are x unfinished instances that are not used). It usually does not make sense to use unfinished training data. |
Sadly, the worker needs adjustments as the bounding boxes collected by the frontend are not passed to the job and thus the worker collect the bounding boxes itself. Edit: Therefore, the worker now needs to be adjusted to also include the task bounding box when collecting the bounding boxes |
But the worker previously collected the bounding boxes as well. Or is the needed change that the |
Yes, that is what I meant. Sorry for being unclear here 🙈 |
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: