Are you computing your bucketSize value from (max - min) / 7? You might want to round that result.
You say you only have problems with some charts, but you haven't said what rendering errors you are referring to. What do you expect it to look like? Could you set up a simple example on jsfiddle so we can be talking about the same thing, data included? Thanks. On Mon, Feb 26, 2018 at 2:23 PM, Nick Laviola <[email protected]> wrote: > Hi Daniel, thanks for the quick reply. I gave that a shot > (*google.charts.load('upcoming', > {packages: ['corechart']});*) but I'm still seeing the same rendering > issue. Here are my current chart options if that gives any insight: > var options = { > title: deviceLetter + ' device ' + testName + ' > values', > legend: { position: 'none' }, > colors: [chartColors[deviceLetter]], > height: 360, > histogram: { > bucketSize: bucketSize, //computed bucket size > minValue: min, //set by user > maxValue: max //set by user > }, > hAxis: {format: '0.0E00', title: testName} > }; > > > > On Monday, February 26, 2018 at 10:57:24 AM UTC-8, Daniel LaLiberte wrote: >> >> Hi Nick, >> >> Have you tried the 'upcoming' version? There are many changes in the >> axis ticks, but I am not sure how this might have impacted the histogram. >> >> On Monday, February 26, 2018 at 1:51:58 PM UTC-5, Nick Laviola wrote: >>> >>> I have a page displaying a series of histograms that all need to have >>> the same number/size of buckets for easy comparisons. When I specify >>> bucketSize however, I get rendering errors on some the charts: >>> >>> >>> <https://lh3.googleusercontent.com/-p4rBFVCODww/WpRW7AVSPJI/AAAAAAAAAdg/6D86hEMK_xELenXzGeCYC4orqIUW6Jw9gCLcBGAs/s1600/Screen%2BShot%2B2018-02-26%2Bat%2B10.45.43%2BAM.png> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> I can remedy this by setting the *hAxis: {type: 'category'} *option, >>> however this then prevents me from setting a number format for the hAxis >>> ticks. I've tried reverting to earlier versions of the corechart, but to no >>> avail. >>> >>> Has anyone else experienced this problem? Can we possibly have this >>> looked at for future versions? >>> >> -- > You received this message because you are subscribed to the Google Groups > "Google Visualization API" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to google-visualization-api@ > googlegroups.com. > Visit this group at https://groups.google.com/ > group/google-visualization-api. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/google-visualization-api/98242b7f-dc84-452b-953b- > f99c17af18de%40googlegroups.com > <https://groups.google.com/d/msgid/google-visualization-api/98242b7f-dc84-452b-953b-f99c17af18de%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2> [email protected] <[email protected]> 5CC, Cambridge MA -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-visualization-api. To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJMTV9TTYC%2BuPd_w8eTsJxixwAse-vRbspzK1qQBbE4Wbg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
