Closed byfate closed 3 years ago
I check my code several times,and follow your adivce(ge, weight loss cv2.points),would your please help me when you are convenient?Hope you can point out my problem if you are convenient,appreciate
Wait, you get 77.8 on DOTA's testing set? Input is 0.5 and 1 scale with 600x600 crop?
Wait, you get 77.8 on DOTA's testing set? Input is 0.5 and 1 scale with 600x600 crop?
Sorry,its HRSC dataset,I didn't mention it .
Oh, I see. The batch size would matter, I used about 100 epochs for HRSC2016. The codes look good to me. I think the current mAP means your code is good too.
OK, looks like that I haveto rent some gpu to see if the map can be higher.when the result come out, I will tell you .thanks for your replying.
No problem.
No problem.
when I change the baseline method's learning rate as *1.0e-4,the batch size is 12 ,using two 2080ti. the highest map** is 83.6,but it is not stable during 100 epoch,and I observe the confidece of the box, lots of box confidence are not high.
what is really strange is when I run the baseline method using 1 Tesla V100 ,learning rate *1.25e-4,batch-size 20*the hightest map is about 77.7%(only in one card which has 32gm video card),and when I change the batch-size to 12 ,learning rate 1.0e-4,its highest map is 83.7%,also the traing process is not stable,it's hard to get the highest map depending on batch-size and learning rate.
It seems that I need to adjust different learning rate and batch-size during traing. In all,thanks for you kind replying.appreciated.
Thank you for your report. I'm thinking maybe the Cuda or library matters, the newest GPU would not be greatly supported. Just guess... But I agree learning rate does matter when the batch size is small in the backpropagation.
Thank you for your report. I'm thinking maybe the Cuda or library matters, the newest GPU would not be greatly supported. Just guess... But I agree learning rate does matter when the batch size is small in the backpropagation.
OK,thank you.
final: Map 77.8%
final loss. about range in [2.1,2.3] (run several times)
batch_size 12;two 2080 gpu other parameter as main.py
nochange ctrbox_net.py change nothing, didn't clamp the angle value range [-9-,0]
just use the same code as the BBAvector method
change decoder.py
ctdet_decode changeto ctdet_decode_base
didnot change much,just add angle heatmap
loss.py
I follow you reply,and the weigh loss is used.
and I clamp the angle heatmap to [-90,0]
func_utils.py
change function decode_prediction to function decode_prediction_new_base
1 I follow your advice using cv2.points instead of using my own affine.
and I clamp the cordinates to [0,input_w/input_h]
So in the function write_results, I use the modified decode_prediction_new_base