Day 1: Basic Statistics - A Warmup
-
-
mfry 9 years ago I am not sure its the precision of the mode, or any precision is the issue. I double checked how my language performs rounding and found out it uses banker's rounding. I changed this to the standard round half up, but that did not fix problem #4.
-
nicocai 9 years ago I had problem with #4 before and I get it now: it can only be two probs: 1) you print the mode as float which actually can only be int; 2) when you have more than one mode you need to print the smallest one: like in 1 1 2 2 3 4 5, you need to print only 1.
-
cgira 9 years ago I think my code does that but still #4 can't pass: 1) I corrected my code to return mode as an integer 2) Here is how i find the mode: (i) Generate a list of tuples as (integer, frequency), (ii) sort tuples by frequency then by integers in ascending way, (iii) return "integer" of the first tuple.
-
nicocai 9 years ago I am thinking maybe there is something concerning in your (ii), where do you make sure that the after sorting by integers, you still maintain the order of frequency?
-
-
-
-
vinays0116 9 years ago mode must be an integer not a double value. i dont think precision of mode is the issue here rather there must be something wrong in calculation of mode. did u verufy the code for all possible inputs?
-
coolrohan123 9 years ago Yes I did, the rest three cases are fine. Just the last one is failing
-
-
same for for me but I suspect the precision. Especially on the mode. For example, on testcase #1, when I print it as 4978.0 it testcase 1 fail but when I force it to be 4978 (using {0:.0f}), testcase #1 succeeds.
Add Reply Preview cancel