plplot-devel — Technical discussion about PLplot development

Re: [Plplot-devel] The wxwidgets device driver speed/idle time

[Alan W. I. <ir...@be...>]

On 2016-11-15 22:52-0000 p.d...@gm... wrote:

> Hi Alan, Laurent
> I can't say I have much to add. It wasn't obvious to me where the lag was last time i looked, but I agree it is an issue
>

> I haven't done much plplot work for some time, but when I can i will
look at this. If anyone has any suggestions I would be keen to hear.

Hi Phil:

>From what you say above it sounds like any serious time you can spend
on this would be pretty limited and not immediate.  Given those
conditions, I think that likely the most valuable thing you can do for
us immediately is to write up a paragraph or so describing how you are
currently using IPC to communicate between -dev wxwidgets and
wxPLViewer including a summary of where waits might be occurring. I
suggest you commit that overview in the new file
drivers/README.wxwidgets_IPC (or I will do that if you just want to
send your overview by e-mail). That IPC overview would be a big help
in getting up to speed for anyone else wanting to figure out what is
going on with these weird idle times that we are encountering on the
Linux platform.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

Re: [Plplot-devel] The wxwidgets device driver speed/idle time

[<p.d...@gm...>]

Hi Alan, Laurent
I can't say I have much to add. It wasn't obvious to me where the lag was last time i looked, but I agree it is an issue

I haven't done much plplot work for some time, but when I can i will look at this. If anyone has any suggestions I would be keen to hear.

Phil 

Sent from my Windows 10 phone

From: Alan W. Irwin
Sent: 15 November 2016 21:22
To: Laurent Berger
Cc: PLplot development list
Subject: Re: [Plplot-devel] The wxwidgets device driver speed/idle time

On 2016-11-15 14:59+0100 Laurent Berger wrote:

> Hi Alan,
>
> I haven't got qt installed.
> My results looks like yours results :
>
> lb@mp12-lb:~/plplot.git/examples/c++$ time ./x01 -dev wxwidgets -np
> PLplot library version: 5.11.1
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103: 
> Having multiple values in <test> isn't supported and may not work as expected
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 138: 
> Having multiple values in <test> isn't supported and may not work as expected
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103: 
> Having multiple values in <test> isn't supported and may not work as expected
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 138: 
> Having multiple values in <test> isn't supported and may not work as expected
>
> real    0m0.407s
> user    0m0.108s
> sys    0m0.016s
> lb@mp12-lb:~/plplot.git/examples/c++$ time ./x01 -dev wxwidgets -np
> PLplot library version: 5.11.1
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103: 
> Having multiple values in <test> isn't supported and may not work as expected
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 138: 
> Having multiple values in <test> isn't supported and may not work as expected
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103: 
> Having multiple values in <test> isn't supported and may not work as expected
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 138: 
> Having multiple values in <test> isn't supported and may not work as expected
>
> real    0m10.997s
> user    0m0.064s
> sys    0m0.040s
> lb@mp12-lb:~/plplot.git/examples/c++$ time ./x01 -dev xwin -np
> PLplot library version: 5.11.1
>
> real    0m0.122s
> user    0m0.056s
> sys    0m0.020s
> lb@mp12-lb:~/plplot.git/examples/c++$ time ./x01 -dev xwin -np
> PLplot library version: 5.11.1
>
> real    0m0.122s
> user    0m0.060s
> sys    0m0.016s
> lb@mp12-lb:~/plplot.git/examples/c++$ time ./x01 -dev xcairo -np
> PLplot library version: 5.11.1
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103: 
> Having multiple values in <test> isn't supported and may not work as expected
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 138: 
> Having multiple values in <test> isn't supported and may not work as expected
>
> real    0m0.125s
> user    0m0.088s
> sys    0m0.016s
> lb@mp12-lb:~/plplot.git/examples/c++$ time ./x01 -dev xcairo -np
> PLplot library version: 5.11.1
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103: 
> Having multiple values in <test> isn't supported and may not work as expected
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 138: 
> Having multiple values in <test> isn't supported and may not work as expected
>
> real    0m0.128s
> user    0m0.084s
> sys    0m0.020s
> lb@mp12-lb:~/plplot.git/examples/c++$

Hi Laurent:

Thanks very much for the above report.

Your timing results verify mine and show that -dev wxwidgets sometimes
has very poor "real" timing results even though the actual cpu times
indicated by the sum of "user" + "sys" are quite fast and consistent.

For this case

> real    0m10.997s
> user    0m0.064s
> sys    0m0.040s

the sum of user + sys is 0.104 seconds so that means for this test the
cpu was idle for 10.893 seconds out of the 10.997 seconds or 99.05 per
cent of the time which is equivalent to two (!) orders of magnitude
slowdown.  Since your results and mine confirm the problem for a wide
range of Linux kernel versions, my working hypothesis is these
excessive idle times/slowdowns are due to the inefficient way that
Linux kernel IPC is being used to implement the necessary two-way
communication between -dev wxwidgets and the wxPLviewer application on
Linux.

Gaining two orders of magnitude in speed is certainly an attractive
goal for the wxwidgets device/wxPLviewer combination so I am tempted
to immediately start reviewing the Linux kernel IPC use between -dev
wxwidgets and wxPLviewer.  However, my current knowledge of Linux
kernel IPC is small, and I have many other PLplot issues on my plate
at the moment so I will have to delay this for quite a while.  Thus,
there is an opportunity for someone else to contribute substantially
here if they have some knowledge about the most efficient way to use
Linux kernel IPC or want to learn more about that interesting topic.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

------------------------------------------------------------------------------
_______________________________________________
Plplot-devel mailing list
Plp...@li...
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Re: [Plplot-devel] The wxwidgets device driver speed/idle time

[Alan W. I. <ir...@be...>]

On 2016-11-15 14:59+0100 Laurent Berger wrote:

> Hi Alan,
>
> I haven't got qt installed.
> My results looks like yours results :
>
> lb@mp12-lb:~/plplot.git/examples/c++$ time ./x01 -dev wxwidgets -np
> PLplot library version: 5.11.1
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103: 
> Having multiple values in <test> isn't supported and may not work as expected
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 138: 
> Having multiple values in <test> isn't supported and may not work as expected
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103: 
> Having multiple values in <test> isn't supported and may not work as expected
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 138: 
> Having multiple values in <test> isn't supported and may not work as expected
>
> real    0m0.407s
> user    0m0.108s
> sys    0m0.016s
> lb@mp12-lb:~/plplot.git/examples/c++$ time ./x01 -dev wxwidgets -np
> PLplot library version: 5.11.1
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103: 
> Having multiple values in <test> isn't supported and may not work as expected
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 138: 
> Having multiple values in <test> isn't supported and may not work as expected
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103: 
> Having multiple values in <test> isn't supported and may not work as expected
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 138: 
> Having multiple values in <test> isn't supported and may not work as expected
>
> real    0m10.997s
> user    0m0.064s
> sys    0m0.040s
> lb@mp12-lb:~/plplot.git/examples/c++$ time ./x01 -dev xwin -np
> PLplot library version: 5.11.1
>
> real    0m0.122s
> user    0m0.056s
> sys    0m0.020s
> lb@mp12-lb:~/plplot.git/examples/c++$ time ./x01 -dev xwin -np
> PLplot library version: 5.11.1
>
> real    0m0.122s
> user    0m0.060s
> sys    0m0.016s
> lb@mp12-lb:~/plplot.git/examples/c++$ time ./x01 -dev xcairo -np
> PLplot library version: 5.11.1
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103: 
> Having multiple values in <test> isn't supported and may not work as expected
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 138: 
> Having multiple values in <test> isn't supported and may not work as expected
>
> real    0m0.125s
> user    0m0.088s
> sys    0m0.016s
> lb@mp12-lb:~/plplot.git/examples/c++$ time ./x01 -dev xcairo -np
> PLplot library version: 5.11.1
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103: 
> Having multiple values in <test> isn't supported and may not work as expected
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 138: 
> Having multiple values in <test> isn't supported and may not work as expected
>
> real    0m0.128s
> user    0m0.084s
> sys    0m0.020s
> lb@mp12-lb:~/plplot.git/examples/c++$

Hi Laurent:

Thanks very much for the above report.

Your timing results verify mine and show that -dev wxwidgets sometimes
has very poor "real" timing results even though the actual cpu times
indicated by the sum of "user" + "sys" are quite fast and consistent.

For this case

> real    0m10.997s
> user    0m0.064s
> sys    0m0.040s

the sum of user + sys is 0.104 seconds so that means for this test the
cpu was idle for 10.893 seconds out of the 10.997 seconds or 99.05 per
cent of the time which is equivalent to two (!) orders of magnitude
slowdown.  Since your results and mine confirm the problem for a wide
range of Linux kernel versions, my working hypothesis is these
excessive idle times/slowdowns are due to the inefficient way that
Linux kernel IPC is being used to implement the necessary two-way
communication between -dev wxwidgets and the wxPLviewer application on
Linux.

