Skip to content
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

unable to autoTrain #9

Open
GallonDeng opened this issue Oct 24, 2019 · 1 comment
Open

unable to autoTrain #9

GallonDeng opened this issue Oct 24, 2019 · 1 comment

Comments

@GallonDeng
Copy link

Hi, I set the "numImages_autotrain" to a small number(i.e., 5) to test the autoTrain function. My system is Ubuntu 16.04 and all the aide modules run on a single machine with one AIworker for detection task. But the autoTrain only ran once and never restart even new annotations were completed. It showed the trainning completed and task completed.
Then I mannually started trainning process and it worked a few times but would get stuck if I restart the process (annotaion and then training) again. The status would be kept "PENDING" not "SUCCESS"

@bkellenb
Copy link
Collaborator

Hi,

Apologies for the delayed response. The "PENDING" message is usually down to the server engine (Gunicorn) spawning multiple threads. Essentially, the job gets scheduled and sent to an AIWorker by one thread, but potentially not broadcast to other, new threads. This only affects the status messages for the GUI, not the actual training, and we are working on a fix for it for the next release.

In the meantime, the default implementations of e.g. RetinaNet should print to the command line while training, so if you have the terminal window of the AIWorker open, you should see the training messages accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants