Dear Zindians,
Some competitors have raised the fact that the predicted value is float, however it should be an integer since we counting the number of a given object. That is perfectly understandable. However, we recommend keeping you predicted values as they are. No rounding should be done.
"Rounding or setting thresholds in your submission is not allowed and will lead to disqualification in code review."
Best,
Joel
Again. I'm against this rule. In this challenge it is "NATURAL" to round prediction. But for transparency @Zindi can request original predictions for top performers. It sounds dogmatic to me....
In a challenge where the given annotation is integer, even the polygon-based annotation covers multiple objects. The logical way to post-process is rounding, but @Zindi will never fail to amaze me with irrational rules, as there is nothing like a non-rounded number of objects.
Honestly I would have expected rounding to be allowed in this , since we cannot have a float solar panel counts. Thresholds being banned makes absolute sense but rounding should be allowed to be fair
Deleted