Gaining two orders of magnitude in speed is certainly an attractive
goal for the wxwidgets device/wxPLviewer combination so I am tempted
to immediately start reviewing the Linux kernel IPC use between -dev
wxwidgets and wxPLviewer.  However, my current knowledge of Linux
kernel IPC is small, and I have many other PLplot issues on my plate
at the moment so I will have to delay this for quite a while.  Thus,
there is an opportunity for someone else to contribute substantially
here if they have some knowledge about the most efficient way to use
Linux kernel IPC or want to learn more about that interesting topic.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

Re: [Plplot-devel] ctest failure with Qt file devices

[Alan W. I. <ir...@be...>]

Hi Hazen:

On 2016-11-15 08:15-0500 Hazen Babcock wrote:

> This is happening with Qt4, specifically:

OK. That very likely means this is our problem and nothing
to do with Qt4.

> [this] command does not segfault:
> ./x02c -dev pngqt -o ex2.png
>
> But it does segfault in family mode:
> ./x02c -fam -dev pngqt -o ex2.png

If I recall correctly example 2 moves through the pages in a unique
but legitimate way that other examples do not use so that may be
triggering this issue for the qt devices.  So I plan to take a look
later when I have finished up some other PLplot issues I am currently
dealing with unless you are able to solve this issue first on your own.

Assuming you do want to investigate further on your own, I would try
compiling with

export CFLAGS="-g"
export CXXFLAGS="-g"

(so the valgrind results properly identify code lines and you can
attach a gdb session (if you like) whenever valgrind finds a memory
management issue.  Then run valgrind (with --db-attach=yes) on example
2 with familying and a variety of qt devices to see if they all have
memory management issues and exactly what part of our qt code is
generating those.  My guess is it is something one or all of our qt
devices does wrong for the end-of-page processing in familying mode
for the unique way example 2 navigates through its two pages.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

Re: [Plplot-devel] libplplottcltk now has a pure redacted API

[Alan W. I. <ir...@be...>]

On 2016-11-15 12:34-0000 Arjen Markus wrote:

> I will run the tests for bare Windows too but I do not expect any problems.
>
>
>>> AM: Indeed, all examples produce identical output (save the ones not ported to Tcl, x34 and x32)

Hi Arjen:

Thanks for this good test of all standard Tcl examples on bare
windows.

Does -dev ntk produce good results on this platform as well?

Alan

__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

Re: [Plplot-devel] libplplottcltk now has a pure redacted API

[Alan W. I. <ir...@be...>]

Hi Arjen:

Thanks for your report.

On 2016-11-15 11:59-0000 Arjen Markus wrote:

> I ran the comprehensive tests for Cygwin and MinGW (no interactive
tests) as well as the interactive comprehensive tests for Cygwin. The
non-interactive tests were perfect for both platforms. But I had some
trouble with the set of interactive tests [....]

> [out of order] The oddities seem to be related to Cygwin and the set-up I use, rather than the redacted Tcl interface.

That sounds promising, and I may have some further comments about
those oddities once I see the tarball report(s) from running
scripts/comprehensive_test.sh that I request below.

I hope "MinGW" is shorthand for MinGW-w64/MSYS2 for the reasons we
have discussed before, but could you confirm that please?

Also, you appear to be having some trouble with the interactive
case and did not report back any *.out results.  Therefore, I have now
changed my mind and would like you to run true comprehensive tests (if
you were not doing that before).  That is, please run
scripts/comprehensive_test.sh and send me the report tarball that
creates to give me all the data I need to make intelligent comments on
your results.  To keep those tests short and to the point of testing
just the Tcl/Tk bindings and examples, I highly recommend the

--cmake_added_options "-DDEFAULT_NO_DEVICES=ON -DPLD_ntk=ON -DPLD_tk=ON -DPLD_tkwin=ON -DPLD_xwin=ON -DPLD_ps=ON -DDEFAULT_NO_BINDINGS=ON -DENABLE_tcl=ON -DENABLE_tk=ON -DENABLE_itcl=ON -DENABLE_itk=ON"

option for scripts/comprehensive_test.sh.  Also, for now, I would
limit it to the shared case for just the build tree (i.e., the test I
requested before from you, but with the better report facilities
provided by this script) using the

--do_nondynamic no --do_static no --do_test_install_tree no --do_test_traditional_install_tree no

script options.

> -        The Cygwin interactive tests ran for some 5 hours - then I interrupted the script. I came across the same tests so many times that I started to suspect an infinite loop. Not sure what to make of it.

As I recall, your previous Cygwin interactive tests were incredibly
slow (because those tests [other than the ones that use -dev ntk] are
all done directly or indirectly with X, and Cygwin X is very slow). So
5 hours might be typical if you are running all our interactive tests
for all our major configurations, and for build tree, install tree,
and traditional install tree. So when you attempt to do this again
using scripts/comprehensive_test.sh, make sure to limit what is tested
as I recommend above.  I would hope that severe limiting of the
components, the build configurations, and the trees that are tested
would allow both the interactive and noninteractive parts of this test
to complete in a much more reasonable length of time.

> -        Some of the programs running the NTK device did not produce any graphs, which is odd.

The point of these mass interactive tests is to check for important
run-time issues such as segfaults with all our interactive devices.
But clicking through all the pages of those results by hand would get
old very quickly.  So to make that burden a lot lighter these mass
tests use the -np option.

But if you compare the results from

examples/c/x00c -dev ntk -np

and

examples/c/x00c -dev ntk

you may find the former just gives you a "flash" of the final result
on the screen which may be hard to see.

When in doubt you can run the latter form of the command by hand, but
that would get old very quickly if you were doing that for all our
standard examples and all our interactive devices!  :-)

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

Re: [Plplot-devel] The wxwidgets device driver speed/idle time

[Laurent B. <lau...@un...>]

Hi Alan,

I haven't got qt installed.
My results looks like yours results :

lb@mp12-lb:~/plplot.git/examples/c++$ time ./x01 -dev wxwidgets -np
PLplot library version: 5.11.1
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 
103: Having multiple values in <test> isn't supported and may not work 
as expected
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 
138: Having multiple values in <test> isn't supported and may not work 
as expected
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 
103: Having multiple values in <test> isn't supported and may not work 
as expected
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 
138: Having multiple values in <test> isn't supported and may not work 
as expected

real    0m0.407s
user    0m0.108s
sys    0m0.016s
lb@mp12-lb:~/plplot.git/examples/c++$ time ./x01 -dev wxwidgets -np
PLplot library version: 5.11.1
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 
103: Having multiple values in <test> isn't supported and may not work 
as expected
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 
138: Having multiple values in <test> isn't supported and may not work 
as expected
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 
103: Having multiple values in <test> isn't supported and may not work 
as expected
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 
138: Having multiple values in <test> isn't supported and may not work 
as expected

real    0m10.997s
user    0m0.064s
sys    0m0.040s
lb@mp12-lb:~/plplot.git/examples/c++$ time ./x01 -dev xwin -np
PLplot library version: 5.11.1

real    0m0.122s
user    0m0.056s
sys    0m0.020s
lb@mp12-lb:~/plplot.git/examples/c++$ time ./x01 -dev xwin -np
PLplot library version: 5.11.1

real    0m0.122s
user    0m0.060s
sys    0m0.016s
lb@mp12-lb:~/plplot.git/examples/c++$ time ./x01 -dev xcairo -np
PLplot library version: 5.11.1
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 
103: Having multiple values in <test> isn't supported and may not work 
as expected
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 
138: Having multiple values in <test> isn't supported and may not work 
as expected

real    0m0.125s
user    0m0.088s
sys    0m0.016s
lb@mp12-lb:~/plplot.git/examples/c++$ time ./x01 -dev xcairo -np
PLplot library version: 5.11.1
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 
103: Having multiple values in <test> isn't supported and may not work 
as expected
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 
138: Having multiple values in <test> isn't supported and may not work 
as expected

real    0m0.128s
user    0m0.084s
sys    0m0.020s
lb@mp12-lb:~/plplot.git/examples/c++$






