Self-intersection Submission Error

Hi,

It seems several participants, including our team, have issues with submission because of the self-intersection error. We tried to check and debug our submission code, but none of them works. It turns out that if we could slightly change your evaluation codes, our submission has no issue. We have created a pull request for this. We would very appreciate if you could review and reflect the change. We are not 100% sure, but this update would at least alleviate some issues of self-intersection during submission.

https://github.com/cmctec/ARCADE/pull/4/commits

Thanks,

Dear organising committee,

Do you have any updates on this issue? We are encountering the same issue with the submission. The error we get is provided below:

Failed shapely.errors.GEOSException: TopologyException: Input geom 0 is invalid: Self-intersection at 169.12019230769232 344.5

Can you please guide us on how to workaround this issue? Any guidance will be greatly appreciated.

Many thanks and

Best regards, Bilal

Dear @inqlee0704,

It seems that the organising committee has been taking a while to address this matter. I was wondering if any other participating team has managed to resolve the issue on their end. If so, it would be greatly appreciated if someone could share their findings with us.

Thank you, Bilal

Dear participants, Thank you for you interest in this challenge! We will review your failed submissions with this error message and guide you how to avoid it, or, if necessary, will change the evaluation script. However, we can't accept pull request as portions of code you would like to delete are required to avoid other possible errors. Mainly, two possible reasons of this error: 1) your predictor didn't produce proper polygon on its output, so that when converting coordinates of polygon to Polygon class object it returns an error, if still no error, it may return an error when trying to analyze the region of intersection of two polygons.
2) even if your polygon is correct, it may be of shape, where it intersects itself, and when converting to Polygon object or when analyzing the intersection with other polygons it may return an error.However, we intended to solve that problem by buffering your polygon, bu it seems, there is still a problem with that. So my advice for now: 1) check your polygons for correctness, 2) make sure coordinates are in COCO format, 3) try to analyze each shape with error by executing the available code on github, and printing each step, then change your polygons properly Please also wait, we will analyze your submitted results, and hopefully will get back to you with solutions. Thanks again!

Dear @abulegenov,

Thank you for such a detailed explanation. Hopefully, this will be resolved eventually. I am looking forward to a solution for our submission.

Much appreciated.

Many thanks and Best regards, Bilal

Dear Organizing Committee,

Can you please provide some guidance or code examples to avoid the self-intersection error? We are currently stuck with this error and can't proceed with the work.

We will greatly appreciate your help on this.

Many thanks and Kind regards, Bilal

Hello dear friend @inqlee0704 @bilalUWE @abulegenov

I am facing the same issue as you, we also tried to check and debug our commit code but it didn't work, the error is as below: Failed shapely.errors.GEOSException: TopologyException: Input geom 0 is invalid: Self-intersection at 116.03408266860043 191.3183466279913 I see that you have successfully submitted and received an objective F1 score in the submission screen, how did you resolve this issue, any guidance would be appreciated!

Thanks!

Hello @Tom_and_Jerry,

Just made three submissions and each one failed because of the self-intersection error.

@Organizing committee: Can you please prioritize this request?

Thanks!

Dear @Tom_and_Jerry,

We have not figured out the issue. We have submitted several times, and luckily some submissions didn't have the issue :(

Best, In Kyu

Dear @bilalUWE, @inqlee0704, @TomandJerry, and other participants encountering this issue! We would like thank you for your patience! Coming to your issue, it turns out there was slight mistake in evaluation code, where it assumed to have valid shapely polygon so that it could make operations on it., when in reality it was not. We have checked several of your failed submissions, and after this change in code, Your submissions now should give correct results. If you have further questions, please let us know!