Click here to Skip to main content
15,880,956 members

Comments by creizlein (Top 32 by date)

creizlein 24-May-18 0:02am View    
thanks for the tip! i will check it out
I do still to find a place to store the objects anyways, so the approach of using an arraylist to store the objects and cross-reference them with the x/y cell is about the same as databinding
creizlein 7-May-18 18:43pm View    
I have updated the question with a lit bit more of context, hoping it makes more sense now.
creizlein 7-May-18 18:43pm View    
I have updated the question with a lit bit more of context, hoping it makes more sense now.
creizlein 7-May-18 18:43pm View    
I have updated the question with a lit bit more of context, hoping it makes more sense now.
creizlein 7-May-18 18:42pm View    
Thanks everyone for their inputs. I have been reading about statistics but I am still not certain of what is the Math approach i should use.

To give this a little bit more sense and context, I am trying to summarize a datalog from a car, each "frame" or "entry" comes with a RPM value , which of course varies from 0 to 8000, i get thousands of those records and I need to represent them in a rpm table and the amount of hits each "fixed" index has received.

In a practical example, lets assume we got the following values to process

{10,50,90,50,10,400,450,300,550,900,950,1100,1200,1000,900}

rpm | hits
-----|---------
100 | 5 hits
500 | 4 hits
1000 | 6 hits

In this example I have kind of grouped similar numbers for the sake of simplicity, I do know how to calculate the hits, and to find out to which "index" each value should go, but what i need to find out first is what are the best indexes for the table.
I have created those 3 indexes (100,500,1000) fixed, but I don't know if those are the best indexes to split my numbers, it might be 500 or 400 or 474, who knows.

That is the situation i am debating on how to be done, how do you find the best indexes, which can even vary, they could be just 3 or could be 10 or N , the user will have the input to "subdivide" the indexes in the amount they wish.

Hope it is making a little bit more of sense now.