Replies: 2 comments 13 replies
-
Please try to run this:
Does it produce any warnings/errors? Maybe the path is not writable?
No, this part should work out of the box. These two variables ( |
Beta Was this translation helpful? Give feedback.
-
I found a redundant and wrong setting USER_ID in biigle/build/.env, which should be in biigle/.env (the USER_ID in biigle/.env is correct for biigle:biigle). I remove it, rebuild, got the same error cause for another .pth "faster_rcnn_r50_fpn_1x_coco_20200130-047c8118.pth", then copy it into maia_jobs/, and re-ran training proposals, then it passed the .pth exist check. But now I encounter new fails. (Even the permission seems correct after I modify my fault, the two .pth still need be copied manually into storage/maia_jobs) (I hope that everytime the training proposal failed, we can re-submitt it so that I don't need to delete the job, re-run novelty and re-select the training proposal!) The new error log is quite long, so I paste it as a new file in It seems some internal causes, and I'm not sure what the true problem is. If there is any comments for furthur trial, please let me know. Thanks a lot for your support and help. |
Beta Was this translation helpful? Give feedback.
-
I had upgraded to MAIA 2.0.0 and novelty detection works well. But after that, when training, the maia job soon failed because
Check the php code, it seems will check the file exist:
This 'resnet50-11ad3fa6.pth' acutally can be downloaded, then I downloaded and put it in storage/maia_jobs
But after docker compose restart and re-run this job, it still failed for the same error cause.
I think I may miss some .env setup(? MAIA_MODEL_PATH or MAIA_MODEL_URL?) or other setup configurations I should try? Thanks.
My .env (about MAIA, as the same as .env.example):
Beta Was this translation helpful? Give feedback.
All reactions