Le 14/11/2016 à 22:19, Alan W. Irwin a écrit :
> Hi Laurent:
>
> I have put my reply to you on list for obvious reasons.
>
> On 2016-11-14 14:26+0100 Laurent Berger wrote:
>
>> Hi Alan,
>>
>> I would try to help you
>
> Thanks in advance for that.
>
>> but I'm not familiar on linux (see attached file for version).
>
> From what you included, your Linux platform has access to wxwidgets
> version 3.0 (as do I).  But the rest of your platform (old Linux Mint
> distribution using a relatively old kernel version 3.2.0-2-amd64
> compared to my much more modern Debian Jessie using a fairly
> up-to-date kernel version 3.16.0-4-amd64) provides an extremely useful
> testing contrast in case the issue is some lameness in the IPC
> implementation for my particular Linux kernel.  (IPC, i.e.,
> interprocess communication is used to communicate between -dev
> wxwidgets and the wxPLViewer application that displays the results.)
>
>> I think it is this message 
>> (https://sourceforge.net/p/plplot/mailman/message/34744869/)
>
> Yes, that message and the following one that provided the screenshots 
> referred to
> in that message are the relevant ones.
>
>>
>> I have build plplot on linux using cmake 3.0.2 using "Unix Makefiles"
>> Then sudo make install. I have attached git log result and cmakecache
>> Then  I run in folder examples/c++
>> ./x01c -dev wxdrivers
>>
>> I can see a window with 4 curves. Windows title is wxPLviewer. No 
>> problem
>> Now what do you want to test ?
>
> Speed.
>
> You measure speed on linux using, e.g.,
>
> software@raven> time examples/c/x01c -dev wxwidgets -np
> PLplot library version: 5.11.1
>
> real    0m0.652s
> user    0m0.064s
> sys     0m0.016s
> software@raven> software@raven> time examples/c/x01c -dev wxwidgets -np
> PLplot library version: 5.11.1
>
> real    0m9.327s
> user    0m0.072s
> sys     0m0.008s
>
> That -np option stands for "no pause" and allows you to measure time
> without waiting for the human reaction of clicking on the GUI to
> finish the display.
>
> Those two measurements obviously have a huge difference in the real
> time used. The first timing is not too bad, but (by chance) the second
> timed run shows the problem which is quite often there is a random
> drop of at least an order of magnitude and sometimes two orders of
> magnitude in speed of communications between -dev wxwidgets and
> wxPLviewer due to excessive times when my cpus sit absolutely idle (as
> proved above by comparison of the sum of the user + sys times and the
> real time required to finish the example in the second time run).
> (This excessive idle time is also proved by my screenshots of my cpu
> meter that are referred to above.) The above results are for the
> current master branch tip.  By way of comparison here are the
> consistent timing results I get for -dev xwin, -dev qtwidget (for
> Qt5), and -dev xcairo on my platform.
>
> software@raven> time examples/c/x01c -dev xwin -np
> PLplot library version: 5.11.1
>
> real    0m0.482s
> user    0m0.008s
> sys     0m0.008s
> software@raven> time examples/c/x01c -dev xwin -np
> PLplot library version: 5.11.1
>
> real    0m0.472s
> user    0m0.012s
> sys     0m0.004s
> software@raven> time examples/c/x01c -dev qtwidget -np
> PLplot library version: 5.11.1
> libGL error: failed to authenticate magic 759
> libGL error: failed to load driver: nouveau
>
> real    0m0.472s
> user    0m0.088s
> sys     0m0.012s
> software@raven> software@raven> time examples/c/x01c -dev qtwidget -np
> PLplot library version: 5.11.1
>
> real    0m0.452s
> user    0m0.076s
> sys     0m0.020s
> software@raven> time examples/c/x01c -dev xcairo -np
> PLplot library version: 5.11.1
>
> real    0m0.239s
> user    0m0.048s
> sys     0m0.012s
> software@raven> time examples/c/x01c -dev xcairo -np
> PLplot library version: 5.11.1
>
> real    0m0.229s
> user    0m0.044s
> sys     0m0.012s
>
> If you get consistent timing results for -dev wxwidgets no matter how
> often you repeat the experiment and those timing results are within a
> factor of two of the timing results for one or more of the above
> interactive devices, then it is clear the IPC problem is likely due to
> some kernel issue on my Debian Jessie platform, and we can write off
> my timing results above to that cause.  But if you also get wildly
> inconsistent and often extremely slow wxwidgets results for a
> completely different Linux kernel, then either IPC kernel
> implementations on Linux are uniformly bad regardless of kernel
> version (a conclusion which I doubt) or the way that -dev wxwidgets
> and wxPLviewer currently use IPC to communicate between them is set up
> in a bad way for the Linux case, that randomly causes excessive idle
> times, and that is an issue that the PLplot development team needs to
> urgently address if we ever want the wxwidgets device to be popular on
> Linux.
>
> I am looking forward to your reply with similar time experiments
> on your own Linux platform.
>
> Alan
> __________________________
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and 
> Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state
> implementation for stellar interiors (freeeos.sf.net); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.sf.net); the libLASi project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> and the Linux Brochure Project (lbproject.sf.net).
> __________________________
>
> Linux-powered Science
> __________________________


-- 
Laurent Berger
Enseignant-chercheur I.U.T. du Mans
    Département Gestion des Entreprises et des Administrations
    Département Mesures Physiques
Tél 02 43 83 37 09

Re: [Plplot-devel] ctest failure with Qt file devices

[Hazen B. <hba...@ma...>]

On 11/15/2016 02:46 AM, Alan W. Irwin wrote:
>>
>> All the file based Qt devices are failing for me in ctest. This is an
>> example error message:
>>
>> test 17
>>       Start 17: examples_pngqt
>>
>> 17: Test command: /bin/bash "-c"
>> "EXAMPLES_DIR=/home/hbabcock/Code/plplot-build/examples
>> SRC_EXAMPLES_DIR=/home/hbabcock/Code/plplot/examples
>> OUTPUT_DIR=/home/hbabcock/Code/plplot-build/ctest_examples_output_dir
>> VC_CTEST_DIRECTORY= ./plplot-test.sh --verbose --front-end=c
>> --device=pngqt"
>> 17: Test timeout computed to be: 1500
>> 17: Testing front-end c
>> 17: x00c
>> 17: x01c
>> 17: x02c
>> 17: ./test_c.sh: line 32: 16690 Segmentation fault      (core dumped)
>> $DEBUG_CMD "$cdir"/x${index}${lang} -dev $device -o
>> "${OUTPUT_DIR}"/x${index}${lang}%n.$dsuffix $options 2> test.error >|
>> "${OUTPUT_DIR}"/x${index}${lang}_${dsuffix}.txt
>> 17/24 Test #17: examples_pngqt ...................***Failed    0.61 sec
>>
>
> Is this segfault occurring for Qt5 or Qt4?  If the former, my advice is
> to try Qt4 instead.

This is happening with Qt4, specifically:

$ /usr/bin/qmake-qt4 --version
QMake version 2.01a
Using Qt version 4.8.7 in /usr/lib/x86_64-linux-gnu

> My current testing hasn't detected this segfault, but that doesn't
> mean much since that is the nature of memory management issues; they
> sometimes segfault and they sometimes do not.  By the way, the "x02c"
> prompt
> occurs at the start of that portion of the test (see
> plplot_test/test_c.sh.in) so that is
> the example that segfaulted, not x03c.  So you might or might
> not see a segfault with
>
> ./x02c -dev pngqt -o ex2.png
>
> However, a valgrind run on that here (for the Qt5 case) does show
> memory management issues (invalid reads) that do not lead to segfaults
> for me but which lead to segfaults (like you have seen) for others.
> Furthermore, similar valgrind runs on x00c, x01c and x03c shows no
> such memory management issues.  I will take a look at that memory
> management incompatiblity between the qt devices and example 2 _if_
> that issue also shows up for Qt4, but if this is a Qt5-only issue I
> won't bother with it because I attribute (see below) Qt5-only memory
> management issues to the immaturity of Qt5 compared to Qt4.

Thank you for the correction, that command does not segfault:
./x02c -dev pngqt -o ex2.png

But it does segfault in family mode:
./x02c -fam -dev pngqt -o ex2.png

-Hazen

Re: [Plplot-devel] libplplottcltk now has a pure redacted API

[Arjen M. <Arj...@de...>]

Hi Alan,

From: Arjen Markus [mailto:Arj...@de...]
Sent: Tuesday, November 15, 2016 12:59 PM
To: Alan W. Irwin; PLplot development list
Subject: Re: [Plplot-devel] libplplottcltk now has a pure redacted API


Hi Alan,



I ran the comprehensive tests for Cygwin and MinGW (no interactive tests) as well as the interactive comprehensive tests for Cygwin. The non-interactive tests were perfect for both platforms. But I had some trouble with the set of interactive tests:

-        I could not run them on MinGW, as CMake errored out for reasons I have not explored as yet

-        The Cygwin interactive tests ran for some 5 hours - then I interrupted the script. I came across the same tests so many times that I started to suspect an infinite loop. Not sure what to make of it.

-        Some of the programs running the NTK device did not produce any graphs, which is odd. But navigating the interface was a trifle tricky as no cursor was being shown. That may be due to the set-up of my X Window system - it lacked a window manager. Still, this is something I want to look into a bit closer.

The graphs that I did see looked quite fine to me.



The oddities seem to be related to Cygwin and the set-up I use, rather than the redacted Tcl interface.



I will run the tests for bare Windows too but I do not expect any problems.


>> AM: Indeed, all examples produce identical output (save the ones not ported to Tcl, x34 and x32)

Regards,
Arjen

DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.

Re: [Plplot-devel] libplplottcltk now has a pure redacted API

[Arjen M. <Arj...@de...>]

Hi Alan,



I ran the comprehensive tests for Cygwin and MinGW (no interactive tests) as well as the interactive comprehensive tests for Cygwin. The non-interactive tests were perfect for both platforms. But I had some trouble with the set of interactive tests:

-        I could not run them on MinGW, as CMake errored out for reasons I have not explored as yet

