Difference between revisions of "Plot comparison"

From Octave
Jump to navigation Jump to search
(update page01-03)
Line 43: Line 43:
 
* [http://josoansi.de/octave_plot_compare/compare_plot_demos_01.html#area_01 area_01: Different colors, white vertical lines in FLTK/Qt]
 
* [http://josoansi.de/octave_plot_compare/compare_plot_demos_01.html#area_01 area_01: Different colors, white vertical lines in FLTK/Qt]
 
* [http://josoansi.de/octave_plot_compare/compare_plot_demos_01.html#cmpermute_01 cmpermute_01: No plot]
 
* [http://josoansi.de/octave_plot_compare/compare_plot_demos_01.html#cmpermute_01 cmpermute_01: No plot]
* [http://josoansi.de/octave_plot_compare/compare_plot_demos_01.html#colorbar_23 colorbar_23: xtick unreadable. It should check the text_extent and reduce xticks if the xlabels would overlap]
+
* [http://josoansi.de/octave_plot_compare/compare_plot_demos_02.html#colorbar_23 colorbar_23: xtick unreadable. It should check the text_extent and reduce xticks if the xlabels would overlap]
 
* [http://josoansi.de/octave_plot_compare/compare_plot_demos_01.html#colorbar_01 colorbar_01: This is just a matter of taste but I (Andy1978) would prefer a  smaller gap (only 40% of the current implementation?) between colorbar and the plot like matlab does]
 
* [http://josoansi.de/octave_plot_compare/compare_plot_demos_01.html#colorbar_01 colorbar_01: This is just a matter of taste but I (Andy1978) would prefer a  smaller gap (only 40% of the current implementation?) between colorbar and the plot like matlab does]
  

Revision as of 08:05, 16 July 2016

Visual comparison of plot files from http://josoansi.de/octave_plot_compare/compare_plot_demos_01.html until compare_plot_demos_0_08.html

You can find the scripts which are used to create these plots in scripts/testfun/private.

FLTK, Qt

gnuplot

FLTK, Qt, gnuplot

Matlab errors due to incompatibilities


old results, should be rechecked and merged

  • shrinkfaces_04: shows "inverted?/outer faces", completly different from matlab
  • text_03: can't print multi-line text objects bug#31468
  • colorbar_20: Latex label 10^{2}, 10^{1.5} not in print output. See bugs #42988, #42320, #42340 which are mostly duplicates

gnuplot only differences

There are a lot of gnuplot differences and it might be nice to fix those, but someone would have to take an interest. Octave is moving towards OpenGL for all plotting so most developers focuses on bug fixes for that toolkit.

Nevertheless here are some visual gnuplot ONLY problems which need some attention:

  • fill_03: unusable
  • ezsurf_02: distorted despite "axis equal"
  • isosurface_01: wrong scale, edges missing
  • trimesh_01: invisible lines bug#42561. FLTK plot is fine.
  • zlim_03: Warning/Error "line 0: *All* edges undefined or out of range, thus no plot." and an empty plot (as announced). FLTK plot is fine.

won't fix or Octave only feature

  • fltk/ML axis_09, axis_10, axis_11, axis_12, axis_13: No, [x,y]axislocation' 'zero' (http://savannah.gnu.org/bugs/?40588). This is an Octave (and gnuplot) only feature. We can either blacklist, or visually skip over the comparison since it is blank for Matlab. Perhaps should be removed from demos or blacklist axis_09 in dump.m script
  • matlab comet3_01, comet.png: Only the beginning of the animation is printed. Matlab implements comet in a completely different way which means printing isn't really possible for them.
  • matlab polar_03, polar_05: Modifying ticks for rho (rticks) and theta (tticks) is an Octave addition.
  • matlab polar_04: Modifying color and text properties in polar plot is an Octave addition.
  • Multiple Matlab plots with "Error in color/linetype argument". This is because adding legend keys with ";" in plot like "plot(1:10, "; a ramp;)" is an Octave only addition.