HuguesTHOMAS / KPConv-PyTorch

Kernel Point Convolution implemented in PyTorch
MIT License
782 stars 155 forks source link

Toronto3D process problems #156

Open GeoSur opened 2 years ago

GeoSur commented 2 years ago

Hello mr.Thomas.Thank you for your wonderful work!!And I have met a new question: I have modified this dataset as the same as s3dis, but when i run the triaing process, it raised "ERROR: It seems that the calibration have not reached convergence. Here are some plot to understand why:If you notice unstability, reduce the expected_N valueIf convergece is too slow, increase the expected_N value" I carefully compared my modified data with s3dis, is this because the xyz coordinate value of my input data is too large?((I have reduced the xyz coordinate value as the dataset instructions, but they are still greater than 100)

Another question: How to select an area for validation? Simply change the validation_split in s3dis?

GeoSur commented 2 years ago

@HuguesTHOMAS Hello, THOMAS! When I run the plot.py, it produced two mIou results like the photo. What does the line on top represent? Maybe the top is the best mIou, and the below is the mean mIou? full_toronto_miou

HuguesTHOMAS commented 2 years ago

So here is what it means:

A few remarks:

GeoSur commented 2 years ago

@HuguesTHOMAS Thank you for your reply! Your description is really helpful! And about the output lines from the plot.py. Is the top line represented the mIou of the last epoch, and the below line represented the whole cloud too?

HuguesTHOMAS commented 2 years ago

Yes indeed: https://github.com/HuguesTHOMAS/KPConv-PyTorch/blob/3a774ff8d54a4d080fe65093b2299ede35d9735d/plot_convergence.py#L374-L413

line 393 = mIou of the last epoch line 408 = mIou of the last saved full cloud

GeoSur commented 2 years ago

@HuguesTHOMAS Haha I missed these, thank you for your reply!!