-        The Cygwin interactive tests ran for some 5 hours - then I interrupted the script. I came across the same tests so many times that I started to suspect an infinite loop. Not sure what to make of it.

-        Some of the programs running the NTK device did not produce any graphs, which is odd. But navigating the interface was a trifle tricky as no cursor was being shown. That may be due to the set-up of my X Window system - it lacked a window manager. Still, this is something I want to look into a bit closer.

The graphs that I did see looked quite fine to me.



The oddities seem to be related to Cygwin and the set-up I use, rather than the redacted Tcl interface.



I will run the tests for bare Windows too but I do not expect any problems.


Regards,

Arjen


> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]
> Sent: Thursday, November 10, 2016 10:15 PM
> To: Arjen Markus; PLplot development list
> Subject: libplplottcltk now has a pure redacted API
>
> Hi Arjen:
>
> Using the powerful matrix resize and reshape capabilities of libtclmatrix that I
> recently developed, and following up on your important efforts to provide a redacted
> API for that library, I have now been able to remove the non-redacted API from
> libplplottcltk so that library is now has a pure redacted API.  Also, I have
> (necessarily) changed our Tcl/Tk examples to finish the conversion you started to
> the pure redacted API form. This result passes all my tests on the Linux platform.
> As far as I can tell, the only thing I still need to do to complete this "pure redacted"
> project is a substantial documentation update for libtclmatrix and our Tcl/Tk
> bindings.
>
> For details concerning this effort and the tests I have done on the Linux platform
> see the commit messages for my recent series of commits up to an including
> 0b9182b.
>
> I would appreciate you doing the same fundamental tests of this substantially
> updated Tcl/Tk code on both your Windows platforms (Cygwin and MinGW-
> w64/MSYS2).  Those tests consist of building the check_libtclmatrix_capabilities,
> test_noninteractive, and test_interactive targets.  To limit the time required to do the
> latter two tests, I strongly suggest you use the same CMake limiting options I did to
> drop many components of PLplot from the testing, namely
>
> -DDEFAULT_NO_DEVICES=ON -DPLD_ntk=ON -DPLD_tk=ON -DPLD_tkwin=ON
> -DPLD_xwin=ON -DPLD_ps=ON -DDEFAULT_NO_BINDINGS=ON -
> DENABLE_tcl=ON -DENABLE_tk=ON -DENABLE_itcl=ON -DENABLE_itk=ON
>
> As far as I know, it has been a very long time since you attempted building the
> test_interactive target on your Windows platforms, but building that target is
> essential to complete this test, and the above limiting options mean the tests go
> much faster and the amount of babysitting required to click the interactive GUI's to
> get through the test is also substantially reduced.  N.B. our Tk examples only work
> for the X version of Tk.  I know that is what you get on Cygwin, but I am not sure
> what versions of Tk are available on MinGW-w64/MSYS2, but if they don't have the
> X version, then you will automatically be limited to just the ntk device for the
> interactive part of the test.
>
> Please collect the cmake, and make results in *.out files as per usual with bash >&
> redirection, and send those files to me if you encounter any issues.
>
> Eventually, these new developments should also be tested by using
> scripts/comprehensive_test.sh (with or even without the above limiting
> options) but for now the above simpler test consisting of three different target builds
> for just the shared library build-tree case should be sufficient so long as you use the
> same careful setup of environment variables that you have been using previously
> for your successful comprehensive tests and assuming you collect the requested
> *.out files.
>
> N.B. to test the old Tcl/Tk bindings and examples preserved from before you
> started this redacted API effort, you could use the -
> DUSE_NON_REDACTED_TCL_TK=ON option as well for tests, but that simply
> gives you access to frozen Tcl/Tk bindings and examples code that is only for
> legacy use so I have only tested it once (some time ago) on Linux, and that is likely
> sufficient (unless you feel you will encounter some Windows user who refuses to
> use the new redacted API).
>
> Alan
> __________________________
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state implementation for
> stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net);
> PLplot scientific plotting software package (plplot.sf.net); the libLASi project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux
> Brochure Project (lbproject.sf.net).
> __________________________
>
> Linux-powered Science
> __________________________

DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.

Re: [Plplot-devel] Finding wxWidgets

[Alan W. I. <ir...@be...>]

On 2016-11-14 23:39-0500 Pedro Vicente wrote:

> all is fine
>
> so, the problem was that I was using git bash for Windows as shell (where 
> back-slash forward-slash convention is different from Unix/Windows; as a 
> software engineer I end up losing hours of my life fixing
> different Unix/Windows path conventions. Thanks Microsoft).
>
> Using just a "normal" Windows shell , this works
>
> -DwxWidgets_LIB_DIR:PATH=%WXWIN%\lib\vc_lib
>
> in
>
> cmake ".." -G "Visual Studio 14" -DPL_DOUBLE:BOOL=ON -DBUILD_TEST:BOOL=ON 
> -DCMAKE_CONFIGURATION_TYPES:STRING="Debug" -DCMAKE_BUILD_TYPE:STRING="Debug" 
> -DBUILD_SHARED_LIBS:BOOL=OFF -DSTATIC_RUNTIME:BOOL=ON -DPLD_wxwidgets:BOOL=ON 
> -DwxWidgets_ROOT_DIR:PATH=%WXWIN% -DwxWidgets_LIB_DIR:PATH=%WXWIN%\lib\vc_lib 
> -DwxWidgets_CONFIGURATION=mswud -DENABLE_MIX_CXX=ON 
> -DwxWidgets_EXCLUDE_COMMON_LIBRARIES:BOOL=OFF
>
>
> sorry for all the false alarms

Hi Pedro:

No problem.  Been there done that (when I was playing with MinGW/MSYS
under Wine years ago.)  In sum, I am glad you no longer encounter
wxwidgets find issues.

>
> Just 2 last notes :-)
>
>
> 1)
>
> If we specify the root of wxWidgets with
>
> -DwxWidgets_ROOT_DIR:PATH=%WXWIN%
>
> it seems that having to specify the library path could be eliminated
>
> -DwxWidgets_LIB_DIR:PATH=%WXWIN%\lib\vc_lib
>
> I believe this path
>
> \lib\vc_lib
>
> is always the same for any Windows build? If not than my point is not valid

I believe you are correct.  So try it and see.

>
> 2)
>
> After building with Visual Studio, all built ok
>
> ========== Rebuild All: 88 succeeded, 0 failed, 0 skipped ==========
>
> but in the last release there was an automatic run of the plot demo, that 
> shows a plot window, that did not show up this time
>
> no big deal, but it's a nice feature that shows that all went fine

If you are concerned about a test that is suddenly missing from (say)
the test_interactive target, then you should look for WARNING messages in the
cmake output concerning test targets.  Those warnings typically end
with a phrase similar to

"... so it is temporarily excluded from being a dependency of other more
general interactive test targets"

We typically use such warnings for issues we can do nothing about except
wait for external libraries to fix bugs.  So typically you can run
such targets as an individual test, but you will encounter segfaults that would
ruin more comprehensive testing so we exclude these problematic test
targets from being part of more comprehensive testing in the interest
of allowing the comprehensive tests to finish under normal
circumstances.

For example, today I found two other such problematic tests under Qt5
(test_qt_example and test_pyqt5_example).  I ascribe these to Qt5
immaturity so the only thing we can do about these is wait for the
bugs in Qt5 memory management to be fixed.  So those two tests are
shortly going to be excluded from the test_interactive target (with a
CMake WARNING similar to the above message to remind us to test the
individual targets from time to time to see if the external library at
fault has fixed its problems).

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

Re: [Plplot-devel] ctest failure with Qt file devices

[Alan W. I. <ir...@be...>]

On 2016-11-14 20:51-0500 Hazen Babcock wrote:

>
> Hello,
>
> All the file based Qt devices are failing for me in ctest. This is an
> example error message:
>
> test 17
>       Start 17: examples_pngqt
>
> 17: Test command: /bin/bash "-c"
> "EXAMPLES_DIR=/home/hbabcock/Code/plplot-build/examples
> SRC_EXAMPLES_DIR=/home/hbabcock/Code/plplot/examples
> OUTPUT_DIR=/home/hbabcock/Code/plplot-build/ctest_examples_output_dir
> VC_CTEST_DIRECTORY= ./plplot-test.sh --verbose --front-end=c --device=pngqt"
> 17: Test timeout computed to be: 1500
> 17: Testing front-end c
> 17: x00c
> 17: x01c
> 17: x02c
> 17: ./test_c.sh: line 32: 16690 Segmentation fault      (core dumped)
> $DEBUG_CMD "$cdir"/x${index}${lang} -dev $device -o
> "${OUTPUT_DIR}"/x${index}${lang}%n.$dsuffix $options 2> test.error >|
> "${OUTPUT_DIR}"/x${index}${lang}_${dsuffix}.txt
> 17/24 Test #17: examples_pngqt ...................***Failed    0.61 sec
>
>
> The equivalent(?) command line seems to work fine:
> $ ./x03c -dev pngqt -o ex3.png
>
> This is on a linux system.
> Linux Dell-XPS-8100 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52
> UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>
> gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
>

