octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #55481] Plotting differences from Matlab at 5.


From: Rik
Subject: [Octave-bug-tracker] [bug #55481] Plotting differences from Matlab at 5.0 release
Date: Wed, 16 Jan 2019 14:27:28 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko

Follow-up Comment #19, bug #55481 (project octave):

The different colors are a consequence of the dump_demos.m script.  There is
this bit:


 ## Create script beginning (close figures, etc.)
  fid = fopen (mfile, "w");
  fprintf (fid, "%% DO NOT EDIT!  Generated automatically by
dump_demos.m\n");
  fprintf (fid, "function %s ()\n", funcname);
  fprintf (fid, "set (0, 'DefaultAxesColorOrder', ...\n");
  fprintf (fid, "  [ 0.00000   0.00000   1.00000 ;\n");
  fprintf (fid, "    0.00000   0.50000   0.00000 ;\n");
  fprintf (fid, "    1.00000   0.00000   0.00000 ;\n");
  fprintf (fid, "    0.00000   0.75000   0.75000 ;\n");
  fprintf (fid, "    0.75000   0.00000   0.75000 ;\n");
  fprintf (fid, "    0.75000   0.75000   0.00000 ;\n");
  fprintf (fid, "    0.25000   0.25000   0.25000 ]);\n");
  fprintf (fid, "close all\n");
  fprintf (fid, "more off\n");
  fprintf (fid, "diary diary.log\n");


This ensures that we get reproducible results between Octave and Matlab. 
However, Octave has moved to a different ColorOrder.


octave:1> get (0, 'DefaultAxesColorOrder')
ans =

   0.00000   0.44700   0.74100
   0.85000   0.32500   0.09800
   0.92900   0.69400   0.12500
   0.49400   0.18400   0.55600
   0.46600   0.67400   0.18800
   0.30100   0.74500   0.93300
   0.63500   0.07800   0.18400


We could just update the dump_demos.m script with the new values.  I think,
however, that we might have had a reason for doing this because the first
three lines are primary colors of blue, green, and red.  This stark a
difference is easy to spot.

I guess I would advocate doing the experiment and updating the
DefaultAxesColorOrder and then running dump_demos with just one toolkit (qt)
on Linux and see if the result appears visually okay.  If it does then we can
make the change permanently.

I also think that we need to include the viridis colormap and set it as the
default colormap.  The default used by Matlab is similar to viridis, but not
identical.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55481>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]