Open unclebinary1001 opened 1 year ago
Thanks for bringing this up. We're double checking and looking into it. Please continue on and we'll get back to you shortly
@unclebinary1001 You are right, looks like a float
/Float
doesn't have enough precision and we get the wrong expected value back. Thanks for catching this. I'll add it to our change log and push up a fix. Though it is late in the competition, hopefully this will help others working in Java too.
Sounds good.
I believe something similar may be happening in Test Set 3 for Test 11.
the
getTotalClaimCostForDisaster
method is of float data type so accuracy does not match expected value in TestSet2 sotest4_getTotalClaimCostForDisaster
fails forgetTotalClaimCostForDisaster(56).
I tried changing
estimate_cost
data type in Claim.java and the return types of the methods that depend on it fromFloat
toDouble
. This fixes the test and it works expected