Hi Hazen:

Is this segfault occurring for Qt5 or Qt4?  If the former, my advice is
to try Qt4 instead.

That is the short response, and now here is the (much) longer one.

My current testing hasn't detected this segfault, but that doesn't
mean much since that is the nature of memory management issues; they
sometimes segfault and they sometimes do not.  By the way, the "x02c" prompt
occurs at the start of that portion of the test (see
plplot_test/test_c.sh.in) so that is
the example that segfaulted, not x03c.  So you might or might
not see a segfault with

./x02c -dev pngqt -o ex2.png

However, a valgrind run on that here (for the Qt5 case) does show
memory management issues (invalid reads) that do not lead to segfaults
for me but which lead to segfaults (like you have seen) for others.
Furthermore, similar valgrind runs on x00c, x01c and x03c shows no
such memory management issues.  I will take a look at that memory
management incompatiblity between the qt devices and example 2 _if_
that issue also shows up for Qt4, but if this is a Qt5-only issue I
won't bother with it because I attribute (see below) Qt5-only memory
management issues to the immaturity of Qt5 compared to Qt4.

An example of this Qt5-only possibility I was dealing with just
today is my current testing shows
qt_example generates valgrind reports about invalid reads for Qt5 but
not Qt4.  I looked deeply at that until I realized that Qt5 memory
management issue was generated by the following bog-standard Qt5 code
(taken right out of Qt5 documentation)

     QMessageBox msgBox;
     msgBox.setText( buf );
     msgBox.exec();

to implement that message box used to report interactive selection
coordinates.  (That memory management issue appeared when the OK
button was pressed on the message box.) I also discovered our pyqt5
example intermittently segfaulted while clicking the OK button on that
message box while our pyqt4 example does not.

In sum, I attribute all these symptoms and any further Qt5 memory
management issues that do not appear for Qt4 to the continuing
immaturity of Qt5 (at least the Debian Jessie Qt version 5.3.2 I have
access to) and I presume all these Qt5-only symptoms are nothing to do
with the PLplot code and will go away once Qt5 memory management is
properly debugged.

Note, an additional complicating factor here is I am just finishing up
some substantial build-system changes for Qt5 and some smaller changes
for Qt4, and some of my previous commits on this topic may have
screwed up linking which could also introduce memory management
issues. Anyhow, when I make the final commit on this topic, I plan to
check all qt-related results with "ldd -r" to make sure there are no
linking issues left.  Furthermore, I plan to run some systematic
valgrind tests for the pngqt case for both Qt4 and Qt5 to see whatever
examples (if any) still have both Qt4 and Qt5 memory management
problems.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

Re: [Plplot-devel] Finding wxWidgets

[Pedro V. <ped...@sp...>]

all is fine

so, the problem was that I was using git bash for Windows as shell (where 
back-slash forward-slash convention is different from Unix/Windows; as a 
software engineer I end up losing hours of my life fixing
different Unix/Windows path conventions. Thanks Microsoft).

Using just a "normal" Windows shell , this works

-DwxWidgets_LIB_DIR:PATH=%WXWIN%\lib\vc_lib

in

cmake ".." -G "Visual Studio 
14" -DPL_DOUBLE:BOOL=ON -DBUILD_TEST:BOOL=ON -DCMAKE_CONFIGURATION_TYPES:STRING="Debug" 
 -DCMAKE_BUILD_TYPE:STRING="Debug" -DBUILD_SHARED_LIBS:BOOL=OFF -DSTATIC_RUNTIME:BOOL=ON 
 -DPLD_wxwidgets:BOOL=ON -DwxWidgets_ROOT_DIR:PATH=%WXWIN% -DwxWidgets_LIB_DIR:PATH=%WXWIN%\lib\vc_lib 
 -DwxWidgets_CONFIGURATION=mswud -DENABLE_MIX_CXX=ON -DwxWidgets_EXCLUDE_COMMON_LIBRARIES:BOOL=OFF


sorry for all the false alarms

Just 2 last notes :-)


1)

If we specify the root of wxWidgets with

-DwxWidgets_ROOT_DIR:PATH=%WXWIN%

it seems that having to specify the library path could be eliminated

-DwxWidgets_LIB_DIR:PATH=%WXWIN%\lib\vc_lib

I believe this path

\lib\vc_lib

is always the same for any Windows build? If not than my point is not valid

2)

After building with Visual Studio, all built ok

========== Rebuild All: 88 succeeded, 0 failed, 0 skipped ==========

but in the last release there was an automatic run of the plot demo, that 
shows a plot window, that did not show up this time

no big deal, but it's a nice feature that shows that all went fine

thanks


-Pedro

----- Original Message ----- 
From: "Alan W. Irwin" <ir...@be...>
To: "Pedro Vicente" <ped...@sp...>
Cc: "Phil Rosenberg" <p.d...@gm...>; "Laurent Berger" 
<lau...@un...>; <plp...@li...>
Sent: Monday, November 14, 2016 3:23 AM
Subject: Re: [Plplot-devel] Finding wxWidgets


> On 2016-11-13 22:14-0500 Pedro Vicente wrote:
>
>> I have
>>
>>
>> WXWIN = M:\wx\wxwidgets-3.1.0
>
> Hi Pedro:
>
> That form is consistent with the examples at
> <https://wiki.wxwidgets.org/Adding_an_Environment_Variable_under_Windows>.
> Nevertheless, CMake is sometimes difficult about the back-slash Windows
> directory notation and may need the "native CMake" forward slash notation 
> instead for
> these cmake options that are specifying directories.
>
> So this is just an informed guess, but what happens if you replace
>
> -DwxWidgets_ROOT_DIR:PATH=%WXWIN%
> -DwxWidgets_LIB_DIR:PATH=%WXWIN%\lib\vc_lib
>
> with
>
> -DwxWidgets_ROOT_DIR:PATH=M:/wx/wxwidgets-3.1.0
> -DwxWidgets_LIB_DIR:PATH=M:/wx/wxwidgets-3.1.0/lib/vc_lib
>
> in your cmake options?
>
> Also, if that still does not do the trick, please send the
> CMakeCache.txt file as well.
>
> Alan
> __________________________
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and 
> Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state
> implementation for stellar interiors (freeeos.sf.net); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.sf.net); the libLASi project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> and the Linux Brochure Project (lbproject.sf.net).
> __________________________
>
> Linux-powered Science
> __________________________
> 

[Plplot-devel] ctest failure with Qt file devices

[Hazen B. <hba...@ma...>]

Hello,

All the file based Qt devices are failing for me in ctest. This is an 
example error message:

test 17
       Start 17: examples_pngqt

17: Test command: /bin/bash "-c" 
"EXAMPLES_DIR=/home/hbabcock/Code/plplot-build/examples 
SRC_EXAMPLES_DIR=/home/hbabcock/Code/plplot/examples 
OUTPUT_DIR=/home/hbabcock/Code/plplot-build/ctest_examples_output_dir 
VC_CTEST_DIRECTORY= ./plplot-test.sh --verbose --front-end=c --device=pngqt"
17: Test timeout computed to be: 1500
17: Testing front-end c
17: x00c
17: x01c
17: x02c
17: ./test_c.sh: line 32: 16690 Segmentation fault      (core dumped) 
$DEBUG_CMD "$cdir"/x${index}${lang} -dev $device -o 
"${OUTPUT_DIR}"/x${index}${lang}%n.$dsuffix $options 2> test.error >| 
"${OUTPUT_DIR}"/x${index}${lang}_${dsuffix}.txt
17/24 Test #17: examples_pngqt ...................***Failed    0.61 sec


The equivalent(?) command line seems to work fine:
$ ./x03c -dev pngqt -o ex3.png

This is on a linux system.
Linux Dell-XPS-8100 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609

-Hazen

Re: [Plplot-devel] The wxwidgets device driver speed/idle time

[Alan W. I. <ir...@be...>]

Hi Laurent:

I have put my reply to you on list for obvious reasons.

On 2016-11-14 14:26+0100 Laurent Berger wrote:

> Hi Alan,
>
> I would try to help you

Thanks in advance for that.

> but I'm not familiar on linux (see attached file for 
> version).

>From what you included, your Linux platform has access to wxwidgets
version 3.0 (as do I).  But the rest of your platform (old Linux Mint
distribution using a relatively old kernel version 3.2.0-2-amd64
compared to my much more modern Debian Jessie using a fairly
up-to-date kernel version 3.16.0-4-amd64) provides an extremely useful
testing contrast in case the issue is some lameness in the IPC
implementation for my particular Linux kernel.  (IPC, i.e.,
interprocess communication is used to communicate between -dev
wxwidgets and the wxPLViewer application that displays the results.)

