Moving average ignored a value of inf/nan

[emjay73]

Hi, me again.
"Moving average ignored a value of inf/nan "
issue happens again with multi-GPUs!

Would you please take a look at this issue once again?

(prev issue link : #186)
Thanks!

[dbolya]

What was your command used to run this? And are you on the latest master?

[emjay73]

Yes, it was the latest one.
But to make it clear, I just cloned the repository to the newly created folder and changed the coco DB location in the config file so that I can use my own coco DB without moving it to the 'data' folder.
Then I copied the 'weights' folder with the following elements.

After that, I did the following.
export CUDA_VISIBLE_DEVICES=0,1,2,3
python train.py --config=yolact_base_config --batch_size=32

and it failed once again.

[dbolya]

Wow that's quite weird. This is the unmodified base config? I'll see if I can reproduce this on monday.

And just to sanity check, does it happen with 1 gpu?

[emjay73]

As I mentioned above, I changed the coco DB location in the config file so that I can use my coco DB without moving it to the 'data' folder.

Except that, the other values have the default values.
I just started training with the following command.

export CUDA_VISIBLE_DEVICES=0
python train.py --config=yolact_base_config --batch_size=8

I'll let you know what happens.

[emjay73]

Quick related question!
When do you suppose it is trained enough?

[dbolya]

You mean as to what point it the loss shouldn't be able to explode anymore? That should be around epoch 1-2, but evidently it can still explode on epoch 2 as you found. I'm currently testing 4 GPUs on yolact_base_config, I'll let you know if I can reproduce this.

[emjay73]

I trained it roughly for a day and it's safe with a single GPU !

[emjay73]

With second attempt, loss exploded with single GPU :<

[dbolya]

Ok this is an issue, I was able to reproduce this on 4 gpus. I'm currently testing on 1 gpu, but dang everything was working fine with pascal, no idea why it's not working with COCO.

I'll take a deeper look as to why this is happening and see if I can fix it.

[emjay73]

I hope all of those problems that occurred in single/multi GPU cases are originated from the same flaw.
Thanks and plz,
You are my only hope T-T

[emjay73]

And what about gradient clipping?

[dbolya]

Ok sorry about the delay (thanksgiving and all). The single GPU test came back successful and reproduced the mAP in the paper, so I guess the issue may be somewhere else? Now that I'm back, I'll investigate this further.

[emjay73]

OK Thank you for your notice

[dbolya]

An update: I figured out the source of the random infs during training that you see every now and again. Augmentation could actually output detections with 0 bbox area, hence why some things are divided by 0 and thus produce infinity. Since I ignore batches with inf loss, this wouldn't be the cause of the explosion, but it might be boxes with really small area instead that's causing this explosion (since I don't filter those out).

Right now I'm trying out discarding any box with fewer than than 4 pixels of width and 4 pixels of height. I haven't seen a single inf or nan so far, so this looks promising. I'll update you once / if it finishes training.

[emjay73]

That's good news!
And well, it seems like the problem that is not related to the multiple GPUs..?