My data only has 5 columns and only 2 objectives, but what I am finding is that if the objective values are floats (eg. 12.62) then the Tradeoff Analytics widget starts to struggle (and goes into a spin) when I have six or more options. Fewer options then its ok, it doesn't matter which of the seven I take out, so its not value specific, just the quantity of floats that it has to deal with. So somewhere between (2 objectives x 5-6 options) 10-12 float numbers that it has to work with.
If I change all the values into integers then it is OK, its just a floats that it struggles with.
Answer by DavidAmid (644) | Jul 09, 2015 at 03:14 AM
We are not aware of such behaviour. In fact I have many examples with more options and more columns and all are float. Could you share your json here or send it to davida-at-il.ibm.com
Also if you can share the browser you are using
In this case - Chrome Version 43.0.2357.130 m
After some offline discussions, I pasted my json into the sample app, and it works there. So there is something else in my code that is causing the problem. I need to investigate.
Tradeoff analytics 503 Service Unavailable status code when calling show() method from client 2 Answers
Tradeoff Analytics Widget: 10 $digest() iterations reached. Aborting! 1 Answer
Multiple values for key option in Watson TradeOff Analytics 2 Answers
IBM Watson Tradeoff Analytics- Payload Size 1 Answer
Tradeoff Analytics demo page get error "Error: xhrFailed". 7 Answers