> I think it is this message 
> (https://sourceforge.net/p/plplot/mailman/message/34744869/)

Yes, that message and the following one that provided the screenshots referred to
in that message are the relevant ones.

>
> I have build plplot on linux using cmake 3.0.2 using "Unix Makefiles"
> Then sudo make install. I have attached git log result and cmakecache
> Then  I run in folder examples/c++
> ./x01c -dev wxdrivers
>
> I can see a window with 4 curves. Windows title is wxPLviewer. No problem
> Now what do you want to test ?

Speed.

You measure speed on linux using, e.g.,

software@raven> time examples/c/x01c -dev wxwidgets -np
PLplot library version: 5.11.1

real    0m0.652s
user    0m0.064s
sys     0m0.016s
software@raven> 
software@raven> time examples/c/x01c -dev wxwidgets -np
PLplot library version: 5.11.1

real    0m9.327s
user    0m0.072s
sys     0m0.008s

That -np option stands for "no pause" and allows you to measure time
without waiting for the human reaction of clicking on the GUI to
finish the display.

Those two measurements obviously have a huge difference in the real
time used. The first timing is not too bad, but (by chance) the second
timed run shows the problem which is quite often there is a random
drop of at least an order of magnitude and sometimes two orders of
magnitude in speed of communications between -dev wxwidgets and
wxPLviewer due to excessive times when my cpus sit absolutely idle (as
proved above by comparison of the sum of the user + sys times and the
real time required to finish the example in the second time run).
(This excessive idle time is also proved by my screenshots of my cpu
meter that are referred to above.) The above results are for the
current master branch tip.  By way of comparison here are the
consistent timing results I get for -dev xwin, -dev qtwidget (for
Qt5), and -dev xcairo on my platform.

software@raven> time examples/c/x01c -dev xwin -np
PLplot library version: 5.11.1

real    0m0.482s
user    0m0.008s
sys     0m0.008s
software@raven> time examples/c/x01c -dev xwin -np
PLplot library version: 5.11.1

real    0m0.472s
user    0m0.012s
sys     0m0.004s
software@raven> time examples/c/x01c -dev qtwidget -np
PLplot library version: 5.11.1
libGL error: failed to authenticate magic 759
libGL error: failed to load driver: nouveau

real    0m0.472s
user    0m0.088s
sys     0m0.012s
software@raven> 
software@raven> time examples/c/x01c -dev qtwidget -np
PLplot library version: 5.11.1

real    0m0.452s
user    0m0.076s
sys     0m0.020s
software@raven> time examples/c/x01c -dev xcairo -np
PLplot library version: 5.11.1

real    0m0.239s
user    0m0.048s
sys     0m0.012s
software@raven> time examples/c/x01c -dev xcairo -np
PLplot library version: 5.11.1

real    0m0.229s
user    0m0.044s
sys     0m0.012s

If you get consistent timing results for -dev wxwidgets no matter how
often you repeat the experiment and those timing results are within a
factor of two of the timing results for one or more of the above
interactive devices, then it is clear the IPC problem is likely due to
some kernel issue on my Debian Jessie platform, and we can write off
my timing results above to that cause.  But if you also get wildly
inconsistent and often extremely slow wxwidgets results for a
completely different Linux kernel, then either IPC kernel
implementations on Linux are uniformly bad regardless of kernel
version (a conclusion which I doubt) or the way that -dev wxwidgets
and wxPLviewer currently use IPC to communicate between them is set up
in a bad way for the Linux case, that randomly causes excessive idle
times, and that is an issue that the PLplot development team needs to
urgently address if we ever want the wxwidgets device to be popular on
Linux.

I am looking forward to your reply with similar time experiments
on your own Linux platform.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

[Plplot-devel] The wxwidgets device driver speed/idle time

[Alan W. I. <ir...@be...>]

On 2016-11-14 08:28+0100 Laurent Berger wrote:

> Hi,
>
> I have just made a git pull git.code.sf.net/p/plplot/plplot. Using cmake 
> 3.7.0.rc2 and wxwidgets 3.1.0 and VS 2015. After pressing OK every where, all 
> is fine. thanks for this new version!

Hi Laurent:

I am glad to hear our wxwidgets device driver works for you so well on
Windows (which is the primary development platform used by Phil
Rosenberg for this new wxwidgets device driver).  However, I am having
real trouble with how slow this device is on my Linux platform (Debian
Jessie), and gave a detailed example (last January on this list that
included screen shots of my cpu meter) of the issue which was the cpu
is idle most of the time when communicating data both ways between the
wxwidgets device driver and wxPLViewer application.  However, I don't
know whether this excessivee idle time (compared to all our other
interactive devices available on Linux) is specific to Debian Jessie
or a general issue that needs to be addressed for the Linux
interprocess communication protocol that is being used to communicate
between wxwidgets device driver and wxPLViewer application. So if you
(or anyone else here) has access to a Linux box, some confirmation (or
not) of my (extremely) slow speed results for wxwidgets device driver
and wxPLViewer application would be much appreciated.

Alan

__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

Re: [Plplot-devel] Finding wxWidgets

[Alan W. I. <ir...@be...>]

On 2016-11-13 22:14-0500 Pedro Vicente wrote:

> I have
>
>
> WXWIN = M:\wx\wxwidgets-3.1.0

Hi Pedro:

That form is consistent with the examples at
<https://wiki.wxwidgets.org/Adding_an_Environment_Variable_under_Windows>.
Nevertheless, CMake is sometimes difficult about the back-slash Windows
directory notation and may need the "native CMake" forward slash notation instead for
these cmake options that are specifying directories.

So this is just an informed guess, but what happens if you replace

-DwxWidgets_ROOT_DIR:PATH=%WXWIN%
-DwxWidgets_LIB_DIR:PATH=%WXWIN%\lib\vc_lib

with

-DwxWidgets_ROOT_DIR:PATH=M:/wx/wxwidgets-3.1.0
-DwxWidgets_LIB_DIR:PATH=M:/wx/wxwidgets-3.1.0/lib/vc_lib

in your cmake options?

Also, if that still does not do the trick, please send the
CMakeCache.txt file as well.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

Re: [Plplot-devel] Finding wxWidgets

[Laurent B. <lau...@un...>]

Hi,

I have just made a git pull git.code.sf.net/p/plplot/plplot. Using cmake 
3.7.0.rc2 and wxwidgets 3.1.0 and VS 2015. After pressing OK every 
where, all  is fine. thanks for this new version!



Le 12/11/2016 à 10:00, Alan W. Irwin a écrit :
> On 2016-11-12 00:08-0500 Pedro Vicente wrote:
>
>> Hi Alan
>>
>> it seems all is ok now
>
>> doing
>
>> $ cmake ".." -G "Visual Studio 14" -DPL_DOUBLE:BOOL=ON
>> -DBUILD_TEST:BOOL=ON -DCMAKE_CONFIGURATION_TYPES:STRING="Debug"
>> -DCMAKE_BUILD_TYPE:STRING="Deb ug" -DBUILD_SHARED_LIBS:BOOL=OFF
>> -DSTATIC_RUNTIME:BOOL=ON -DPLD_wxwidgets:BOOL=ON
>> -DwxWidgets_ROOT_DIR:PATH=%WXWIN% -DwxWidgets_LIB_DIR:PATH=%WXWIN%\
>> lib\vc_lib -DwxWidgets_CONFIGURATION=mswud -DENABLE_MIX_CXX=ON
>> -DwxWidgets_EXCLUDE_COMMON_LIBRARIES:BOOL=OFF > make.txt 2>&1
>
>
> Actually, there are still problems finding wxWidgets on your platform.
> Specifically, from the make.txt file you sent you have the following
> (bad) find results:
>
> -- wxWidgets_FOUND           : FALSE
> -- wxWidgets_INCLUDE_DIRS    : -- wxWidgets_LIBRARY_DIRS    : -- 
> wxWidgets_LIBRARIES       : -- wxWidgets_CXX_FLAGS       : -- 
> wxWidgets_USE_FILE        : UsewxWidgets
> -- WARNING: wxWidgets or its libraries not found so setting all 
> wxwidgets devices to OFF.
>
> CMake is pretty good at finding libraries installed in standard
> locations so the first thing I suggest you try is to drop the options
> above that set wxWidgets_ROOT_DIR and wxWidgets_LIB_DIR.  But if that
> doesn't work (i.e., wxWidgets_FOUND is still FALSE). then you should
> consider the large likelihood that those variables are set incorrectly
> (i.e., do not point to the non-standard location where you have
> installed wxwidgets). For example, is WXWIN defined properly to the
> location where you have installed wxWidgets? (I have asked this key
> question before, but so far you have not responded.)
>
> Alan
> __________________________
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and 
> Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state
> implementation for stellar interiors (freeeos.sf.net); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.sf.net); the libLASi project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> and the Linux Brochure Project (lbproject.sf.net).
> __________________________
>
> Linux-powered Science
> __________________________

Re: [Plplot-devel] Finding wxWidgets

[Pedro V. <ped...@sp...>]

sorry wrong thread, reposting this

I have


WXWIN = M:\wx\wxwidgets-3.1.0

in my PATH there is

;%WXWIN%\lib\vc_lib;

but wxwidgets is still not detected

attached make.txt

done with

