ma-laforge

Thanks for that tidbit. It might be a bug with the algorithm for "F1 acceleration". You can disable F1 acceleration by adding the following to your `~/.juliarc` file: ``` DEFAULTS_INSPECTDR...

Great. That's good to know. The problem is in the `_reduce()` function in src/datasets.jl. The F1 acceleration algorithm is known not to be rock solid (see comment): ``` #FIXME: improve...

@rafaqz: BTW, I know disabling F1 acceleration slows things down significantly for large datasets (easily 2-10x for GBs of data)... but is it still faster than GR/plotly? Just curious.

Update: Just added a failsafe that will fall back to plotting with naive solution if code for F1 acceleration crashes (no need for premature de-optimization with `:droppoints => :never`). -...

Go ahead and try a `Pkg.update()` to see if the failsafe is ok: You should now get a warning message, but still get a (slowly generated) plot when the algorithm...

That does sound like a very good argument - even if I wasn't initially looking at it that way. I admit, I'm not 100% certain on how to do this......

Fixed in https://github.com/ma-laforge/InspectDR.jl/commit/b869eae6b178683a12a22f3d36d8344a35641cfb Waiting to tag a release.

Yes. Thanks.

Hi @tbreloff, Part of Plots: Cool :). **Targeted application** As described on the README, I often need to look at simulation results, in order to understand circuit behaviour. I find...

I have no problem with that, but also feel free to write it in your own words. I like your section on backends - expecially the table "For the impatient"....