cmake ".." -G "Visual Studio
14" -DPL_DOUBLE:BOOL=ON -DBUILD_TEST:BOOL=ON -DCMAKE_CONFIGURATION_TYPES:STRING="Debug"
 -DCMAKE_BUILD_TYPE:STRING="Debug" -DBUILD_SHARED_LIBS:BOOL=OFF -DSTATIC_RUNTIME:BOOL=ON
 -DPLD_wxwidgets:BOOL=ON -DwxWidgets_ROOT_DIR:PATH=%WXWIN% -DwxWidgets_LIB_DIR:PATH=%WXWIN%\lib\vc_lib
 -DwxWidgets_CONFIGURATION=mswud -DENABLE_MIX_CXX=ON -DwxWidgets_EXCLUDE_COMMON_LIBRARIES:BOOL=OFF
 > make.txt


I'll debug this when I have some time, hopefully before the release

-Pedro



----- Original Message ----- 
From: "Alan W. Irwin" <ir...@be...>
To: "Pedro Vicente" <ped...@sp...>
Cc: "Phil Rosenberg" <p.d...@gm...>; "Laurent Berger" 
<lau...@un...>; <plp...@li...>
Sent: Saturday, November 12, 2016 4:00 AM
Subject: Re: [Plplot-devel] Finding wxWidgets


> On 2016-11-12 00:08-0500 Pedro Vicente wrote:
>
>> Hi Alan
>>
>> it seems all is ok now
>
>> doing
>
>> $ cmake ".." -G "Visual Studio 14" -DPL_DOUBLE:BOOL=ON
>> -DBUILD_TEST:BOOL=ON -DCMAKE_CONFIGURATION_TYPES:STRING="Debug"
>> -DCMAKE_BUILD_TYPE:STRING="Deb ug" -DBUILD_SHARED_LIBS:BOOL=OFF
>> -DSTATIC_RUNTIME:BOOL=ON -DPLD_wxwidgets:BOOL=ON
>> -DwxWidgets_ROOT_DIR:PATH=%WXWIN% -DwxWidgets_LIB_DIR:PATH=%WXWIN%\
>> lib\vc_lib -DwxWidgets_CONFIGURATION=mswud -DENABLE_MIX_CXX=ON
>> -DwxWidgets_EXCLUDE_COMMON_LIBRARIES:BOOL=OFF > make.txt 2>&1
>
>
> Actually, there are still problems finding wxWidgets on your platform.
> Specifically, from the make.txt file you sent you have the following
> (bad) find results:
>
> -- wxWidgets_FOUND           : FALSE
> -- wxWidgets_INCLUDE_DIRS    : -- wxWidgets_LIBRARY_DIRS    : --  
> wxWidgets_LIBRARIES       : -- wxWidgets_CXX_FLAGS       : --  
> wxWidgets_USE_FILE        : UsewxWidgets
> -- WARNING: wxWidgets or its libraries not found so setting all wxwidgets 
> devices to OFF.
>
> CMake is pretty good at finding libraries installed in standard
> locations so the first thing I suggest you try is to drop the options
> above that set wxWidgets_ROOT_DIR and wxWidgets_LIB_DIR.  But if that
> doesn't work (i.e., wxWidgets_FOUND is still FALSE). then you should
> consider the large likelihood that those variables are set incorrectly
> (i.e., do not point to the non-standard location where you have
> installed wxwidgets). For example, is WXWIN defined properly to the
> location where you have installed wxWidgets? (I have asked this key
> question before, but so far you have not responded.)
>
> Alan
> __________________________
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and 
> Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state
> implementation for stellar interiors (freeeos.sf.net); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.sf.net); the libLASi project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> and the Linux Brochure Project (lbproject.sf.net).
> __________________________
>
> Linux-powered Science
> __________________________
> 

Re: [Plplot-devel] Reducing loudness of compiler "Error" messages

[Pedro V. <ped...@sp...>]

I have


WXWIN = M:\wx\wxwidgets-3.1.0

in my PATH there is

;%WXWIN%\lib\vc_lib;

but wxwidgets is still not detected

attached make.txt

done with

cmake ".." -G "Visual Studio 
14" -DPL_DOUBLE:BOOL=ON -DBUILD_TEST:BOOL=ON -DCMAKE_CONFIGURATION_TYPES:STRING="Debug" 
 -DCMAKE_BUILD_TYPE:STRING="Debug" -DBUILD_SHARED_LIBS:BOOL=OFF -DSTATIC_RUNTIME:BOOL=ON 
 -DPLD_wxwidgets:BOOL=ON -DwxWidgets_ROOT_DIR:PATH=%WXWIN% -DwxWidgets_LIB_DIR:PATH=%WXWIN%\lib\vc_lib 
 -DwxWidgets_CONFIGURATION=mswud -DENABLE_MIX_CXX=ON -DwxWidgets_EXCLUDE_COMMON_LIBRARIES:BOOL=OFF 
 > make.txt


I'll debug this when I have some time, hopefully before the release

-Pedro

----- Original Message ----- 
From: "Alan W. Irwin" <ir...@be...>
To: "Pedro Vicente" <ped...@sp...>
Cc: "Phil Rosenberg" <p.d...@gm...>; "Laurent Berger" 
<lau...@un...>; <plp...@li...>
Sent: Saturday, November 12, 2016 4:07 AM
Subject: Reducing loudness of compiler "Error" messages


> On 2016-11-12 00:08-0500 Pedro Vicente wrote:
>
>> I have a couple suggestions, however
>>
>> the Cmake output is full of messages like
>>
>> CMake Error at CMakeLists.txt:18 (enable_language):
>>
>> No CMAKE_Fortran_COMPILER could be found.
>>
>> -- Configuring incomplete, errors occurred!
>>
>> these are not really errors, just features that are not detected, like a 
>> Fortran compiler
>>
>> would it be possible to replace this just with a information message , 
>> like
>>
>> --detected fortran compiler
>> --fortran compiler not found
>
> I agree those "Error" messages are too loud for simply an issue with a
> missing compiler so ideally it would be good to reduce that loudness.
> I will think about methods of doing that, but it may be a bit tricky
> so no promises.
>
> Alan
> __________________________
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and 
> Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state
> implementation for stellar interiors (freeeos.sf.net); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.sf.net); the libLASi project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> and the Linux Brochure Project (lbproject.sf.net).
> __________________________
>
> Linux-powered Science
> __________________________
> 

Re: [Plplot-devel] Finding wxWidgets

[Pedro V. <ped...@sp...>]

>> > Actually, there are still problems finding wxWidgets on your platform

yes, my bad, I don't know how I missed this
My WXWIN is wrong, sorry

I'll try again

-Pedro





----- Original Message ----- 
From: "Alan W. Irwin" <ir...@be...>
To: "Pedro Vicente" <ped...@sp...>
Cc: "Phil Rosenberg" <p.d...@gm...>; "Laurent Berger" 
<lau...@un...>; <plp...@li...>
Sent: Saturday, November 12, 2016 4:00 AM
Subject: Re: [Plplot-devel] Finding wxWidgets


> On 2016-11-12 00:08-0500 Pedro Vicente wrote:
>
>> Hi Alan
>>
>> it seems all is ok now
>
>> doing
>
>> $ cmake ".." -G "Visual Studio 14" -DPL_DOUBLE:BOOL=ON
>> -DBUILD_TEST:BOOL=ON -DCMAKE_CONFIGURATION_TYPES:STRING="Debug"
>> -DCMAKE_BUILD_TYPE:STRING="Deb ug" -DBUILD_SHARED_LIBS:BOOL=OFF
>> -DSTATIC_RUNTIME:BOOL=ON -DPLD_wxwidgets:BOOL=ON
>> -DwxWidgets_ROOT_DIR:PATH=%WXWIN% -DwxWidgets_LIB_DIR:PATH=%WXWIN%\
>> lib\vc_lib -DwxWidgets_CONFIGURATION=mswud -DENABLE_MIX_CXX=ON
>> -DwxWidgets_EXCLUDE_COMMON_LIBRARIES:BOOL=OFF > make.txt 2>&1
>
>
> Actually, there are still problems finding wxWidgets on your platform.
> Specifically, from the make.txt file you sent you have the following
> (bad) find results:
>
> -- wxWidgets_FOUND           : FALSE
> -- wxWidgets_INCLUDE_DIRS    : -- wxWidgets_LIBRARY_DIRS    : --  
> wxWidgets_LIBRARIES       : -- wxWidgets_CXX_FLAGS       : --  
> wxWidgets_USE_FILE        : UsewxWidgets
> -- WARNING: wxWidgets or its libraries not found so setting all wxwidgets 
> devices to OFF.
>
> CMake is pretty good at finding libraries installed in standard
> locations so the first thing I suggest you try is to drop the options
> above that set wxWidgets_ROOT_DIR and wxWidgets_LIB_DIR.  But if that
> doesn't work (i.e., wxWidgets_FOUND is still FALSE). then you should
> consider the large likelihood that those variables are set incorrectly
> (i.e., do not point to the non-standard location where you have
> installed wxwidgets). For example, is WXWIN defined properly to the
> location where you have installed wxWidgets? (I have asked this key
> question before, but so far you have not responded.)
>
> Alan
> __________________________
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and 
> Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state
> implementation for stellar interiors (freeeos.sf.net); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.sf.net); the libLASi project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> and the Linux Brochure Project (lbproject.sf.net).
> __________________________
>
> Linux-powered Science
> __________________________
> 

[Plplot-devel] Reducing loudness of compiler "Error" messages

[Alan W. I. <ir...@be...>]

On 2016-11-12 00:08-0500 Pedro Vicente wrote:

> I have a couple suggestions, however
>
> the Cmake output is full of messages like
>
> CMake Error at CMakeLists.txt:18 (enable_language):
>
> No CMAKE_Fortran_COMPILER could be found.
>
> -- Configuring incomplete, errors occurred!
>
> these are not really errors, just features that are not detected, like a 
> Fortran compiler
>
> would it be possible to replace this just with a information message , like
>
> --detected fortran compiler
> --fortran compiler not found

I agree those "Error" messages are too loud for simply an issue with a
missing compiler so ideally it would be good to reduce that loudness.
I will think about methods of doing that, but it may be a bit tricky
so no promises.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

Re: [Plplot-devel] Finding wxWidgets

[Alan W. I. <ir...@be...>]

On 2016-11-12 00:08-0500 Pedro Vicente wrote:

> Hi Alan
>
> it seems all is ok now

> doing

> $ cmake ".." -G "Visual Studio 14" -DPL_DOUBLE:BOOL=ON
> -DBUILD_TEST:BOOL=ON -DCMAKE_CONFIGURATION_TYPES:STRING="Debug"
> -DCMAKE_BUILD_TYPE:STRING="Deb ug" -DBUILD_SHARED_LIBS:BOOL=OFF
> -DSTATIC_RUNTIME:BOOL=ON -DPLD_wxwidgets:BOOL=ON
> -DwxWidgets_ROOT_DIR:PATH=%WXWIN% -DwxWidgets_LIB_DIR:PATH=%WXWIN%\
> lib\vc_lib -DwxWidgets_CONFIGURATION=mswud -DENABLE_MIX_CXX=ON
> -DwxWidgets_EXCLUDE_COMMON_LIBRARIES:BOOL=OFF > make.txt 2>&1


Actually, there are still problems finding wxWidgets on your platform.
Specifically, from the make.txt file you sent you have the following
(bad) find results:

-- wxWidgets_FOUND           : FALSE
-- wxWidgets_INCLUDE_DIRS    : 
-- wxWidgets_LIBRARY_DIRS    : 
-- wxWidgets_LIBRARIES       : 
-- wxWidgets_CXX_FLAGS       : 
-- wxWidgets_USE_FILE        : UsewxWidgets
-- WARNING: wxWidgets or its libraries not found so setting all wxwidgets devices to OFF.

CMake is pretty good at finding libraries installed in standard
locations so the first thing I suggest you try is to drop the options
above that set wxWidgets_ROOT_DIR and wxWidgets_LIB_DIR.  But if that
doesn't work (i.e., wxWidgets_FOUND is still FALSE). then you should
consider the large likelihood that those variables are set incorrectly
(i.e., do not point to the non-standard location where you have
installed wxwidgets). For example, is WXWIN defined properly to the
location where you have installed wxWidgets? (I have asked this key
question before, but so far you have not responded.)

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

Re: [Plplot-devel] Finding wxWidgets

[Pedro V. <ped...@sp...>]

Hi Alan

it seems all is ok now

doing


$ cmake ".." -G "Visual Studio 
14" -DPL_DOUBLE:BOOL=ON -DBUILD_TEST:BOOL=ON -DCMAKE_CONFIGURATION_TYPES:STRING="Debug" 
 -DCMAKE_BUILD_TYPE:STRING="Deb 
ug" -DBUILD_SHARED_LIBS:BOOL=OFF -DSTATIC_RUNTIME:BOOL=ON -DPLD_wxwidgets:BOOL=ON 
 -DwxWidgets_ROOT_DIR:PATH=%WXWIN% -DwxWidgets_LIB_DIR:PATH=%WXWIN%\ 
lib\vc_lib -DwxWidgets_CONFIGURATION=mswud -DENABLE_MIX_CXX=ON -DwxWidgets_EXCLUDE_COMMON_LIBRARIES:BOOL=OFF 
 > make.txt 2>&1

and then building

========== Build: 86 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

good job, thanks


the file make.txt is attached

I have a couple suggestions, however

the Cmake output is full of messages like

CMake Error at CMakeLists.txt:18 (enable_language):

  No CMAKE_Fortran_COMPILER could be found.

-- Configuring incomplete, errors occurred!

these are not really errors, just features that are not detected, like a 
Fortran compiler

would it be possible to replace this just with a information message , like

--detected fortran compiler
--fortran compiler not found


-Pedro


----- Original Message ----- 
From: "Alan W. Irwin" <ir...@be...>
To: "Pedro Vicente" <ped...@sp...>; "Phil Rosenberg" 
<p.d...@gm...>; "Laurent Berger" <lau...@un...>; 
<plp...@li...>
Sent: Wednesday, October 19, 2016 8:56 PM
Subject: Re: [Plplot-devel] Finding wxWidgets


> N.B. I have just (commit 3ab6396) updated the PLplot wxWidgets find
> module again to conform (identically except for one necessary line) to
> the latest (CMake-3.7.0-rc2) official version.  See the commit log
> message for a description of the changes in the PLplot version of this
> find module (which we are maintaining separately from the official
> version since that version is being actively maintained and many of
> our users are using a CMake version that is earlier than
> CMake-3.7.0-rc2 so would access a buggy version of this find module
> unless we supply the latest version like this).
>
> I am pretty sure this latest version will work fine for everybody
> (since it is maintained by the CMake developer team who are responding
> so actively to bug reports concerning it), but further tests by
> everybody to confirm good wxWidgets find results using our latest
> master branch would be much appreciated.
>
> Alan
> __________________________
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and 
> Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state
> implementation for stellar interiors (freeeos.sf.net); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.sf.net); the libLASi project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> and the Linux Brochure Project (lbproject.sf.net).
> __________________________
>
> Linux-powered Science
> __________________________
> 

[Plplot-devel] libplplottcltk now has a pure redacted API

[Alan W. I. <ir...@be...>]

Hi Arjen:

Using the powerful matrix resize and reshape capabilities of
libtclmatrix that I recently developed, and following up on your
important efforts to provide a redacted API for that library, I have
now been able to remove the non-redacted API from libplplottcltk so
that library is now has a pure redacted API.  Also, I have
(necessarily) changed our Tcl/Tk examples to finish the conversion you
started to the pure redacted API form. This result passes all my tests
on the Linux platform.  As far as I can tell, the only thing I still
need to do to complete this "pure redacted" project is a substantial
documentation update for libtclmatrix and our Tcl/Tk bindings.

For details concerning this effort and the tests I have done on the
Linux platform see the commit messages for my recent series of commits
up to an including 0b9182b.

I would appreciate you doing the same fundamental tests of this
substantially updated Tcl/Tk code on both your Windows platforms
(Cygwin and MinGW-w64/MSYS2).  Those tests consist of building
the check_libtclmatrix_capabilities, test_noninteractive, and
test_interactive targets.  To limit the time required to do the latter two tests,
I strongly suggest you use the same CMake limiting options I did to drop
many components of PLplot from the testing, namely

-DDEFAULT_NO_DEVICES=ON -DPLD_ntk=ON -DPLD_tk=ON
-DPLD_tkwin=ON -DPLD_xwin=ON -DPLD_ps=ON -DDEFAULT_NO_BINDINGS=ON
-DENABLE_tcl=ON -DENABLE_tk=ON -DENABLE_itcl=ON -DENABLE_itk=ON

As far as I know, it has been a very long time since you attempted
building the test_interactive target on your Windows platforms, but
building that target is essential to complete this test, and the above
limiting options mean the tests go much faster and the amount of
babysitting required to click the interactive GUI's to get through the
test is also substantially reduced.  N.B. our Tk examples only work
for the X version of Tk.  I know that is what you get on Cygwin, but I
am not sure what versions of Tk are available on MinGW-w64/MSYS2, but
if they don't have the X version, then you will automatically be
limited to just the ntk device for the interactive part of the test.

Please collect the cmake, and make results in *.out files as per usual
with bash >& redirection, and send those files to me if you encounter
any issues.

Eventually, these new developments should also be tested by using
scripts/comprehensive_test.sh (with or even without the above limiting
options) but for now the above simpler test consisting of three
different target builds for just the shared library build-tree case
should be sufficient so long as you use the same careful setup of
environment variables that you have been using previously for your
successful comprehensive tests and assuming you collect the requested
*.out files.

N.B. to test the old Tcl/Tk bindings and examples preserved from
before you started this redacted API effort, you could use the
-DUSE_NON_REDACTED_TCL_TK=ON option as well for tests, but that simply
gives you access to frozen Tcl/Tk bindings and examples code that is
only for legacy use so I have only tested it once (some time ago) on
Linux, and that is likely sufficient (unless you feel you will
encounter some Windows user who refuses to use the new redacted API).

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________