Re: [Plplot-devel] Release status: plmetafile.c and plbuf.c compiler warnings

2015-06-01 Thread Jim Dishaw

 On May 31, 2015, at 10:11 PM, Jim Dishaw j...@dishaw.org wrote:
 
 Yep, I will take a look
 
 
 
 On May 31, 2015, at 9:32 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
 
 On 2015-05-31 22:06+0100 Phil Rosenberg wrote:
 
 Hi Alan
 You should now find that the plbuf.c warning is gone. I haven't
 touched the plmeta files. I will leave these to Jim as I don't know
 that code well.
 
 @ Phil: I confirm you fix, and thanks!
 
 @Jim:
 
 The remaining warnings are
 
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c: In function 
 ‘read_header’:
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c:341:8: warning: 
 ‘pdf_rc’ may be used uninitialized in this function [-Wuninitialized]
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c:306:9: note: ‘pdf_rc’ 
 was declared here
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c: In function 
 ‘plreadmetafile’:
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c:378:23: warning: 
 ‘plm’ may be used uninitialized in this function [-Wmaybe-uninitialized]
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c:1117:14: note: ‘plm’ 
 was declared here
 

I think these two patches will fix the warnings (I don’t get any warnings with 
clang, but it does not have the -Wmaybe-uninitialized option). 



0001-Fixed-uninitialized-value-warning-in-plreadmetafile.patch
Description: Binary data


0002-Fixed-uninitialized-variable-error-in-read_entry.patch
Description: Binary data
 

--
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: plmetafile.c and plbuf.c compiler warnings

2015-06-01 Thread Alan W. Irwin
On 2015-06-01 17:32-0400 Jim Dishaw wrote:

 On May 31, 2015, at 9:32 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca 
 wrote:
 The remaining warnings are

 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c: In function 
 ‘read_header’:
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c:341:8: warning: 
 ‘pdf_rc’ may be used uninitialized in this function [-Wuninitialized]
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c:306:9: note: 
 ‘pdf_rc’ was declared here
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c: In function 
 ‘plreadmetafile’:
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c:378:23: warning: 
 ‘plm’ may be used uninitialized in this function [-Wmaybe-uninitialized]
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c:1117:14: note: ‘plm’ 
 was declared here


 I think these two patches will fix the warnings (I don’t get any warnings 
 with clang, but it does not have the -Wmaybe-uninitialized option).

The above warnings were fixed by your two commits.

Pushed and thanks!

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
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: plmetafile.c and plbuf.c compiler warnings

2015-05-31 Thread Phil Rosenberg
 Hi Alan
I'm attacking my to do list. Do you still get these warnings? I just
looked and the line 1309 no longer makes sense in terms of a reference
to cmd so I guess the code has changed since then. I don't get any
unallocated variable warnings for plbuf in VC++ so perhaps someone
else fixed this issue.

Phil

On 12 March 2015 at 20:14, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
 To Phil:

 gcc is generating these warnings when building libplplot.  Would you
 please take a look to see whether this is either a real uninitialized issue
 that needs to be fixed or a false alarm?

 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c: In function
 ‘read_header’:
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c:336:8: warning:
 ‘pdf_rc’ may be used uninitialized in this function [-Wuninitialized]
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c:301:9: note: ‘pdf_rc’
 was declared here
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c: In function
 ‘plreadmetafile’:
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c:373:23: warning:
 ‘plm’ may be used uninitialized in this function [-Wmaybe-uninitialized]
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c:1112:14: note: ‘plm’
 was declared here
 []
 /home/software/plplot/HEAD/plplot.git/src/plbuf.c: In function ‘rdbuf_bop’:
 /home/software/plplot/HEAD/plplot.git/src/plbuf.c:1309:11: warning: ‘cmd’
 may be used uninitialized in this function [-Wmaybe-uninitialized]
 /home/software/plplot/HEAD/plplot.git/src/plbuf.c:593:19: note: ‘cmd’ was
 declared here

 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
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: plmetafile.c and plbuf.c compiler warnings

2015-05-31 Thread Phil Rosenberg
Hi Alan
I've worked this out, the line in question is in a function called
with the possibly uninitialized variable.
 I'm writing the code now to double check everything although the only
case where we could get an uninitialized variable would be for a
corrupted buffer.

Phil

On 31 May 2015 at 18:33, Phil Rosenberg p.d.rosenb...@gmail.com wrote:
  Hi Alan
 I'm attacking my to do list. Do you still get these warnings? I just
 looked and the line 1309 no longer makes sense in terms of a reference
 to cmd so I guess the code has changed since then. I don't get any
 unallocated variable warnings for plbuf in VC++ so perhaps someone
 else fixed this issue.

 Phil

 On 12 March 2015 at 20:14, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
 To Phil:

 gcc is generating these warnings when building libplplot.  Would you
 please take a look to see whether this is either a real uninitialized issue
 that needs to be fixed or a false alarm?

 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c: In function
 ‘read_header’:
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c:336:8: warning:
 ‘pdf_rc’ may be used uninitialized in this function [-Wuninitialized]
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c:301:9: note: ‘pdf_rc’
 was declared here
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c: In function
 ‘plreadmetafile’:
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c:373:23: warning:
 ‘plm’ may be used uninitialized in this function [-Wmaybe-uninitialized]
 /home/software/plplot/HEAD/plplot.git/src/plmetafile.c:1112:14: note: ‘plm’
 was declared here
 []
 /home/software/plplot/HEAD/plplot.git/src/plbuf.c: In function ‘rdbuf_bop’:
 /home/software/plplot/HEAD/plplot.git/src/plbuf.c:1309:11: warning: ‘cmd’
 may be used uninitialized in this function [-Wmaybe-uninitialized]
 /home/software/plplot/HEAD/plplot.git/src/plbuf.c:593:19: note: ‘cmd’ was
 declared here

 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
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: plmetafile.c and plbuf.c compiler warnings

2015-05-31 Thread Phil Rosenberg
Hi Alan
You should now find that the plbuf.c warning is gone. I haven't
touched the plmeta files. I will leave these to Jim as I don't know
that code well.

Phil

On 31 May 2015 at 20:14, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
 On 2015-05-31 18:59+0100 Phil Rosenberg wrote:

 Hi Alan
 I've worked this out, the line in question is in a function called
 with the possibly uninitialized variable.
 I'm writing the code now to double check everything although the only
 case where we could get an uninitialized variable would be for a
 corrupted buffer.


 Hi Phil:

 Our e-mails crossed, but it is great to read above you are analyzing
 the situation and figuring out the source of these warnings. When I
 see your commit with the fix for these warnings, I will follow up by
 trying the same build test again.


 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
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: plmetafile.c and plbuf.c compiler warnings

2015-05-31 Thread Alan W. Irwin
On 2015-05-31 18:33+0100 Phil Rosenberg wrote:

 Hi Alan
 I'm attacking my to do list. Do you still get these warnings? I just
 looked and the line 1309 no longer makes sense in terms of a reference
 to cmd so I guess the code has changed since then. I don't get any
 unallocated variable warnings for plbuf in VC++ so perhaps someone
 else fixed this issue.

With the following compiler options:

CFLAGS=-O3 -fvisibility=hidden -Wuninitialized

and gcc on Linux, the following warnings are
generated from building the plplot target:

/home/software/plplot/HEAD/plplot.git/src/plmetafile.c: In function 
‘read_header’:
/home/software/plplot/HEAD/plplot.git/src/plmetafile.c:341:8: warning: ‘pdf_rc’ 
may be used uninitialized in this function [-Wuninitialized]
/home/software/plplot/HEAD/plplot.git/src/plmetafile.c:306:9: note: ‘pdf_rc’ 
was declared here
/home/software/plplot/HEAD/plplot.git/src/plmetafile.c: In function 
‘plreadmetafile’:
/home/software/plplot/HEAD/plplot.git/src/plmetafile.c:378:23: warning: ‘plm’ 
may be used uninitialized in this function [-Wmaybe-uninitialized]
/home/software/plplot/HEAD/plplot.git/src/plmetafile.c:1117:14: note: ‘plm’ was 
declared here
[...]
/home/software/plplot/HEAD/plplot.git/src/plbuf.c: In function ‘rdbuf_bop’:
/home/software/plplot/HEAD/plplot.git/src/plbuf.c:1309:11: warning: ‘cmd’ may 
be used uninitialized in this function [-Wmaybe-uninitialized]
/home/software/plplot/HEAD/plplot.git/src/plbuf.c:593:19: note: ‘cmd’ was 
declared here

You should be able to replicate this on your Linux box and probably
also on your Cygwin platform.

 On 12 March 2015 at 20:14, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:

 gcc is generating these warnings when building libplplot.  Would you
 please take a look to see whether this is either a real uninitialized issue
 that needs to be fixed or a false alarm?

My guess is these are all due to false alarms from gcc, but if your
analysis says that is the case it is also worth squelching
these warnings by dummy initializing some variables with appropriate comment
like

// To squelch spurious gcc uninitialized warnings
 PLINT i=0; // or whatever is needed

so that real and useful warnings from gcc considering uninitialized
variables will not be obfuscated by known false alarms.

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
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-04-14 Thread Alan W. Irwin
On 2015-04-10 21:54+0100 Andrew Ross wrote:


 Hazen,

 That's interesting, and at odds with my tests a week or so back on Kubuntu
 14.10. Can you confirm which flavour and version of Ubuntu you are using?
 Also, I assume this is with Qt4 and not Qt5?

Hi Andrew:

The answers to your questions have been scattered a bit in different
threads so to collect them together for you here, Hazen used Qt4.8.6,
and Lubuntu, and today he said he was pretty sure the version was
14.04.2 LTS. And he recently attached a detailed valgrind report that
showed all sorts of invalid reads for one of the qt devices on his
Lubuntu platform.  (Interestingly, the invalid reads occurred during
initialization rather than the cases we have looked at in the past
where invalid reads occurred at plend.)

So if you run that specific valgrind test on your own kubuntu version
and do not confirm the severe memory management errors, then that is a
pretty clear demonstration of a Lubuntu Qt bug, and if the Qt
packaging for Lubuntu is identical to that used for every other
variant besides Kubuntu, then it is likely a non-Kubuntu Ubuntu bug.

Since there is only a 6-month difference between 14.04.2 LTS and 14.10
and we never appear to get such severe memory management issues for at
least two variants of Debian (which sticks pretty close to the
upstream version of Qt) there is a decent chance this bug has nothing
to do with upstream Qt and instead is due to some difference in
patching between the Lubuntu Qt patches that are applied and the
Kubuntu patches that are applied to the upstream version. Anyhow,
those package patches and the equivalent package patches for the
Debian cases are the first place I would look for a relevant
difference between the various versions that work, and the one or more
(Lubuntu and possibly Ubuntu) versions that do not.

If you can pin this issue down to a package patch that was applied or
not, that is well worth a bug report to Ubuntu since it is in our
interest to have Qt working properly on all variants of Ubuntu.

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
__

--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-04-11 Thread Hazen Babcock


On 04/10/2015 09:06 PM, Alan W. Irwin wrote:
 On 2015-04-10 12:29-0400 Hazen Babcock wrote:


 That's a fairly sparse but still acceptable comprehensive test result
 for
 this release, but to start the next release cycle properly I strongly
 encourage everybody here to learn to run the
 scripts/comprehensive_test.sh bash script to completion on all
 platforms accessible to you (taking the approach that you should
 disable any PLplot component that has errors in order to get the
 script to complete).  Such tests are encouraged for essentially all
 platforms (e.g, MSVC, Cygwin, MinGW/MSYS, MinGW-w64/MSYS2, Mac OS X,
 all varieties of Linux distributions, and other Unices).

 I just tried to run the non-interactive comprehensive tests on lubuntu
 without success. Perhaps it is because I'm not running the tests
 properly? The QT devices that are causing the problems work fine if I
 run them by hand. I looked on the sourceforge wiki but I could not
 find and instructions on how to do this. Attached is what I tried and
 the results of the test.

 Hi Hazen:

 Thanks for helping out with comprehensive testing.

 To answer your question, you should look at
 https://sourceforge.net/p/plplot/wiki/Testing_PLplot/ in general and
 https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Comprehensive%20testing

 and
 https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Testing%20Reports
 in specific for directions and results concerning comprehensive testing.

 The script results require no special setup other than what you do for
 your hand-crafted builds.  Greg had similar problems (but on the
 OpenSUSE platform) with segfaults for all Qt related ctest results.

 I suspect these severe memory management issues (which sometimes but
 not always will generate segfaults like you and Greg have seen) have
 nothing to do with PLplot but are instead due to bad Qt libraries or
 bad Qt library dependencies on some platforms. In contrast to your
 result and Greg's I have looked hard at qt results with valgrind on
 Debian stable, and they have no severe memory management issues with
 Qt4.8, and I think Andrew has done the same for his various Debian and
 Ubuntu platforms.  Andrew and I do have different severe memory
 management results for the Qt5 case; I get them with the epa_build of
 Qt5, and he does not for several different distros.  But Qt4 has
 always been completely reliable in this regard for us _for the
 platforms we have access to_.  But this is obviously not the case for
 you and Greg.

 Anyhow, for now we are just trying to keep track of exactly which
 platforms have good qt results with Qt4.8 and which do not.  However, we
 are
 also interested in exactly which components of PLplot work for all our
 different major configurations (shared libraries/dynamic devices,
 shared libraries/non-dynamic devices, and static libraries/non-dynamic
 devices. Thus, please try to get the script to finish
 with components removed that are giving trouble.  (I gave that same
 advice to Greg).

 So, for example, to
 drop everything Qt related you should specify

 --cmake_added_options DEFAULT_NO_QT_DEVICES=ON -DENABLE_qt=OFF

 when attempting to run scripts/comprehensive_testing.sh again.

 Once you get that script to complete, we will note in the
 corresponding report on the Wiki exactly which components had to be
 dropped and why.

It worked fine without the Qt components. Is there an output file that I 
should send?

Why do you think these Qt components fail in the tests, but work fine if 
they are run independently? What is the testing framework doing that is 
not being done from the command line?

-Hazen

--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-04-10 Thread Andrew Ross

Hazen,

That's interesting, and at odds with my tests a week or so back on Kubuntu
14.10. Can you confirm which flavour and version of Ubuntu you are using?
Also, I assume this is with Qt4 and not Qt5?

Andrew

On Fri, Apr 10, 2015 at 12:29:15PM -0400, Hazen Babcock wrote:
 
 That's a fairly sparse but still acceptable comprehensive test result for
 this release, but to start the next release cycle properly I strongly
 encourage everybody here to learn to run the
 scripts/comprehensive_test.sh bash script to completion on all
 platforms accessible to you (taking the approach that you should
 disable any PLplot component that has errors in order to get the
 script to complete).  Such tests are encouraged for essentially all
 platforms (e.g, MSVC, Cygwin, MinGW/MSYS, MinGW-w64/MSYS2, Mac OS X,
 all varieties of Linux distributions, and other Unices).
 
 I just tried to run the non-interactive comprehensive tests on lubuntu
 without success. Perhaps it is because I'm not running the tests properly?
 The QT devices that are causing the problems work fine if I run them by
 hand. I looked on the sourceforge wiki but I could not find and instructions
 on how to do this. Attached is what I tried and the results of the test.
 
 best,
 -Hazen
 

--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-04-10 Thread Hazen Babcock
On 04/10/2015 04:54 PM, Andrew Ross wrote:

 Hazen,

 That's interesting, and at odds with my tests a week or so back on Kubuntu
 14.10. Can you confirm which flavour and version of Ubuntu you are using?
 Also, I assume this is with Qt4 and not Qt5?


Andrew,

This is what I have:
hb ~$ uname -a
Linux hbabcock-laptop2 3.13.0-49-generic #81-Ubuntu SMP Tue Mar 24 
19:29:48 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

hb ~$ qmake --version
QMake version 2.01a
Using Qt version 4.8.6 in /usr/lib/x86_64-linux-gnu

-Hazen


--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-04-10 Thread Alan W. Irwin
On 2015-04-10 12:29-0400 Hazen Babcock wrote:

 
 That's a fairly sparse but still acceptable comprehensive test result for
 this release, but to start the next release cycle properly I strongly
 encourage everybody here to learn to run the
 scripts/comprehensive_test.sh bash script to completion on all
 platforms accessible to you (taking the approach that you should
 disable any PLplot component that has errors in order to get the
 script to complete).  Such tests are encouraged for essentially all
 platforms (e.g, MSVC, Cygwin, MinGW/MSYS, MinGW-w64/MSYS2, Mac OS X,
 all varieties of Linux distributions, and other Unices).

 I just tried to run the non-interactive comprehensive tests on lubuntu 
 without success. Perhaps it is because I'm not running the tests properly? 
 The QT devices that are causing the problems work fine if I run them by hand. 
 I looked on the sourceforge wiki but I could not find and instructions on how 
 to do this. Attached is what I tried and the results of the test.

Hi Hazen:

Thanks for helping out with comprehensive testing.

To answer your question, you should look at
https://sourceforge.net/p/plplot/wiki/Testing_PLplot/ in general and
https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Comprehensive%20testing
and
https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Testing%20Reports
in specific for directions and results concerning comprehensive testing.

The script results require no special setup other than what you do for
your hand-crafted builds.  Greg had similar problems (but on the
OpenSUSE platform) with segfaults for all Qt related ctest results.

I suspect these severe memory management issues (which sometimes but
not always will generate segfaults like you and Greg have seen) have
nothing to do with PLplot but are instead due to bad Qt libraries or
bad Qt library dependencies on some platforms. In contrast to your
result and Greg's I have looked hard at qt results with valgrind on
Debian stable, and they have no severe memory management issues with
Qt4.8, and I think Andrew has done the same for his various Debian and
Ubuntu platforms.  Andrew and I do have different severe memory
management results for the Qt5 case; I get them with the epa_build of
Qt5, and he does not for several different distros.  But Qt4 has
always been completely reliable in this regard for us _for the
platforms we have access to_.  But this is obviously not the case for
you and Greg.

Anyhow, for now we are just trying to keep track of exactly which
platforms have good qt results with Qt4.8 and which do not.  However, we are
also interested in exactly which components of PLplot work for all our
different major configurations (shared libraries/dynamic devices,
shared libraries/non-dynamic devices, and static libraries/non-dynamic
devices. Thus, please try to get the script to finish
with components removed that are giving trouble.  (I gave that same
advice to Greg).

So, for example, to
drop everything Qt related you should specify

--cmake_added_options DEFAULT_NO_QT_DEVICES=ON -DENABLE_qt=OFF

when attempting to run scripts/comprehensive_testing.sh again.

Once you get that script to complete, we will note in the
corresponding report on the Wiki exactly which components had to be
dropped and why.

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
__

--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-04-10 Thread Alan W. Irwin
On 2015-04-10 21:54+0100 Andrew Ross wrote:

 [Hazen's poor qt result is] at odds with my tests a week or so back on Kubuntu
 14.10.

Hi Andrew:

Could you please report the details of those good comprehensive test
results at
https://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Testing%20Reports

Thanks in advance.

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
__

--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

2015-04-05 Thread Alan W. Irwin
On 2015-04-05 01:17-0700 Alan W. Irwin wrote:

 On 2015-04-04 23:11-0700 Greg Jung wrote:

 afaict these environment variables are essential for plots:

 PLPLOT_DRV_DIR=/usr/local/lib/plplot5.10.0/drivers
 PLPLOT_HOME=/usr/local/share/plplot5.10.0/

 DRV_DIR for dynamic loading, to get the driver_info files (.dll files
 are to be pick
 up in PATH) and PLPLOT_HOME for support files:

 Our build system has long (since 2000 or so) superseded those
 variables which are leftovers from the days when we essentially had no
 build system at all. So setting those varaiables should _never_ be
 needed. For example, I don't use them for any of my successful
 comprehensive testing of PLplot on the Linux and MinGW/MSYS platforms.
 Furthermore, they could introduce problems for your comprehensive testing
 issues on Cygwin. For example, the comprehensive testing script uses
 its own distinct build tree and install tree so using those variables
 to point to results from an entirely different install tree could
 introduce inconsistencies and also pollute build-tree results with
 install-tree results.  So my strong advice is to drop both
 PLPLOT_DRV_DIR and PLPLOT_HOME completely on all platforms with the
 possible exception of the advice Arjen gave to work around what I
 consider to be a bug in recent classical MSYS.

 My guess is you are following some severely dated documentation that still
 mentions PLPLOT_DRV_DIR and PLPLOT_HOME.  Could you tell me where that
 documentation is so I can update it to the post-2000 era?

 Thanks very much for including the script output in the tarball. The
 error occurred in the first attempt to run make.  So if you look at
 make.out it obviously has something to do with cairo so try removing
 all the cairo device drivers from the test (using
 -DDEFAULT_NO_CAIRO_DEVICES=ON which is much more convenient
 than setting all those -DPLD variables assocated with the many
 different cairo devices to
 OFF) and run the script again.

@Greg:

There is one issue with your script output that concerns me.  To quote
the relevant section from plplotcygwin.out

ctest_command=ctest
build_command=make
cmake_command=cmake -DENABLE_qt=OFF -DENABLE_wxwidgets=OFF -DPLD_wxwidgets=OFF
traditional_build_command=make

That cmake_command is not output from the script so I assume you
inserted that to show how you aliased cmake.  Thanks for that
additional information, but that change to the cmake command will
at minimum generate warnings (when cmake should be run without options
at all for the CMake-based build of the installed examples) 
and may generate subtle errors.

Instead you should simply use the script option

--cmake_added_options \
-DENABLE_qt=OFF -DENABLE_wxwidgets=OFF -DPLD_wxwidgets=OFF

and the script will use those options when necessary and drop them
when they should not be used.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

2015-04-04 Thread Arjen Markus
Hi Alan, Greg,



 -Original Message-
 From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]

 @Greg: You have much more experience with Cygwin than I do (since my actual
 experience is zero).  Nevertheless, historically there has been lots of 
 warnings on
 the CMake list that Cygwin users _must_ use the Cygwin version of CMake and 
 not
 the generic Windows version.  So because Arjen has had success with
 comprehensive testing on Cygwin in the past with that approach, and you are
 currently not having such success with a generic version of CMake rather than 
 the
 Cygwin version, I drew the conclusion you should try the Cygwin version of 
 CMake.

 @Arjen:

 Do you still use the Cygwin version of CMake for your Cygwin tests or is that
 historical advice no longer relevant so that the generic Windows version of 
 CMake
 that you can download for Kitware gives good results for you?

Under Cygwin I always use the Cygwin version of CMake. I simply do not know if 
that is still necessary and whether the generic Windows version would work as 
well. It is something that can easily be tested of course.

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.
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

2015-04-04 Thread Arjen Markus
Hi Alan,



 -Original Message-
 From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
 Sent: Saturday, April 04, 2015 9:04 PM
 To: Arjen Markus
 Cc: Greg Jung; Phil Rosenberg; Jim Dishaw; PLplot development list
 Subject: RE: Release status: call for comprehensive testing: Cygwin

 Hi Arjen:

 It is very encouraging from my release manager perspective that all 
 components of
 PLplot that you have enabled on Cygwin appear to be working for the shared 
 case
 so long as you exclude the traditional build of the installed examples.  
 From the
 output that you attached it appears a number of different things went wrong 
 with that
 traditional build and test of the installed examples.  We can address those 
 post-
 release.


 @Greg

 This (mostly) good result from Arjen on Cygwin obviously is sharply in 
 contrast with
 your own results where not even ctest worked on that platform.  Therefore, I 
 suggest
 you get in touch with Arjen to figure out exactly what he did.  Then 
 following that
 procedure rigourously should give you similar good results, and probably even 
 more
 importantly we should be able to document exactly what you did that should be
 avoided by others on Cygwin when they are running 
 scripts/comprehensive_test.sh.

Alan, are you sure it's Cygwin and not MSYS/MinGW where Greg's problems occur? 
I have seen some strange effects myself for that platform, unfortunately. I 
have to set:

set PLPLOT_DRV_DIR=.../drivers

that is set that environment variable to the directory that holds the *.drvinfo 
files, besides prepending the PATH variable with the directory containing the 
DLLs, even though things are running in the build tree. I think that is the 
same problem as Greg is experiencing with his MSYS/MinGW set-up.

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.
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-04-03 Thread Arjen Markus
Hi Greg,



It may or may not be related to your MSYS/MinGW issues, but I have to set some 
environment variables to get the examples under MSYS/MinGW to run (lack of 
drivers, font files). Plus I have some icky problems with make - it seems to 
become MicroSoft's nmake sometimes, at least I get nmake's start-up messages.



I have been unable so far to find the reason for these two issues. When things 
become a bit more relaxed, I intend to dig deeper. It is annoying enough.



Regards,



Arjen



 -Original Message-
 From: Greg Jung [mailto:gvj...@gmail.com]
 Sent: Friday, April 03, 2015 7:57 AM
 To: Alan W. Irwin
 Cc: PLplot development list
 Subject: Re: [Plplot-devel] Release status: call for comprehensive testing

 This is a long-standing cygwin warning, CMake no longer defines WIN32 on
 Cygwin!
 for those rip-van-winkles coming back to cygwin and somehow wanting
 WIN32 to be defined.
 I am very familar with the possible quirks that can arise with Cmake; if 
 there is a
 systemic failure it generally blows up in your face.  For the test I ran 
 cmake without
 modification - to do that I had to re-direct the cmake command to a pristine
 installation.  Although you may not feel comfortable doing so, trust me its 
 not
 cmake.

 In each setup there are naturally missing pieces.
 From my perspective,I need only libplplot.dll, libplplotcxx.dll,
 wingcc, svg, ps, null, Z, X, and maybe cairo devices, and wxwidget. If a 
 failure
 occurs because it isn't within this narrow requirement, that is irrelevant.

 I should note that, in running the raw cmake without mod and without setting
 variables, I am wholly reliant on the pkgconfig system to find libraries and 
 sniff
 dependencies, which directs cmake to look in the tree beneath the compiler
 distribution. So in that respect the plplot build is a raging success.
 If CMAKE were to find a library in /usr/lib this would be an error, because 
 that,
 analogous to the CYGWIN /usr/lib, is for programs to be run under the msys- 
 dll.
 Compiling for Mingw using MSYS Makefiles
 is really, from CMAKE point of view, a happy accident.  In that first run the 
 generator
 string turned out to be Unix Makefiles which seemed to work nevertheless, 
 in the
 make phase.  I re-ran mingw64 and specified MSYS Makefiles for the same 
 result.

 My mingw tests didn't result in an install_tree/ so I suspect make install 
 is not an
 included step in the script.  This is consistent with the ctest failure not 
 picking up ps
 driver etc.  I keep my usual plplot drivers in a directory not on the MSYS 
 path.
   All of the .dll files are there in the build directory but there is no 
 install directory.
 ctest -j4 fails - if I manually go (cwd) to the build directory and ctest  
 
 and get a series of the following messages:
 1: Testing front-end c
 1: x00c
 1: Unable to load driver: ps.
 1:
 1: *** PLPLOT ERROR, IMMEDIATE EXIT ***
 1: Unable to load driver
  so either ps.info isn't being found, or ps.dll, or both.  If it is working 
 for you, perhaps
 you are finding these in the old installation.

 greg@Homerw7 MINGW64 /d/bld/plplot-mingw32/output_tree $ ls -la total 420
 drwxr-xr-x 1 greg None  0 Apr  2 21:21 .
 drwxr-xr-x 1 greg None  0 Mar 28 16:15 ..
 -rw-r--r-- 1 greg None  19804 Mar 28 16:15 cmake.out
 -rw-r--r-- 1 greg None   5568 Mar 28 17:06 ctest.out
 -rw-r--r-- 1 greg None 397277 Mar 28 16:16 make.out $ ls -la 
 ../build_tree/dll total
 2744
 drwxr-xr-x 1 greg None  0 Mar 28 16:16 .
 drwxr-xr-x 1 greg None  0 Mar 30 08:31 ..
 -rwxr-xr-x 1 greg None 143271 Mar 28 16:16 cairo.dll -rwxr-xr-x 1 greg None 
 118558
 Mar 28 16:15 libcsirocsa.dll
 -rw-r--r-- 1 greg None   6542 Mar 28 16:15 libcsirocsa.dll.a
 -rwxr-xr-x 1 greg None 509403 Mar 28 16:16 libplplot.dll
 -rw-r--r-- 1 greg None 194548 Mar 28 16:16 libplplot.dll.a -rwxr-xr-x 1 greg 
 None
 190112 Mar 28 16:16 libplplotcxx.dll
 -rw-r--r-- 1 greg None 171696 Mar 28 16:16 libplplotcxx.dll.a -rwxr-xr-x 1 
 greg None
 278549 Mar 28 16:16 libplplottcltk.dll
 -rw-r--r-- 1 greg None   3950 Mar 28 16:16 libplplottcltk.dll.a
 -rwxr-xr-x 1 greg None  92430 Mar 28 16:16 libplplottcltk_Main.dll
 -rw-r--r-- 1 greg None   1502 Mar 28 16:16 libplplottcltk_Main.dll.a
 -rwxr-xr-x 1 greg None 120392 Mar 28 16:15 libqsastime.dll
 -rw-r--r-- 1 greg None   3874 Mar 28 16:15 libqsastime.dll.a
 -rwxr-xr-x 1 greg None  96826 Mar 28 16:15 libtclmatrix.dll
 -rw-r--r-- 1 greg None   2782 Mar 28 16:15 libtclmatrix.dll.a
 -rwxr-xr-x 1 greg None  90308 Mar 28 16:16 mem.dll -rwxr-xr-x 1 greg None  
 95259
 Mar 28 16:16 ntk.dll -rwxr-xr-x 1 greg None  82507 Mar 28 16:16 null.dll 
 -rwxr-xr-x 1
 greg None 120304 Mar 28 16:16 ps.dll -rwxr-xr-x 1 greg None 108182 Mar 28 
 16:16
 svg.dll -rwxr-xr-x 1 greg None 106513 Mar 28 16:16 test-drv-info.exe 
 -rwxr-xr-x 1
 greg None 107419 Mar 28 16:16 wingcc.dll -rwxr-xr-x 1 greg None 100481 Mar 28
 16:16 xfig.dll


 Here now is a re-run of the mingw64 test, under msys2 using MSYS Makefiles

Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

2015-04-03 Thread Greg Jung
In Cygwin, I do use the cygwin cmake; but it isn't distributed by
cygwin, I built it from source.  At one point I tried the windows
cmake from cygwin and it failed miserably.

On Fri, Apr 3, 2015 at 12:20 PM, Alan W. Irwin
ir...@beluga.phys.uvic.ca wrote:
 On 2015-04-02 22:57-0700 Greg Jung wrote:

 This is a long-standing cygwin warning, CMake no longer defines WIN32
 on Cygwin!
 for those rip-van-winkles coming back to cygwin and somehow wanting
 WIN32 to be defined.
 I am very familar with the possible quirks that can arise with Cmake;
 if there is a systemic failure
 it generally blows up in your face.  For the test I ran cmake without
 modification - to do that I had to re-direct the cmake command to a
 pristine installation.  Although you may not feel comfortable doing
 so,
 trust me its not cmake.


 @Greg: You have much more experience with Cygwin than I do (since my
 actual experience is zero).  Nevertheless, historically there has been
 lots of warnings on the CMake list that Cygwin users _must_ use the
 Cygwin version of CMake and not the generic Windows version.  So
 because Arjen has had success with comprehensive testing on Cygwin in
 the past with that approach, and you are currently not having such
 success with a generic version of CMake rather than the Cygwin
 version, I drew the conclusion you should try the Cygwin version of
 CMake.

 @Arjen:

 Do you still use the Cygwin version of CMake for your Cygwin
 tests or is that historical advice no longer relevant so that the
 generic Windows version of CMake that you can download for Kitware
 gives good results for you?

 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
 __

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing: MinGW-w64/MSYS2

2015-04-03 Thread Greg Jung
The cmake I specify for MSYS is a vanilla cmake downloaded from
cmake.org; I use this because all of my other CMakes use scripts I
modified.

Cmake for Msys needs to use msys make, not mingw32-make; otherwise you
want to do a mingw build which involves hiding sh from the PATH,
using CMD.exe,  etc. etc. I tried it once it fell pretty quickly.

I really couldn't quote an example where msys(1) is so different from msys2
that msys2 is more unix-like.   Both use the same name-conversion
rules and both use an interface layer to look like linux.  When I
installed msys2
it succeeded in a build that mingw(org)/msys was failing.  Then I
discovered that most of the libraries I was building were already
pre-built and distributed, via the MSYS2/pacman distribution program.

I'm on Linux today, will send interim results under a different subject.

On Fri, Apr 3, 2015 at 12:26 PM, Alan W. Irwin
ir...@beluga.phys.uvic.ca wrote:
 On 2015-04-02 22:57-0700 Greg Jung wrote:


 In each setup there are naturally missing pieces.

 From my perspective,I need only libplplot.dll, libplplotcxx.dll,

 wingcc, svg, ps, null, Z, X, and maybe cairo devices, and wxwidget. If
 a failure occurs because it isn't within this narrow requirement, that
 is irrelevant.


 Hi Greg:

 But if the failure causes premature stopping of the test, then you
 don't have a complete test coverage for the components that are
 relevant to your needs.  So by all means for now explicitly drop all
 components that you don't want to comprehensively test (e.g., by using
 appropriate -DENABLE_???=OFF and -DPLD_???=OFF options via the
 --cmake_added_options option of scripts/comprehensive_test.sh) to
 allow you to complete the tests for a narrow set of components. Once
 such a limited test completes without failures, then we can note that
 success on our wiki and use it (if you are willing to make that exact
 same test again) as a benchmark for tests near the end of future
 release cycles to insure there are no regressions in the part of
 PLplot that interests you.

 I should note that, in running the raw cmake without mod and without
 setting variables,
 I am wholly reliant on the pkgconfig system to find libraries and
 sniff dependencies, which directs
 cmake to look in the tree beneath the compiler distribution.


 Actually, CMake finds software using so-called find modules.  A few
 of those use pkg-config, but many do not.

 in that respect the plplot build is a raging success.


 I agree that CMake is very good about finding software using whatever
 methods are used in the appropriate find module.  However, when you
 have multiple versions of the same software installed or if some of
 your installed software is installed in a non-standard location, you
 do have to direct CMake to find the correct software version that is
 appropriate for a particular platform by (typically) setting the
 environment variables PATH, CMAKE_INCLUDE_PATH, CMAKE_LIBRARY_PATH,
 and PKG_CONFIG_PATH.

 If CMAKE were to find a library in /usr/lib this would be an error,
 because that, analogous to the CYGWIN /usr/lib, is for programs to be
 run under the msys- dll.


 Well, the user must set environment variables appropriate to each
 tested platform to give hints to CMake about finding software, and if
 they fail to set up a platform properly that way, it is a user error.

 Compiling for Mingw using MSYS Makefiles
 is really, from CMAKE point of view, a happy accident.  In that first
 run the generator string turned out to be Unix Makefiles which
 seemed to work nevertheless, in the make phase.  I re-ran mingw64 and
 specified MSYS Makefiles for the same result.


 Not quite sure what you mean here because first you refer to Mingw,
 then to mingw64.  I suspect in both cases you meant MinGW-w64/MSYS2
 rather than MinGW/MSYS, but I am not completely sure.  Neverthess, I
 strongly agree with the principle that the generator you should use is
 dependent on platform.  For classical MinGW with no MSYS it is MinGW
 Makefiles (and you must also specify --build_command mingw32-make).
 For classicial MinGW/MSYS it is MSYS Makefiles.  For Cygwin it is
 Unix Makefiles.  My _guess_ for MinGW-w64/MSYS2 is that it should be
 Unix Makefiles, (since that platform is a light-weight variant of
 modern Cygwin), but the exact generator to use is something you will
 have to discover for yourself since you are the first (that I am aware
 of) that has tried comprehensive testing on that particular platform.

 My mingw tests didn't result in an install_tree/ so I suspect make
 install is not an included step
 in the script.  This is consistent with the ctest failure not picking
 up ps driver etc.  I keep my usual
 plplot drivers in a directory not on the MSYS path.
  All of the .dll files are there in the build directory but there is
 no install directory.
 ctest -j4 fails - if I manually go (cwd) to the build directory and ctest
  
 and get a series of the following messages:
 1: Testing front-end c
 1: x00c
 

Re: [Plplot-devel] Release status: call for comprehensive testing: Cygwin

2015-04-03 Thread Alan W. Irwin
On 2015-04-03 14:06-0700 Greg Jung wrote:

 In Cygwin, I do use the cygwin cmake; but it isn't distributed by
 cygwin, I built it from source.  At one point I tried the windows
 cmake from cygwin and it failed miserably.

@Greg:

Thanks for that clarification.  I agree that cmake built on Cygwin
should work fine to build and test PLplot on Cygwin.  Yet your results
are different from Arjen's historical good comprehensive test results
on Cygwin (where he did use the Cygwin install version of CMake).  So
either that difference is significant (which I agree is unlikely, but
you never know), there is some CMake version issue between the CMake
version you are using and the CMake version that Arjen historically
used (much more likely), something is wrong with your additional setup
on Cygwin (e.g., environment variables that you set that might
interfere with our testing framework, also fairly likely), or else
there is some comprehensive testing regression for PLplot for the
Cygwin platform.

@Arjen, Phil, and Jim:

As release manager, that latter possibility of a regression in
comprehensive testing on the Cygwin platform really concerns me, and I
ask at least one of you guys to confirm/deny that possibility by
simply running scripts/comprehensive_test.sh on Cygwin with
appropriate environmental variables set (ideally with a source
script that you run from using the bash source command to keep
everything easily and automatically reproducible) to setup the Cygwin
platform for the PLplot build and test.

N.B. I emphasize sourcing a source script from bash and running
scripts/comprehensive_test.sh as opposed to piece-meal tests done by
hand since (a) the script result should be completely automated and
reproducible if you have set up the platform properly, and (b)
comprehensive testing is so much more powerful than piece-meal tests.
So I would appreciate hearing from any of you quickly if you are in a
good position to run that script.

Meanwhile, I am going to continue with the release process culminating
(I hope this weekend) with starting scripts/comprehensive_test.sh for
the MinGW/MSYS/Wine case.  That result will take roughly 3 days to
complete (since Wine startup of each command is so much slower than
what happens for Microsoft Windows).  Once I have a good comprehensive
test result on MinGW/MSYS/Wine (likely Tuesday at the earliest) I plan
to go ahead with the release unless one of you confirms Greg's result
that running scripts/comprehensive_test.sh no longer works on Cygwin.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-04-02 Thread Greg Jung
This is a long-standing cygwin warning, CMake no longer defines WIN32
on Cygwin!
for those rip-van-winkles coming back to cygwin and somehow wanting
WIN32 to be defined.
I am very familar with the possible quirks that can arise with Cmake;
if there is a systemic failure
it generally blows up in your face.  For the test I ran cmake without
modification - to do that I had to re-direct the cmake command to a
pristine installation.  Although you may not feel comfortable doing
so,
trust me its not cmake.

In each setup there are naturally missing pieces.
From my perspective,I need only libplplot.dll, libplplotcxx.dll,
wingcc, svg, ps, null, Z, X, and maybe cairo devices, and wxwidget. If
a failure occurs because it isn't within this narrow requirement, that
is irrelevant.

I should note that, in running the raw cmake without mod and without
setting variables,
I am wholly reliant on the pkgconfig system to find libraries and
sniff dependencies, which directs
cmake to look in the tree beneath the compiler distribution. So in
that respect the plplot build is a raging success.
If CMAKE were to find a library in /usr/lib this would be an error,
because that, analogous to the CYGWIN /usr/lib, is for programs to be
run under the msys- dll.  Compiling for Mingw using MSYS Makefiles
is really, from CMAKE point of view, a happy accident.  In that first
run the generator string turned out to be Unix Makefiles which
seemed to work nevertheless, in the make phase.  I re-ran mingw64 and
specified MSYS Makefiles for the same result.

My mingw tests didn't result in an install_tree/ so I suspect make
install is not an included step
in the script.  This is consistent with the ctest failure not picking
up ps driver etc.  I keep my usual
plplot drivers in a directory not on the MSYS path.
  All of the .dll files are there in the build directory but there is
no install directory.
ctest -j4 fails - if I manually go (cwd) to the build directory and ctest  
and get a series of the following messages:
1: Testing front-end c
1: x00c
1: Unable to load driver: ps.
1:
1: *** PLPLOT ERROR, IMMEDIATE EXIT ***
1: Unable to load driver
 so either ps.info isn't being found, or ps.dll, or both.  If it is
working for you, perhaps you are finding these in the old
installation.

greg@Homerw7 MINGW64 /d/bld/plplot-mingw32/output_tree
$ ls -la
total 420
drwxr-xr-x 1 greg None  0 Apr  2 21:21 .
drwxr-xr-x 1 greg None  0 Mar 28 16:15 ..
-rw-r--r-- 1 greg None  19804 Mar 28 16:15 cmake.out
-rw-r--r-- 1 greg None   5568 Mar 28 17:06 ctest.out
-rw-r--r-- 1 greg None 397277 Mar 28 16:16 make.out
$ ls -la ../build_tree/dll
total 2744
drwxr-xr-x 1 greg None  0 Mar 28 16:16 .
drwxr-xr-x 1 greg None  0 Mar 30 08:31 ..
-rwxr-xr-x 1 greg None 143271 Mar 28 16:16 cairo.dll
-rwxr-xr-x 1 greg None 118558 Mar 28 16:15 libcsirocsa.dll
-rw-r--r-- 1 greg None   6542 Mar 28 16:15 libcsirocsa.dll.a
-rwxr-xr-x 1 greg None 509403 Mar 28 16:16 libplplot.dll
-rw-r--r-- 1 greg None 194548 Mar 28 16:16 libplplot.dll.a
-rwxr-xr-x 1 greg None 190112 Mar 28 16:16 libplplotcxx.dll
-rw-r--r-- 1 greg None 171696 Mar 28 16:16 libplplotcxx.dll.a
-rwxr-xr-x 1 greg None 278549 Mar 28 16:16 libplplottcltk.dll
-rw-r--r-- 1 greg None   3950 Mar 28 16:16 libplplottcltk.dll.a
-rwxr-xr-x 1 greg None  92430 Mar 28 16:16 libplplottcltk_Main.dll
-rw-r--r-- 1 greg None   1502 Mar 28 16:16 libplplottcltk_Main.dll.a
-rwxr-xr-x 1 greg None 120392 Mar 28 16:15 libqsastime.dll
-rw-r--r-- 1 greg None   3874 Mar 28 16:15 libqsastime.dll.a
-rwxr-xr-x 1 greg None  96826 Mar 28 16:15 libtclmatrix.dll
-rw-r--r-- 1 greg None   2782 Mar 28 16:15 libtclmatrix.dll.a
-rwxr-xr-x 1 greg None  90308 Mar 28 16:16 mem.dll
-rwxr-xr-x 1 greg None  95259 Mar 28 16:16 ntk.dll
-rwxr-xr-x 1 greg None  82507 Mar 28 16:16 null.dll
-rwxr-xr-x 1 greg None 120304 Mar 28 16:16 ps.dll
-rwxr-xr-x 1 greg None 108182 Mar 28 16:16 svg.dll
-rwxr-xr-x 1 greg None 106513 Mar 28 16:16 test-drv-info.exe
-rwxr-xr-x 1 greg None 107419 Mar 28 16:16 wingcc.dll
-rwxr-xr-x 1 greg None 100481 Mar 28 16:16 xfig.dll


Here now is a re-run of the mingw64 test, under msys2 using MSYS Makefiles
$ ./comprehensive_test.sh --prefix /d/bld/plplot-mingw64-2
--generator_string 'MSYS Makefiles' --build_command 'make -j6'
--cmake_command '/d/programs/CMake-3.1.1-win32-x86/bin/CMake'
Summary of options used for these tests

prefix=/d/bld/plplot-mingw64-2

do_clean_as_you_go=yes

generator_string=MSYS Makefiles

ctest_command=ctest -j4
build_command=make -j6
cmake_command=/d/programs/CMake-3.1.1-win32-x86/bin/CMake

Each of the steps in this comprehensive test may take a while
Prepend /d/bld/plplot-mingw64-2/shared/build_tree/dll to the original PATH
/d/programs/CMake-3.1.1-win32-x86/bin/CMake in the build tree
make -j6 VERBOSE=1 in the build tree
ctest -j4 in the build tree

$ ps
  PIDPPIDPGID WINPID   TTY UIDSTIME COMMAND
 532853205008   3520  pty0197609 21:49:04 /usr/bin/bash
 5516

Re: [Plplot-devel] Release status: call for comprehensive testing

2015-04-02 Thread Alan W. Irwin
On 2015-03-30 12:42-0700 Alan W. Irwin wrote:

 There is a big warning in plplot-cygwin/output_tree/cmake.out (for
 version 3.0.1) about CMake no longer defines WIN32 on Cygwin!

Hi Greg:

I believe I have now found the source of that warning message which is
(according to cmake mailing list messages I have read) that you were
using some non-Cygwin version of the cmake command, and Cygwin
requires you to use an officially packaged cmake command instead
in order for CMake-based builds to work properly on that platform.

For example, from
https://cygwin.com/packages/x86/cmake/cmake-3.1.2-1 it appears this
particular offical Cygwin cmake binary is installed at
/usr/bin/cmake.exe, and the corresponding cmake modules are located at
/usr/share/cmake-3.1.2/Modules while from your cmake.out output you
were instead using a cmake version whose modules were installed in
/opt/local/!

So the next time you run a Cygwin test you should be sure to (a) have
a version of CMake installed from a Cygwin package, and (b) manipulate
your PATH before running scripts/comprehensive_test.sh so that is the
cmake version that is used.

Since MinGW-w64/MSYS2 is very similar to Cygwin, I assume that
platform has a similar requirement, i.e., in that case you must
install and use the MinGW-w64/MSYS2 version of cmake which probably
explains (at least in part) the bad results you were getting
for your tests on your various MSYS2 platforms.

Note also, that Cygwin and (likely) MSYS2 are unique in this regard
and for Unix platforms a generic Unix version of cmake can be used and
for Windows platforms like MSVC and MinGW/MSYS, a generic Windows
version of cmake can be used.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-31 Thread Arjen Markus
Hi Alan,



 -Original Message-
 From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]

 @Arjen and Phil, will both of you please look at the cygwin.tgz attachment?

 There is a big warning in plplot-cygwin/output_tree/cmake.out (for version 
 3.0.1)
 about CMake no longer defines WIN32 on Cygwin! Have either of you run into 
 this
 issue for CMake on Cygwin?  There is advice in that warning about what Greg
 should do to overcome this issue but with several options.  Could you advise 
 him
 which option to take (and also update the Cywin part of our wiki accordingly)?

That message has been around for a while - since 2.8.4 if I am not mistaken (I 
found that version number while googling for the option I use to quiet CMake 
about it). The option

-DCMAKE_LEGACY_CYGWIN_WIN32=OFF will suppress it and I have not seen any 
problems relating to WIN32. But that may come when building with the static 
option.

I have not received any attachment, so unfortunately I can not have a closer 
look right now.

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.
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-31 Thread Arjen Markus
Hi Alan,


 @Arjen and Phil, will both of you please look at the cygwin.tgz attachment?

 There is a big warning in plplot-cygwin/output_tree/cmake.out (for version 
 3.0.1)
 about CMake no longer defines WIN32 on Cygwin! Have either of you run into 
 this
 issue for CMake on Cygwin?  There is advice in that warning about what Greg
 should do to overcome this issue but with several options.  Could you advise 
 him
 which option to take (and also update the Cywin part of our wiki accordingly)?

I have tried building Plplot using static libraries (-DBUILD_SHARED_LIBS=OFF 
-DENABLE_DYNDRIVERS=ON), but this fails on something in the Qt device:

cd /cygdrive/d/plplot-svn/build-cygwin-static/bindings/qt_gui  
/usr/bin/c++.exe   -DPLPLOT_HAVE_CONFIG_H -DQT_CORE_LIB -DQT_GUI_LIB 
-DQT_NO_DEBUG -DQT_SVG_LIB -I/cygdrive/d/plplot-svn/plplot-git/include 
-I/cygdrive/d/plplot-svn/plplot-git/lib/qsastime 
-I/cygdrive/d/plplot-svn/plplot-git/lib/nistcd 
-I/cygdrive/d/plplot-svn/plplot-git/drivers 
-I/cygdrive/d/plplot-svn/build-cygwin-static 
-I/cygdrive/d/plplot-svn/build-cygwin-static/include -I/usr/include/qt4 
-I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore
-DUSINGDLL -o CMakeFiles/plplotqt.dir/plqt.cpp.o -c 
/cygdrive/d/plplot-svn/plplot-git/bindings/qt_gui/plqt.cpp

/cygdrive/d/plplot-svn/plplot-git/bindings/qt_gui/plqt.cpp:28:28: error: 
definition of 'int vectorize' is marked 'dllimport'

PLDLLIMPEXP_QT_DATA( int ) vectorize = 0;

^

/cygdrive/d/plplot-svn/plplot-git/bindings/qt_gui/plqt.cpp:28:28: warning: 
'vectorize' redeclared without dllimport attribute: previous dllimport ignored 
[-Wattributes]

/cygdrive/d/plplot-svn/plplot-git/bindings/qt_gui/plqt.cpp:29:28: error: 
definition of 'int lines_aa' is marked 'dllimport'

PLDLLIMPEXP_QT_DATA( int ) lines_aa  = 1;

I will retry it turning the Qt devices off. But this is clearly an issue 
connected to the WIN32 macro.

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.
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-31 Thread Alan W. Irwin
On 2015-03-31 09:33- Arjen Markus wrote:

 Hi Alan,


 @Arjen and Phil, will both of you please look at the cygwin.tgz attachment?

 There is a big warning in plplot-cygwin/output_tree/cmake.out (for version 
 3.0.1)
 about CMake no longer defines WIN32 on Cygwin! Have either of you run into 
 this
 issue for CMake on Cygwin?  There is advice in that warning about what Greg
 should do to overcome this issue but with several options.  Could you advise 
 him
 which option to take (and also update the Cywin part of our wiki 
 accordingly)?

 I have tried building Plplot using static libraries (-DBUILD_SHARED_LIBS=OFF 
 -DENABLE_DYNDRIVERS=ON), but this fails on something in the Qt device:

 cd /cygdrive/d/plplot-svn/build-cygwin-static/bindings/qt_gui  
 /usr/bin/c++.exe   -DPLPLOT_HAVE_CONFIG_H -DQT_CORE_LIB -DQT_GUI_LIB 
 -DQT_NO_DEBUG -DQT_SVG_LIB -I/cygdrive/d/plplot-svn/plplot-git/include 
 -I/cygdrive/d/plplot-svn/plplot-git/lib/qsastime 
 -I/cygdrive/d/plplot-svn/plplot-git/lib/nistcd 
 -I/cygdrive/d/plplot-svn/plplot-git/drivers 
 -I/cygdrive/d/plplot-svn/build-cygwin-static 
 -I/cygdrive/d/plplot-svn/build-cygwin-static/include -I/usr/include/qt4 
 -I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore   
  -DUSINGDLL -o CMakeFiles/plplotqt.dir/plqt.cpp.o -c 
 /cygdrive/d/plplot-svn/plplot-git/bindings/qt_gui/plqt.cpp

 /cygdrive/d/plplot-svn/plplot-git/bindings/qt_gui/plqt.cpp:28:28: error: 
 definition of 'int vectorize' is marked 'dllimport'

 PLDLLIMPEXP_QT_DATA( int ) vectorize = 0;

^

 /cygdrive/d/plplot-svn/plplot-git/bindings/qt_gui/plqt.cpp:28:28: warning: 
 'vectorize' redeclared without dllimport attribute: previous dllimport 
 ignored [-Wattributes]

 /cygdrive/d/plplot-svn/plplot-git/bindings/qt_gui/plqt.cpp:29:28: error: 
 definition of 'int lines_aa' is marked 'dllimport'

 PLDLLIMPEXP_QT_DATA( int ) lines_aa  = 1;

 I will retry it turning the Qt devices off. But this is clearly an issue 
 connected to the WIN32 macro.

Hi Arjen:

Gack.  I am really glad you found this bug in setting the -DUSINGDLL
compile flag for libplplotqt source files (and also for smoke
bindings) for the static library case.  This bug was caused by a commit made
by me back in 2013.  One of our users has just run into this as well
(see recent traffic on plplot-general).

The funny thing is, this bug (which only affects Windows systems where
plplotqt is being built) has been around so long without detection.  I
am pretty sure that running scripts/comprehensive_testing.sh anytime
since 2013 on a Windows system with access to Qt would have found this
bug so this example emphasizes once again how important such
comprehensive testing (on fully loaded systems) is.

I have fixed this bug on my local system but cannot (yet) push it
to SF because there is a complete SF outage at this time!

So stay tuned to the git feed, and once this fix has been pushed, please
follow up with the above test again (as well as comprehensive testing
please).

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-31 Thread Alan W. Irwin
On 2015-03-31 11:05-0700 Greg Jung wrote:

 Here is tarball og the output directory from recent fully-completed
 Suse-13.2 test.
 I did terminate interactive testing at the end, by killing windows,
 the strip chart was going very slow.  But the wx Viewers looked great.


Hi Greg:

Thanks very much for these test results.  I don't think it matters
much in this particular case, but please get into the habit of
attaching the script output for this and your other platform tests.

From the WARNING messages in
opensuse-13.2/shared/output_tree/cmake.out your test has been
artificially limited by not installing the appropriate system
software.  Just taking those WARNING messages in order,
that missing system software includes swig (which means the
java, python, octave, and lua bindings must be dropped), development
libraries for Tcl/Tk/Itcl/Itk (which means all Tcl-related bindings
must be dropped), an Ada compiler (which means the Ada binding must be
dropped), a D compiler (which means the D binding must be dropped),
shapelib (which means interesting parts of the API and also parts of
example 19 must be dropped), qhull (which means interesting parts of
the API and also parts of example 21 must be dropped), libLASi (which
means the psttf device driver must be dropped), the development
version of Qt4 (which means the qt device driver must be dropped),
libharu (or libhpdf) (which means the pdf device driver must be
dropped), and the OCaml development libraries (which means our ocaml
binding must be dropped).  At least swig and development versions of
Tcl/Tk/Itcl/Itk and Qt4 should be readily available on OpenSuSe so I
suggest you install at least those (assuming you have control of that
machine) to increase the power of your test.

Because you terminated the test prematurely, you only got through
roughly one third of it (i.e., you didn't get to the nodynamic and
static parts of this comprehensive test).  The slowness of the
wxPLViewer application for example 17 is a well-known bug for new
wxwidgets, and the proper way to get out of it without terminating the
test is to to hit the file menu button on the wxPLViewer which
provides an exit option which you should take.  Also, the -np option
(the No pause option which is used for this test to try and reduce
how much the user has to interact with the test) is not honored (yet)
by new wxwidgets which means you have to either use the exit option to
immediately exit each of the wxwidgets examples (as for example 17) or
else hit enter to get through all the pages and eventually exit.
Similarly, if/when you install the development versions of Tcl etc.,
you will find a few of the Tcl examples do not honor the -np option so
you will have to get through them by hand, e.g., by hitting the enter
key to move through some of the pages.

So although we have reduced the tedium of running the interactive part
of the comprehensive tests an enormous amount by using the -np option,
honoring that option is not yet perfect so there still is a certain
amount of patience and interaction required to get through the
interactive part of the comprehensive test.

N.B. You can use the --do_test_interactive no option for
scripts/comprehensive_tests.sh if you want to completely drop the
interactive part of the tests. Such noninteractive comprehensive test
are well defined, and it certainly would still be worthwhile for me to
report such incomplete results on our wiki if you ran out of patience
with dealing with the interactive part of the test.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-31 Thread Alan W. Irwin
On 2015-03-31 09:31-0700 Alan W. Irwin wrote:

 Hi Arjen:

 Gack.  I am really glad you found this bug in setting the -DUSINGDLL
 compile flag for libplplotqt source files (and also for smoke
 bindings) for the static library case.  This bug was caused by a commit made
 by me back in 2013.  One of our users has just run into this as well
 (see recent traffic on plplot-general).

 The funny thing is, this bug (which only affects Windows systems where
 plplotqt is being built) has been around so long without detection.  I
 am pretty sure that running scripts/comprehensive_testing.sh anytime
 since 2013 on a Windows system with access to Qt would have found this
 bug so this example emphasizes once again how important such
 comprehensive testing (on fully loaded systems) is.

 I have fixed this bug on my local system but cannot (yet) push it
 to SF because there is a complete SF outage at this time!

 So stay tuned to the git feed, and once this fix has been pushed, please
 follow up with the above test again (as well as comprehensive testing
 please).

SF now working again, and I have pushed this bug fix (commit id
b6b60d1).  Please test that this solves the issue.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-31 Thread Greg Jung
Here is tarball og the output directory from recent fully-completed
Suse-13.2 test.
 I did terminate interactive testing at the end, by killing windows,
 the strip chart was going very slow.  But the wx Viewers looked great.




On Tue, Mar 31, 2015 at 9:31 AM, Alan W. Irwin
ir...@beluga.phys.uvic.ca wrote:
 On 2015-03-31 09:33- Arjen Markus wrote:

 Hi Alan,


 @Arjen and Phil, will both of you please look at the cygwin.tgz
 attachment?

 There is a big warning in plplot-cygwin/output_tree/cmake.out (for
 version 3.0.1)
 about CMake no longer defines WIN32 on Cygwin! Have either of you run
 into this
 issue for CMake on Cygwin?  There is advice in that warning about what
 Greg
 should do to overcome this issue but with several options.  Could you
 advise him
 which option to take (and also update the Cywin part of our wiki
 accordingly)?

 I have tried building Plplot using static libraries
 (-DBUILD_SHARED_LIBS=OFF -DENABLE_DYNDRIVERS=ON), but this fails on
 something in the Qt device:

 cd /cygdrive/d/plplot-svn/build-cygwin-static/bindings/qt_gui 
 /usr/bin/c++.exe   -DPLPLOT_HAVE_CONFIG_H -DQT_CORE_LIB -DQT_GUI_LIB
 -DQT_NO_DEBUG -DQT_SVG_LIB -I/cygdrive/d/plplot-svn/plplot-git/include
 -I/cygdrive/d/plplot-svn/plplot-git/lib/qsastime
 -I/cygdrive/d/plplot-svn/plplot-git/lib/nistcd
 -I/cygdrive/d/plplot-svn/plplot-git/drivers
 -I/cygdrive/d/plplot-svn/build-cygwin-static
 -I/cygdrive/d/plplot-svn/build-cygwin-static/include -I/usr/include/qt4
 -I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore
 -DUSINGDLL -o CMakeFiles/plplotqt.dir/plqt.cpp.o -c
 /cygdrive/d/plplot-svn/plplot-git/bindings/qt_gui/plqt.cpp

 /cygdrive/d/plplot-svn/plplot-git/bindings/qt_gui/plqt.cpp:28:28: error:
 definition of 'int vectorize' is marked 'dllimport'

 PLDLLIMPEXP_QT_DATA( int ) vectorize = 0;

^

 /cygdrive/d/plplot-svn/plplot-git/bindings/qt_gui/plqt.cpp:28:28: warning:
 'vectorize' redeclared without dllimport attribute: previous dllimport
 ignored [-Wattributes]

 /cygdrive/d/plplot-svn/plplot-git/bindings/qt_gui/plqt.cpp:29:28: error:
 definition of 'int lines_aa' is marked 'dllimport'

 PLDLLIMPEXP_QT_DATA( int ) lines_aa  = 1;

 I will retry it turning the Qt devices off. But this is clearly an issue
 connected to the WIN32 macro.


 Hi Arjen:

 Gack.  I am really glad you found this bug in setting the -DUSINGDLL
 compile flag for libplplotqt source files (and also for smoke
 bindings) for the static library case.  This bug was caused by a commit made
 by me back in 2013.  One of our users has just run into this as well
 (see recent traffic on plplot-general).

 The funny thing is, this bug (which only affects Windows systems where
 plplotqt is being built) has been around so long without detection.  I
 am pretty sure that running scripts/comprehensive_testing.sh anytime
 since 2013 on a Windows system with access to Qt would have found this
 bug so this example emphasizes once again how important such
 comprehensive testing (on fully loaded systems) is.

 I have fixed this bug on my local system but cannot (yet) push it
 to SF because there is a complete SF outage at this time!

 So stay tuned to the git feed, and once this fix has been pushed, please
 follow up with the above test again (as well as comprehensive testing
 please).


 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-opensuse13.2.tgz
Description: GNU Zip compressed data
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-30 Thread Greg Jung
  Mingw/msys:
Because I have cmake modified to look in /usr/local
and such for libraries and such (not a good idea, I know now), I added
the option --cmake_command to the script and used

--cmake_command=/d/path-to-cmake/bin/cmake.exe and the make completed
ok but the ctest
hung at example/c/x00c; I had to kill the process.
I'm sending gzipped- tar files to you separately because the list
filters may kill the message altogether.

About Msys/Msys2:
I suppose there are 4 distinct platforms I use in Windows: Msys2 with
minw32/, with mingw64/, and msys1 with mingw standard (mingw.org).
And cygwin64.  For the purposes of these tests I'll label
them mingw32, mingw64, and mingworg.  Msys or cygwin run  posix
compatibility layers and maintain their own mounted file systems
within windows'  file system.  They can also interpret windows-style
pathnames. Both Msys are derived from cygwin.
Cygwin tries hard to be your unix in the dos-box but msys is
avowedly limited in scope to the support of cross-compilations of UNIX
builds on the windows' platform.  To do this it generally snoops on
the command line and looks for likely places that filenames would
benefit
from translation from the msys-mounted to the win-style, i.e. /usr/lib
becomes D:/path-to-msys/lib.
For cygwin, everything is kept in posix-style notation.

 As far as msys goes, msys2 is built to be 64-bit, to keep up better
with the modern cygwin layer.
Msys2 uses a pacman-based packaging update system,
https://sourceforge.net/p/msys2/wiki/MSYS2%20installation/
  The default configuration is, /msys64 toplevel directory which
becomes /. GCC toolchain,
complete with support libraries, are installed from the mingw-w64
project into /mingw64 and, for
native 32-bit builds, /mingw32.  The big convenience for me, besides
the pre-built libraries, was
that someone decided which exception and thread models to use!!  (I
suppose they could be swapped out if needed).





On Sun, Mar 29, 2015 at 10:01 AM, Alan W. Irwin
ir...@beluga.phys.uvic.ca wrote:
 On 2015-03-28 22:20-0700 Alan W. Irwin wrote:

 Also, when you report back again, will you please always specify the
 scripts/comprehensive_test.sh options you used in every different
 platform case?  The easiest way to do that is to always include
 everything output from the script rather than bits and pieces like
 above.  So ideally you would capture the whole output from the script
 in a file, compress that file, and attach it to your post here (as
 well as tarballs of comprehensive_test_disposeable/shared/output_tree,
 comprehensive_test_disposeable/nondynamic/output_tree, and
 comprehensive_test_disposeable/static/output_tree) for each platform
 you test.


 Hi Greg:

 One other point I should have mentioned is you should use a different
 --prefix option for each separate run of scripts/comprehensive_test.sh
 to keep your comprehensive testing results for various platforms (if
 done on the same computer) completely separate from each other.


 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
 __

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-30 Thread Alan W. Irwin
On 2015-03-30 12:14-0700 Alan W. Irwin wrote:

 On 2015-03-30 10:40-0700 Greg Jung wrote:

 Here are  gzipped- tar files sent separately because the list
 filters may kill the message altogether.

 Our mailing list does not kill tarballs in my experience. So to test
 that in this case, I am forwarding this to the list.  Also, I hope it
 arrives there because I need help with some of these issues from the
 others there.

@Greg: there appears to be no problem with those attachments.

@Arjen and Phil, will both of you please look at the cygwin.tgz attachment?

There is a big warning in plplot-cygwin/output_tree/cmake.out (for
version 3.0.1) about CMake no longer defines WIN32 on Cygwin! Have
either of you run into this issue for CMake on Cygwin?  There is
advice in that warning about what Greg should do to overcome this
issue but with several options.  Could you advise him which option to
take (and also update the Cywin part of our wiki accordingly)?

@Greg:

Thanks very much for your four preliminary platform reports, but to
make complete sense of those  I need the other
information I requested which is the complete output from
scripts/comprehensive_test.sh in each of the four cases.

On bash you can collect such information using

scripts/comprehensive_test.sh  comprehensive_test.sh.out

(although you also have to anticipate the script will hang until you
answer the question that will be at the end of that *.out file).

That complete output gives all sorts of useful background information
such as what options you used for the script such as the cmake
generator you specified, etc.  For example, I suspect the issues you
are seeing might be due to specifying the wrong generator, but I won't
know for sure until I can see that complete results.  Also, I suggest
you compress that output for those four cases before you attach it
because sometimes mailing software messes with plain text attachments
in my experience.

And please send those 4 compressed attachments to the mailing list and
not to me privately since we often need group expertise to give you
the best advice about how to deal with the problems running
scripts/comprehensive_test.sh thta you have encountered.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-29 Thread Alan W. Irwin
On 2015-03-26 18:50-0700 Alan W. Irwin wrote:

 With commit id 5f6e28f I finally have been able to complete
 scripts/comprehensive_test.sh on Linux without issues which removes
 the last known regression compared to 5.10.0 for this release which is
 a much-desired result.

 My next steps are [1] to do some straightforward release preliminaries
 (such as setting version strings and updating the website) followed by
 [2] epa_build and comprehensive test of plplot on Linux (which will do a
 similar test to what I just completed but for the latest versions of
 PLplot dependencies) and [3] plplot_lite on MinGW/MSYS/Wine.  Note that
 Wine test will take a couple of days (since Wine is so slow).

I am happy to report that I have finished [2] above with no issues.
The entire test took 3.7 hours to complete on my computer.  For
details about this successful comprehensive test using epa_build and
the previous success at running scripts/comprehensive_tests.sh
directly, see the reports I just posted at 
http://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Testing%20Reports.

Note, I am not interested in posting vague it doesn't work
reports there, but if you did get the script to complete using one of
the scripts options, say, to remove a component of PLplot that is not
working for you, then I would definitely be interested in posting that
definite result. So to take a concrete example, Greg is currently not
having much luck with comprehensive testing on some variant of MSYS2,
but that result is too vague at the present time to report in our
wiki.  But once he gets the *.out results to me that I have requested, I
might be able to advise him what components of PLplot he should avoid
(or maybe even come up with a build system fix) to allow him to finish
scripts/comprehensive_test.sh on MSYS2, and that definite report
detailing exactly which components had to be dropped would be well
worth posting at
http://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Testing%20Reports.


 While I am doing those steps I strongly encourage the rest of you to
 do comprehensive testing of PLplot master tip on all platforms that
 are accessible to you following the instructions at
 http://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Comprehensive%20testing
 and
 http://sourceforge.net/p/plplot/wiki/Testing_PLplot/#Testing%20Reports.

I very much appreciate the effort some of you have started putting
into comprehensive testing, and now that I have shown the epa_build
method of doing this works for master tip (as it also worked for the
last release) on Linux, then some who are having trouble with system
dependencies when running scripts/comprehensive_tests.sh directly
might want to try the epa_build method instead following the
instructions in cmake/epa_build/README.

My next planned steps in the release process are to essentially
prepare a release candidate ([1] above plus all other steps mentioned
in README.Release_Manager_Cookbook that do not involve uploads to the
SourceForge file release area) plus respond to any bugs that your own
comprehensive testing might turn up. Once I am entirely satisfied with
that result, I will finally try [3] above to give me the best chance
of not having to repeat that (very long) test.  Assuming that test
finds no regressions I plan to complete the release with the actual
upload of the tarball and signature file to SourceForge.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-29 Thread Jim Dishaw




 On Mar 29, 2015, at 9:17 AM, Andrew Ross andrewr...@users.sourceforge.net 
 wrote:
 

  Also -np to prevent pausing between
 pages doesn't work. This is not a major issue, but is a slight pain when
 running the automatic tests.
 
 Andrew

I believe this bug might be related to the extra plP_eop() call. This results 
in the need for extra keypresses. 
 --
 Dive into the World of Parallel Programming The Go Parallel Website, sponsored
 by Intel and developed in partnership with Slashdot Media, is your hub for all
 things parallel software development, from weekly thought leadership blogs to
 news, videos, case studies, tutorials and more. Take a look and join the 
 conversation now. http://goparallel.sourceforge.net/
 ___
 Plplot-devel mailing list
 Plplot-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/plplot-devel

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-29 Thread Andrew Ross
On Sat, Mar 28, 2015 at 05:41:12PM -0700, Alan Irwin wrote:
 On 2015-03-28 21:40- Andrew Ross wrote:
 
 I use 2.2.1 as well but with additional patches applied.
 
 See cmake/epa_build/libharu/CMakeLists.txt for how to locate those
 patches.
 
 Most of those are to install a CMake-based build system which you
 don't need (except for epa_build), but one of those, i.e.,
 cmake/epa_build/libharu/large_font.patch is a bug fix for large fonts
 (as occurs for example 24), see
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726069.  The
 Debian maintainer responded there and said he would apply the patch to
 the Debian package, but the sid, testing, and stable version of that
 package are all the same so it appears he did not do so.  If it is
 possible for him to make that change this late in the Debian release
 cycle, could you please nag him to do so?
 
 You may also want to nag the Ubuntu developers about that patch.

Good point. I do vaguely remember this now.

  One other thing I noticed is that itcl / itk are disabled because the
  header files are not found. I do have them installed. Looks like the
  headers are now in /usr/include/itcl3/ . CMake is looking in
  ${TCL_INCLUDE_PATH}/itcl3, but TCL_INCLUDE_PATH is /usr/include/tcl8.6 in
  my case so this doesn't work. It used to work, so I expect this is
  something related to the way itcl / itk are packaged on Ubuntu. Alan, do
  you run into this on Debian?
 
 Both Debian stable and epa_build are fine in this regard, and I suspect
 Orion would have said something if this was an issue on Fedora.
 
 The current find_path assumption in cmake/modules/tcl-related.cmake is
 the itcl and itk headers are in subdirectories of the versioned tcl
 headers which is what occurs for both Debian stable and epa_build and
 makes some sense since itcl and itk versions depend on Tcl (and Tk)
 version.  But I guess Ubuntu have decided to violate that assumption.
 
 I don't think that if Itcl and Itk are missing it is a
 release-critical issue since they play a fairly small role for PLplot.
 Therefore, I think we should deal with this issue post-release by
 coming up with some PATHS or HINTS options for the find_path commands
 that will make Ubuntu work automatically without interfering with what
 works for Debian stable (and other distros?) and epa_build.  However,
 for now, if you want to test Itcl and Itk on Ubuntu, you could do that
 by setting ITCL_INCLUDE_PATH and ITK_INCLUDE_PATH appropriately.

I'm surprised Debian and Ubuntu have diverged here. I'll check what is in
unstable. It may be the change is in the new Debian release too. Anyway, I
agree about the fix. Just flagging it up while testing.

Two other comments for Phil on wxwidgets. Example 17 is a mess (I'm sure
this is already on the list of bugs). Also -np to prevent pausing between
pages doesn't work. This is not a major issue, but is a slight pain when
running the automatic tests.

Andrew

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-29 Thread Alan W. Irwin
On 2015-03-28 22:20-0700 Alan W. Irwin wrote:

 Also, when you report back again, will you please always specify the
 scripts/comprehensive_test.sh options you used in every different
 platform case?  The easiest way to do that is to always include
 everything output from the script rather than bits and pieces like
 above.  So ideally you would capture the whole output from the script
 in a file, compress that file, and attach it to your post here (as
 well as tarballs of comprehensive_test_disposeable/shared/output_tree,
 comprehensive_test_disposeable/nondynamic/output_tree, and
 comprehensive_test_disposeable/static/output_tree) for each platform
 you test.

Hi Greg:

One other point I should have mentioned is you should use a different
--prefix option for each separate run of scripts/comprehensive_test.sh
to keep your comprehensive testing results for various platforms (if
done on the same computer) completely separate from each other.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-28 Thread Andrew Ross
On Sat, Mar 28, 2015 at 09:07:46PM +, Andrew Ross wrote:
 
 Alan,
 
 For me with Ubuntu 14.10 (Utopic Unicorn) scripts/comprehensive_test.sh
 fails. Compile all goes fine, but the test of the C examples with the pdf
 driver fails at example 24 with
 
 ERROR: error_no=1050, detail_no=0
 ERROR in haru library
 
 I'm assuming this is a libharu issue since no-one else has run into it.
 A quick google search suggests this error is An invalid font-size was
 set. For reference this is version 2.2.1-1.1. Alan, what version are you
 running?
 
 I'll disable the pdf driver and try again.

This gets me through the shared library ctest test in the build tree. The
rest is still running.

One other thing I noticed is that itcl / itk are disabled because the
header files are not found. I do have them installed. Looks like the
headers are now in /usr/include/itcl3/ . CMake is looking in
${TCL_INCLUDE_PATH}/itcl3, but TCL_INCLUDE_PATH is /usr/include/tcl8.6 in
my case so this doesn't work. It used to work, so I expect this is
something related to the way itcl / itk are packaged on Ubuntu. Alan, do
you run into this on Debian?

Andrew

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: call for comprehensive testing

2015-03-28 Thread Alan W. Irwin
On 2015-03-28 21:40- Andrew Ross wrote:

 On Sat, Mar 28, 2015 at 09:07:46PM +, Andrew Ross wrote:

 Alan,

 For me with Ubuntu 14.10 (Utopic Unicorn) scripts/comprehensive_test.sh
 fails. Compile all goes fine, but the test of the C examples with the pdf
 driver fails at example 24 with

 ERROR: error_no=1050, detail_no=0
 ERROR in haru library

 I'm assuming this is a libharu issue since no-one else has run into it.
 A quick google search suggests this error is An invalid font-size was
 set. For reference this is version 2.2.1-1.1. Alan, what version are you
 running?

I use 2.2.1 as well but with additional patches applied.

See cmake/epa_build/libharu/CMakeLists.txt for how to locate those
patches.

Most of those are to install a CMake-based build system which you
don't need (except for epa_build), but one of those, i.e.,
cmake/epa_build/libharu/large_font.patch is a bug fix for large fonts
(as occurs for example 24), see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726069.  The
Debian maintainer responded there and said he would apply the patch to
the Debian package, but the sid, testing, and stable version of that
package are all the same so it appears he did not do so.  If it is
possible for him to make that change this late in the Debian release
cycle, could you please nag him to do so?

You may also want to nag the Ubuntu developers about that patch.


 I'll disable the pdf driver and try again.

 This gets me through the shared library ctest test in the build tree. The
 rest is still running.

 One other thing I noticed is that itcl / itk are disabled because the
 header files are not found. I do have them installed. Looks like the
 headers are now in /usr/include/itcl3/ . CMake is looking in
 ${TCL_INCLUDE_PATH}/itcl3, but TCL_INCLUDE_PATH is /usr/include/tcl8.6 in
 my case so this doesn't work. It used to work, so I expect this is
 something related to the way itcl / itk are packaged on Ubuntu. Alan, do
 you run into this on Debian?

Both Debian stable and epa_build are fine in this regard, and I suspect
Orion would have said something if this was an issue on Fedora.

The current find_path assumption in cmake/modules/tcl-related.cmake is
the itcl and itk headers are in subdirectories of the versioned tcl
headers which is what occurs for both Debian stable and epa_build and
makes some sense since itcl and itk versions depend on Tcl (and Tk)
version.  But I guess Ubuntu have decided to violate that assumption.

I don't think that if Itcl and Itk are missing it is a
release-critical issue since they play a fairly small role for PLplot.
Therefore, I think we should deal with this issue post-release by
coming up with some PATHS or HINTS options for the find_path commands
that will make Ubuntu work automatically without interfering with what
works for Debian stable (and other distros?) and epa_build.  However,
for now, if you want to test Itcl and Itk on Ubuntu, you could do that
by setting ITCL_INCLUDE_PATH and ITK_INCLUDE_PATH appropriately.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: need help with OLD_WXWIDGETS=ON option (fwd)

2015-03-25 Thread Alan W. Irwin
On 2015-03-25 15:39- Phil Rosenberg wrote:

 Hi Alan
 I have pushed that fix. There was also a problem on resize that caused
 a hang due to re-entrancy in the event loop which I have fixed too.

 There is also a problem with rendering the wxPLplotDemo whereby there
 are sections of the window that are not being rendered. I'm not sure
 if this is a long standing issue that nobody has noticed before or if
 it is something that has changed in wxWidgets 3.0 or if it is a new
 thing. However all the examples render correctly.

Hi Phil:

Your fix works perfectly here.

I have had a look at a small sample of the examples with
-DOLD_WXWIDGETS=ON and -dev wxwidgets, and they appear to render as
before.  Note, I don't say they render correctly because there were
some long-standing rendering issues with old wxwidgets such as affine
transform issues with example 8 backend=0, and I am just glad we don't
have to worry about fixing those anymore.  In other words,
-DOLD_WXWIDGETS=ON appears to deliver exactly what we had before
for 5.10.0, warts and all, which is our goal.

I have also looked at wxPLplotDemo results with -DOLD_WXWIDGETS=ON,
and that renders perfectly with the Debian stable version of the
wxwidgets libraries (2.8.12.1).  So that supports your hypothesis
above that the rendering issue you found for this case is due to an
inconsistency with wxWidgets 3.0.  So if you confirm this issue also
existed for the 5.10.0 version of the wxwidgets device driver, then
there is nothing more you should do here since the only fixing we
should do for the -DOLD_WXWIDGETS=ON case is if there is a regression
(change) from what occurred for the wxwidgets device driver for
PLplot-5.10.0.

So anticipating you will not find such a regression, then thanks very
much for fixing the -DOLD_WXWIDGETS=ON case which was a major
showstopper for this release, and it looks like the rest of this
release is largely up to me (unless I find more regressions with any
aspect of PLplot that I need help fixing).

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: another plend segfault and/or double free

2015-03-25 Thread Alan W. Irwin
On 2015-03-21 11:57-0700 Alan W. Irwin wrote:

 Hi Andrew:

 I have now (commit fa0c879) solved this release-critical regression.

 The crux of the problem is redundant linking of qt_example to both
 plplot (which contained all of the code in plplotqt for this
 ENABLE_DYNDRIVERS=NO case) and plplotqt. examples/c++/qt_example had no severe
 memory management issues if I manipulated visibility so that I used
 either the plplotqt symbols from just plplot or just plplotqt.
 However, if both sets of symbols are made visible (the change that
 formally caused this regression), it caused severe memory management
 issues when the libraries were closed at plend.  The obvious fix for
 this issue has been applied which is to drop the redundant linking of
 qt_example to libplplotqt for the ENABLE_DYNDRIVERS=NO case.

 There are obvious broader implications here now that we have a clear
 case of plend memory management issues caused by redundant linking to
 two sets of the identical code located in two different libraries. I
 frankly never expected this to be an issue since I thought the linker
 would choose one set or the other with no other consequences. But from
 this experience this is obviously not the case (probably due to all
 the behind-the-scenes shenanigans that go on when libraries are
 closed). Anyhow, since I have not been aware of this issue for all the
 years I have been trying to maintain correct PLplot linking, I am
 virtually positive there are similar instances of this same problem
 for other device drivers.  Note, for example, that for the
 ENABLE_DYNDRIVERS=NO case there is necessarily always two copies of
 the device driver binding code (e.g., like the libplplotqt binding
 code) to break circular linking issues.

 So my current plan is to look very carefully for such issues and fix
 them (likely most of those fixes will occur post-release if there is
 not a clear regression from 5.10.0 results) in the hope this
 refinement of our linking model will ultimately resolve a substantial
 number of the plend memory management issues we have been
 encountering.

It turns out this is not an issue at all for wxwidgets because that
driver code does not depend on bindings/wxwidgets code.

So the only maintained drivers where for ENABLE_DYNDRIVERS=NO
duplicate code occurs in two separate libraries is for -dev tk and
-dev tkwin.  But the plplot library currently does not have visible
symbols corresponding to the libplplottcltk symbols so from the experience with 
plplot and plplotqt there should
be no memory management issues for Windows and Unix forms of gcc if
the gcc compile option -fvisibility=hidden is used and also no such
issues for the MSVC case.

Therefore, for Linux I dropped the gcc -fvisibility=hidden option in
anticipation that would generate severe memory management issues for
-dev tk, but it did not.  So experience with the C++ qt device driver
does not predict exactly what will happen for the C tk device driver.
Nevertheless, we do have a large number of outstanding plend memory
management issues for anything having to do with Tcl and Tk, and at
least in the C++ case, duplicate symbols defined in two separate
libraries does lead to plend memory management trouble. Therefore, as
a post-release project I plan to make visible all the libplplottcltk
symbols that are currently not visible in plplot, and then drop
libplplottcltk from all link commands to see whether that fixes some
of the current plend issues with Tcl/Tk.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-25 Thread Alan W. Irwin
On 2015-03-21 12:29-0700 Alan W. Irwin wrote:

 Just to summarize where we stand there are several open-ended issues
 blocking the release.

 1. I am in the middle of a hunt for plend memory management issues caused by 
 redundant
 library linking (see previous post to Andrew).

I have finished that hunt, but will only fix the two cases found
(for -dev tk and -dev tkwin) post-relase (see just prior post for more
details).


 2. Because of issues like the qt_example segfault that I have just
 fixed, I have as yet been unable to complete a comprehensive test of
 PLplot on Linux.  Until I can get such a clean test the possibility
 exists there are other such segfault issues lurking in our master tip
 code base due to some regression since the 5.10.0 release.


 3. -DOLD_WXWIDGETS=ON does not yet work.
Thanks to Phil's efforts it now works for me so I think we
are likely done here unless Phil proves the one OLD_WXWIDGETS
issue he found on his system (which I did not find on mine) is
a regression from PLplot-5.10.0

In sum, 1 and 3 are no longer relevant, I am still working on 2, and deep 
freeze continues.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: another plend segfault and/or double free

2015-03-21 Thread Andrew Ross

Alan,

Thanks for the update. I'm glad you managed to track it down. I'd held of
delving into this as you seemed to have it under control. I'm also
slightly surprised at the linker not being more intelligent here.
Certainly something we need to be wary of.

Andrew

On Sat, Mar 21, 2015 at 11:57:20AM -0700, Alan Irwin wrote:
 Hi Andrew:
 
 I have now (commit fa0c879) solved this release-critical regression.
 
 The crux of the problem is redundant linking of qt_example to both
 plplot (which contained all of the code in plplotqt for this
 ENABLE_DYNDRIVERS=NO case) and plplotqt. examples/c++/qt_example had no severe
 memory management issues if I manipulated visibility so that I used
 either the plplotqt symbols from just plplot or just plplotqt.
 However, if both sets of symbols are made visible (the change that
 formally caused this regression), it caused severe memory management
 issues when the libraries were closed at plend.  The obvious fix for
 this issue has been applied which is to drop the redundant linking of
 qt_example to libplplotqt for the ENABLE_DYNDRIVERS=NO case.
 
 There are obvious broader implications here now that we have a clear
 case of plend memory management issues caused by redundant linking to
 two sets of the identical code located in two different libraries. I
 frankly never expected this to be an issue since I thought the linker
 would choose one set or the other with no other consequences. But from
 this experience this is obviously not the case (probably due to all
 the behind-the-scenes shenanigans that go on when libraries are
 closed). Anyhow, since I have not been aware of this issue for all the
 years I have been trying to maintain correct PLplot linking, I am
 virtually positive there are similar instances of this same problem
 for other device drivers.  Note, for example, that for the
 ENABLE_DYNDRIVERS=NO case there is necessarily always two copies of
 the device driver binding code (e.g., like the libplplotqt binding
 code) to break circular linking issues.
 
 So my current plan is to look very carefully for such issues and fix
 them (likely most of those fixes will occur post-release if there is
 not a clear regression from 5.10.0 results) in the hope this
 refinement of our linking model will ultimately resolve a substantial
 number of the plend memory management issues we have been
 encountering.
 
 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
 __
 
 --
 Dive into the World of Parallel Programming The Go Parallel Website, sponsored
 by Intel and developed in partnership with Slashdot Media, is your hub for all
 things parallel software development, from weekly thought leadership blogs to
 news, videos, case studies, tutorials and more. Take a look and join the 
 conversation now. http://goparallel.sourceforge.net/
 ___
 Plplot-devel mailing list
 Plplot-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/plplot-devel

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: another plend segfault and/or double free

2015-03-21 Thread Alan W. Irwin
Hi Andrew:

I have now (commit fa0c879) solved this release-critical regression.

The crux of the problem is redundant linking of qt_example to both
plplot (which contained all of the code in plplotqt for this
ENABLE_DYNDRIVERS=NO case) and plplotqt. examples/c++/qt_example had no severe
memory management issues if I manipulated visibility so that I used
either the plplotqt symbols from just plplot or just plplotqt.
However, if both sets of symbols are made visible (the change that
formally caused this regression), it caused severe memory management
issues when the libraries were closed at plend.  The obvious fix for
this issue has been applied which is to drop the redundant linking of
qt_example to libplplotqt for the ENABLE_DYNDRIVERS=NO case.

There are obvious broader implications here now that we have a clear
case of plend memory management issues caused by redundant linking to
two sets of the identical code located in two different libraries. I
frankly never expected this to be an issue since I thought the linker
would choose one set or the other with no other consequences. But from
this experience this is obviously not the case (probably due to all
the behind-the-scenes shenanigans that go on when libraries are
closed). Anyhow, since I have not been aware of this issue for all the
years I have been trying to maintain correct PLplot linking, I am
virtually positive there are similar instances of this same problem
for other device drivers.  Note, for example, that for the
ENABLE_DYNDRIVERS=NO case there is necessarily always two copies of
the device driver binding code (e.g., like the libplplotqt binding
code) to break circular linking issues.

So my current plan is to look very carefully for such issues and fix
them (likely most of those fixes will occur post-release if there is
not a clear regression from 5.10.0 results) in the hope this
refinement of our linking model will ultimately resolve a substantial
number of the plend memory management issues we have been
encountering.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: another plend segfault and/or double free

2015-03-19 Thread Alan W. Irwin
On 2015-03-19 14:38-0700 Alan W. Irwin wrote:

 Hi Andrew (again):

 I just discovered this issue was a regression compared to 5.10.0.  So
 I will git bisect it to see which commit first created this issue, and
 get back to you at that point if I cannot figure out the problem
 introduced by that commit.

According to git bisect the issue first appeared for 6f5dc7b546f05c79

That's one of my commits which is a small but rather subtle symbol visibility 
change given by the
following diff:

software@raven git diff 6f5dc7b546f05c79^ 6f5dc7b546f05c79
diff --git a/include/pldll.h.in b/include/pldll.h.in
index bdf5f7e..f818b64 100644
--- a/include/pldll.h.in
+++ b/include/pldll.h.in
@@ -131,7 +131,10 @@
#define PLDLLIMPEXP_PLPLOT_MODULE_DATA( type )PLDLLIMPORT type
  #endif

-#if defined ( plplotqt_EXPORTS )
+// Note for the case when ENABLE_DYNDRIVERS is not defined, the
+// libplplot build specifically includes bindings/qt-gui/plqt.cpp (see
+// cmake/modules/qt.cmake).
+#if defined ( plplotqt_EXPORTS ) || ( !defined ( ENABLE_DYNDRIVERS )  
defined ( plplot_EXPORTS ) )
#define PLDLLIMPEXP_QTPLDLLEXPORT
#define PLDLLIMPEXP_QT_DATA( type )PLDLLEXPORT type
  #else

So the difference means that for the case where ENABLE_DYNDRIVERS is
not #defined, then for _both_ the build of libplplotqt and the build
of libplplot, PLDLLIMPEXP_QT and PLDLLIMPEXP_QT_DATA are both defined
(which makes complete sense to me since some the qt device driver code
gets into libplplot for the nondynamic devices case). So I don't see
anything wrong with the above change at all, but if anyone spots a
problem, please let me know.  Meanwhile, I will keep investigating by
seeing whether temporarily reverting the above change for master tip
solves the segfault issue (confirming the above change is
the only source of the problem) and by investigations with nm.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: another plend segfault and/or double free

2015-03-19 Thread Alan W. Irwin
Hi Andrew (again):

I just discovered this issue was a regression compared to 5.10.0.  So
I will git bisect it to see which commit first created this issue, and
get back to you at that point if I cannot figure out the problem
introduced by that commit.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: epa_build: libharu and general release topics

2015-03-18 Thread Arjen Markus
Hi Alan,



 -Original Message-
 From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
 Sent: Saturday, March 14, 2015 1:19 AM
 To: Andrew Ross
 Cc: PLplot development list
 Subject: [Plplot-devel] Release status: epa_build: libharu and general 
 release topics


 @ Arjen: If there is anything else release-rated we have discussed that I have
 forgotten or you notice any new release-related topic, please let me know.



I had a curious error when I tried to build Plplot and the C and C++ examples 
with VS 2010. Something to do with the macro WIN32. But when I tried to 
identify the exact configuration (32 bits, 64 bits, something described as 
cross tools), the problem had disappeared.

However, using only C and C++ did bring up an issue I had not noticed before: 
VS 2010 complains about MIN() and MAX() in examples x08.cc and x33.cc - loss of 
precision going from PLFLT to PLINT. I have stared at the code but as far as I 
can tell there should be no mixup of precisions. It is probably nothing 
important, but I thought I'd mention it anyway.

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.
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: fix for plbuf resizing issue

2015-03-15 Thread Alan W. Irwin
On 2015-03-15 20:03-0400 Jim Dishaw wrote:

 Did we ever come to a resolution on this?

 On Mar 13, 2015, at 3:10 PM, Jim Dishaw j...@dishaw.org wrote:
 The plP_eop() call, for some reason, results in extra keypresses
needed to advance to the next page. I thought I knew the reason, but
after examining the code, my initial hypothesis doesn't look correct.
I will step through the code to see what is causing the issue.

Hi Jim:

I have some points to offer.

I confirm the issue (which shows up whenever I attempt to resize -dev
xwin).

I have no idea whether Phil is investigating fixing this or not.

But regardless of whether you or Phil fixes the issue, the fix should
be done on a topic branch now and pushed to master post-release since
the fix very likely involves a change to plbuf, which I want to avoid
at this late date in the release cycle.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: epa_build: pango/cairo build issues

2015-03-14 Thread Andrew Ross
On Fri, Mar 13, 2015 at 12:23:56PM -0700, Alan Irwin wrote:
 On 2015-03-13 10:26-0700 Alan W. Irwin wrote:
 On 2015-03-13 10:19- Andrew Ross wrote:
 1) The cairo build fails (seems to be due to a bug in cairo build scripts
 exposed in gcc-4.9.0 - see http://sourceforge.net/p/mingw-w64/bugs/396/)
 
 Hi Andrew:
 
 That thread implies the problem is caused by the build scripts for
 GTK+ which apparently use the -flto link time option that is described
 at https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html.
 However, there is no mention of flto in the epa_build tree so unless
 -flto is on by default with gcc-4.9.0, the source of the issue with
 epa_build of GTK+ (or the pango/cairo subset of that) must be
 something else.  Also note that gcc-4.7.2 knows nothing about the
 -flto option so if the solution is turning off that option for gcc-4.9.x
 that can only be done for that version of gcc.
 
 In sum, dealing with this epa_build issue for pango/cairo is likely
 not going to be a simple fix so we should look at this again
 post-release.

I agree. Since the epa_build is not core to plplot I don't see this as a
release issue. For reference Debian unstable has gcc-4.9.2. It might be 
interesting to look at the Debian build for the packages / any Debian
specific patches for clues to this issue.

Andrew

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: epa_build: libharu and general release topics

2015-03-14 Thread Andrew Ross
On Fri, Mar 13, 2015 at 05:19:02PM -0700, Alan Irwin wrote:
 On 2015-03-13 10:26-0700 Alan W. Irwin wrote:
 On 2015-03-13 10:19- Andrew Ross wrote:
 2) The libharu build succeeds, but the hpdf_pdfa.h include file is not
 installed so the plplot build of the pdf driver fails.
 
 Hi Andrew:
 
 As of commit fac174e I have changed the CMake-based libharu build
 system to install both hpdf_namedict.h and hpdf_pdfa.h because both
 those headers are installed by the autotools-based libharu build
 system. As far as I can tell, my own epa_build should have complained
 about missing hpdf_pdfa.h, but for some unknown reason it didn't.  But
 in any case, thanks for reporting this issue which has now been fixed.
 
 I also took this opportunity to search the -dev pdf results for
 rendering issues, and I have documented everything I spotted at
 https://sourceforge.net/p/plplot/bugs/155/.  I think all of these I
 have seen before so I conclude they are not due to any recent changes.
 In agreement with that conclusion, note that most devices do not share
 these rendering issues so they cannot be due to recent plbuf changes
 (which typically clobber every device result).  So this comprehensive
 check of the rendering for all our examples has been most reassuring
 from the release quality perspective.

Thanks Alan. I suspect you also had the Debian packages installed? The
header would be picked up from there, even if you were linking against
the epa_build version. Providing the versions weren't too out of sync
it wouldn't be problematic and there would be no way of telling. This
is one advantage of the pbuilder approach. Each time you start with
a pristine base install and only install additional packages which
are explicitly requested.

 @ Andrew: I think this concludes all release topics that we have discussed
 previously, but if there is anything else we have discussed that I
 have forgotten or you notice any new release-related topic, please let
 me know.

I agree. There is the outstanding octave segfault which occurs with one
of the p?? examples when run explicitly, but not with the test scripts.
This is odd, but probably not release critical. I may still get chance
to track this down, but debugging such issues with octave is tricky
since you can't easily use gdb. I can't see what the difference is
between the two cases, but this at least provides a starting point.

Otherwise it is the documented issues with the various drivers, but 
these are longstanding in most cases. A good goal for the next release
cycle would be to try and squash as many of these as we can to get
more uniform behaviour between all (or at least our main) drivers.
 
Andrew

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: fix for plbuf resizing issue

2015-03-13 Thread Jim Dishaw

 On Mar 13, 2015, at 2:34 PM, Phil Rosenberg p.d.rosenb...@gmail.com wrote:
 
 Hi Jim Alan
 Firstly I'm not in front of a pc right now so I'm doing function names from 
 memory. Apologies if they are wrong.
 
 Are you talking about the call to plP_eop() that is in the plreplot() 
 function?
 
 If so, I put that there. The reason is that when creating the first page from 
 a buffer,   we need to do the bop actions, however due to the plinit call the 
 status is already set to bop, so the call to plP_bop does nothing. The state 
 #define values are not exposed to plbuf.c so the appropriate action appeared 
 to be to end the existing page.
 It might be that changes to device initialization mean this is no longer 
 necessary, but I don't know without testing. I'm not sure why it would cause 
 the behaviour you describe though. Which device were they in?
 

The plP_eop() call, for some reason, results in extra keypresses needed to 
advance to the next page. I thought I knew the reason, but after examining the 
code, my initial hypothesis doesn't look correct. I will step through the code 
to see what is causing the issue. 

 Phil
 From: Alan W. Irwin
 Sent: ‎13/‎03/‎2015 17:59
 To: Phil Rosenberg; Jim Dishaw
 Cc: PLplot development list
 Subject: Release status: fix for plbuf resizing issue
 
 On 2015-03-13 11:10-0400 Jim Dishaw wrote:
 
  Alan,
 
 
  I noticed a bug that occurs when resizing a plot.  Every time a plot
 is resized, an extra key press is required to advance the page.  The
 problem appears to be a pop_eop() that was added in plRemakePlot()
 during one of your fixes (afd73a98).  If I comment that line out, the
 bug goes way.  There should already be an EOP (or at least in most
 cases) at the end of the buffer because Does calling plP_eop()
 internally cause problems if the application was not expecting it? 
 I've run through all the examples without the plP_eop() call and
 cannot detect a problem.  Example 17 had no issues and that does not
 have an EOP.
 
 
  If the plP_eop() is required, I propose two solutions:
 
  1) Check for an EOP before putting another one.
  2) Do not replay the plot buffer unless there is an EOP (which would 
  prevent redraws until an EOP and break example 17).
 
 
 Hi Jim:
 
 I verify that bug here (using examples/c/x01c -dev xwin).
 
 However, you have to dig deeper to find out who to blame.  In other
 words, It wasn't me.  :-)
 
 Here is the git magic you need.
 
 software@raven git blame src/plbuf.c |grep plP_eop
 afd37a98 (Alan W. Irwin  2015-03-11 02:33:40 -0700 1222) plP_eop();
 
 So far so good, but if you use git log to look up that commit, it was just a 
 whitespace
 (style) change by me.  So taking the search one step further
 (afd37a98^ is the parent commit of afd37a98)
 
 software@raven git blame afd37a98^ src/plbuf.c |grep plP_eop
 1e402417 (Phil Rosenberg 2015-02-27 17:12:03 + 1218) plP_eop();
 
 and if you look up 1e402417 using git log the first line of the
 commit message is
 
 Fixed bug in rdbuf_di.
 
 So that is a serious (non-style) commit, and Phil is the one to
 ask about your possible solutions for this bug.
 
 So I have put this on the list and also added Phil to the recipients.
 
 @Phil: I have no objections to your pushing a simple, well-tested fix for
 this bug, but if the fix is complicated or you don't have time to
 thoroughly test it, you should probably wait until post-release.
 
 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
 __
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: fix for plbuf resizing issue

2015-03-13 Thread Phil Rosenberg
Hi Jim Alan
Firstly I'm not in front of a pc right now so I'm doing function names from 
memory. Apologies if they are wrong.

Are you talking about the call to plP_eop() that is in the plreplot() function?

If so, I put that there. The reason is that when creating the first page from a 
buffer,   we need to do the bop actions, however due to the plinit call the 
status is already set to bop, so the call to plP_bop does nothing. The state 
#define values are not exposed to plbuf.c so the appropriate action appeared to 
be to end the existing page.
It might be that changes to device initialization mean this is no longer 
necessary, but I don't know without testing. I'm not sure why it would cause 
the behaviour you describe though. Which device were they in?

Phil

-Original Message-
From: Alan W. Irwin ir...@beluga.phys.uvic.ca
Sent: ‎13/‎03/‎2015 17:59
To: Phil Rosenberg p.d.rosenb...@gmail.com; Jim Dishaw j...@dishaw.org
Cc: PLplot development list Plplot-devel@lists.sourceforge.net
Subject: Release status: fix for plbuf resizing issue

On 2015-03-13 11:10-0400 Jim Dishaw wrote:

 Alan,


 I noticed a bug that occurs when resizing a plot.  Every time a plot
is resized, an extra key press is required to advance the page.  The
problem appears to be a pop_eop() that was added in plRemakePlot()
during one of your fixes (afd73a98).  If I comment that line out, the
bug goes way.  There should already be an EOP (or at least in most
cases) at the end of the buffer because Does calling plP_eop()
internally cause problems if the application was not expecting it? 
I've run through all the examples without the plP_eop() call and
cannot detect a problem.  Example 17 had no issues and that does not
have an EOP.


 If the plP_eop() is required, I propose two solutions:

 1) Check for an EOP before putting another one.
 2) Do not replay the plot buffer unless there is an EOP (which would prevent 
 redraws until an EOP and break example 17).


Hi Jim:

I verify that bug here (using examples/c/x01c -dev xwin).

However, you have to dig deeper to find out who to blame.  In other
words, It wasn't me.  :-)

Here is the git magic you need.

software@raven git blame src/plbuf.c |grep plP_eop
afd37a98 (Alan W. Irwin  2015-03-11 02:33:40 -0700 1222) plP_eop();

So far so good, but if you use git log to look up that commit, it was just a 
whitespace
(style) change by me.  So taking the search one step further
(afd37a98^ is the parent commit of afd37a98)

software@raven git blame afd37a98^ src/plbuf.c |grep plP_eop
1e402417 (Phil Rosenberg 2015-02-27 17:12:03 + 1218) plP_eop();

and if you look up 1e402417 using git log the first line of the
commit message is

Fixed bug in rdbuf_di.

So that is a serious (non-style) commit, and Phil is the one to
ask about your possible solutions for this bug.

So I have put this on the list and also added Phil to the recipients.

@Phil: I have no objections to your pushing a simple, well-tested fix for
this bug, but if the fix is complicated or you don't have time to
thoroughly test it, you should probably wait until post-release.

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
__
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: fix for plbuf resizing issue

2015-03-13 Thread Alan W. Irwin
On 2015-03-13 10:59-0700 Alan W. Irwin wrote:

 On 2015-03-13 11:10-0400 Jim Dishaw wrote:

 Alan,


 I noticed a bug that occurs when resizing a plot.  Every time a plot
 is resized, an extra key press is required to advance the page.  The
 problem appears to be a pop_eop() that was added in plRemakePlot()
 during one of your fixes (afd73a98).  If I comment that line out, the
 bug goes way.  There should already be an EOP (or at least in most
 cases) at the end of the buffer because Does calling plP_eop()
 internally cause problems if the application was not expecting it?
 I've run through all the examples without the plP_eop() call and
 cannot detect a problem.  Example 17 had no issues and that does not
 have an EOP.


 If the plP_eop() is required, I propose two solutions:

 1) Check for an EOP before putting another one.
 2) Do not replay the plot buffer unless there is an EOP (which would prevent 
 redraws until an EOP and break example 17).


 Hi Jim:

 I verify that bug here (using examples/c/x01c -dev xwin).

 However, you have to dig deeper to find out who to blame.  In other
 words, It wasn't me.  :-)

 Here is the git magic you need.

 software@raven git blame src/plbuf.c |grep plP_eop
 afd37a98 (Alan W. Irwin  2015-03-11 02:33:40 -0700 1222) plP_eop();

 So far so good, but if you use git log to look up that commit, it was just a 
 whitespace
 (style) change by me.  So taking the search one step further
 (afd37a98^ is the parent commit of afd37a98)

 software@raven git blame afd37a98^ src/plbuf.c |grep plP_eop
 1e402417 (Phil Rosenberg 2015-02-27 17:12:03 + 1218) plP_eop();

 and if you look up 1e402417 using git log the first line of the
 commit message is

 Fixed bug in rdbuf_di.

 So that is a serious (non-style) commit, and Phil is the one to
 ask about your possible solutions for this bug.

 So I have put this on the list and also added Phil to the recipients.

 @Phil: I have no objections to your pushing a simple, well-tested fix for
 this bug, but if the fix is complicated or you don't have time to
 thoroughly test it, you should probably wait until post-release.

Oops.  It just sunk in that this is a plbuf change where we have at
least one example (example 2.02) where there were unintended
wide-spread consequences of a plbuf change for all devices.  And also
some plbuf change and a subsequent fix for that was the likely cause
of the on-again/off-again -dev tk zoom issue. So my advice is to hold
off on this fix until post-release so we have a full release cycle to
test it.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: plmeta/plrender

2015-03-13 Thread Jim Dishaw

On Mar 12, 2015, at 3:38 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:

 Hi Jim:
 
 Here are the results of a simple test I tried with -DPLD_plmeta=ON
 
 # Build what is relevant
 make plrender
 make plmeta
 make x01c
 make ps
 
 # Test
 examples/c/x01c -dev psc -o test1.psc
 examples/c/x01c -dev plmeta -o test.plmeta
 utils/plrender test.plmeta -dev psc -o test2.psc
 
 There were no build issues and no run time issues.  However, test1.psc
 was quite different (text size, etc.,) from test2.psc, and I was under
 the impression that the effect of all your recent plmeta/plrender
 changes was those two files should be identical (modulo the
 possibility of some small rounding errors).
 

I left plrender to behave like it did before my changes in order not to cause 
any issues if it was being used.  I did not feel the code I had written was 
ready for the release.

 This issue is not release critical (since -DPLD_plmeta=OFF by
 default), and I definitely don't plan to push any further
 plmeta/plrender changes prior to the release (deep freeze and all
 that) nor try -DPLD_plmeta=ON again until post-release.  However, I
 did notice this issue so I thought I should bring it to your
 attention, and I encourage you to follow up immediately on a topic
 branch with the goal of pushing the plmeta/plrender fix for this issue
 soon after the release.
 

I am planning to pick it up after release.


--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-12 Thread Jim Dishaw

 On Mar 12, 2015, at 7:06 AM, Phil Rosenberg p.d.rosenb...@gmail.com wrote:
 
 This thread is becoming a bit unwieldy, but I will try to answer below
 
 @Jim
 I had already written and tested a fix for the hatchings and have just
 committed it, sorry if you spent time on this.

No problem. It was only a 5 minute fix. 

 Regarding the plhrsh issue, my build is fine  - although it is a
 static build, so perhaps that is the difference. However I couldn't
 see any reference to plhersh in plmeta.c. I will commit your change
 though as exposing it should not affect anything else.
 

It is in src/plmetafile.c not plmeta.c. 

 
 On 12 March 2015 at 04:03, Jim Dishaw j...@dishaw.org wrote:
 I made a fix for double line fill bug.  Please see attached file
 
 
 
 
 I noticed a different bug.  If you don't resize a plot, pressing enter 
 advances to the next page.  After resizing a plot, it takes more than one 
 key press to advance.  I'm not sure the cause, my suspicion is that there 
 are some additional commands (perhaps EOPs) creeping in at the end of the 
 plot buffer.  I will investigate further.
 
 
 On Mar 11, 2015, at 11:36 PM, Jim Dishaw j...@dishaw.org wrote:
 
 
 On Mar 11, 2015, at 4:59 PM, Phil Rosenberg p.d.rosenb...@gmail.com 
 wrote:
 
 Hi Alan
 
 A quick bit of stepping through my code has confirmed my suspicion
 from below. In plfill_soft plP_draphy is called for each line of the
 pattern and these lines are saved in the buffer, so basically writing
 to buffer needs switching off in this function. the change is about 3
 lines of code, but I will save it for post release if you prefer.
 
 That is essentially correct.  It appears that the issue is there is both a 
 PLESC_FILL in the buffer and then the lines that were generated by 
 plP_fill.  There should be only one and not both and the PLESC_FILL should 
 be the one to stay in the buffer.
 
 The first solution that comes to my mind is to set plsc-plbuf_write = 0 
 after the plbuf_esc() call and restore the original value at the end of the 
 function.
 
 Phil
 
 On 11 March 2015 at 18:31, Alan W. Irwin ir...@beluga.phys.uvic.ca 
 wrote:
 On 2015-03-11 13:01- Phil Rosenberg wrote:
 
 
 * Example 13; extra lines in Maurice, Vince, and Rafael parts
 of the pie chart, but the other slices are fine.
 
 This isn't shown on Windows. Perhaps the cause is that both the lines
 and the fill are being saved to the buffer meaning the lines get
 rendered twice. This is just a guess though
 
 
 --
 Dive into the World of Parallel Programming The Go Parallel Website, 
 sponsored
 by Intel and developed in partnership with Slashdot Media, is your hub for 
 all
 things parallel software development, from weekly thought leadership blogs 
 to
 news, videos, case studies, tutorials and more. Take a look and join the
 conversation now. http://goparallel.sourceforge.net/
 ___
 Plplot-devel mailing list
 Plplot-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/plplot-devel
 
 

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-12 Thread Jim Dishaw

On Mar 12, 2015, at 2:13 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:

 On 2015-03-11 14:49-0700 Alan W. Irwin wrote:
 
 Hi Phil:
 
 I just saw your one-line fix at
 http://sourceforge.net/p/plplot/plplot/ci/4e93f99a84a5c72d253c8791f813400ba2f46ff6.
 
 Does that really do the job?  For example, I noticed earlier in that code
 a test of pls-device rather than pls-dev, but I am just looking at
 patterns with no deep understanding of what is going on.
 
 
 Hi Phil:
 
 I haven't seen a response to the above question.
 
 @Phil, Jim:
 
 The recent exposure of plhrsh is not complete and has visibility
 issues for the shared library case.  In all cases where a private
 function like this needs to be exposed, you need a declaration in
 include/plplotP.h using the PLDLLIMPEXP macro.  Please fix.
 

I defer to Phil because I would send the patch to him anyway.


--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-12 Thread Alan W. Irwin
On 2015-03-11 14:49-0700 Alan W. Irwin wrote:

 Hi Phil:

 I just saw your one-line fix at
 http://sourceforge.net/p/plplot/plplot/ci/4e93f99a84a5c72d253c8791f813400ba2f46ff6.

 Does that really do the job?  For example, I noticed earlier in that code
 a test of pls-device rather than pls-dev, but I am just looking at
 patterns with no deep understanding of what is going on.


Hi Phil:

I haven't seen a response to the above question.

@Phil, Jim:

The recent exposure of plhrsh is not complete and has visibility
issues for the shared library case.  In all cases where a private
function like this needs to be exposed, you need a declaration in
include/plplotP.h using the PLDLLIMPEXP macro.  Please fix.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: plmeta/plrender

2015-03-12 Thread Alan W. Irwin
Hi Jim:

Could you clarify the purpose of the -mfi and -mfo options
and the plreadmetafile routine?

It appears the options simply set metafile input and output file names without
doing anything else contrary to their self documentation in src/plargs.c
of Read the specified PLplot metafile and Write the plot to the
specified PLplot metafile.

The only potential actual use of mf_infile I can find within the
source tree is in plreadmetafile.  That function appears to do
something similar to plrender, and it is only used in
examples/c/test_plbuf.c with an explicit name rather than NULL so the
result is mf_infile is just a placeholder (i.e., never actually used
in our current source tree).

By the way, if my interpretation of the purpose of plreadmetafile is
correct, can plrender simply call plreadmetafile (with an explicit
name for the plmeta file as read from the command line) to allow
removal of a lot of (redundant) code from plrender?

I can also find no actual use of mf_outfile anywhere in the source
tree.  So this appears to be a placeholder as well.

Since we are in deep freeze now, we should leave these placeholders in
place for this release and not mess with plrender, but post-release
(or on a topic branch now), you should remove these options or
actually use them for something (with better documentation strings
such as Set an input plmetafile name and Set an output plmetafile
name), and you might also wish to call plreadmetafile from plrender
(if my above interpretation of the purpose of plreadmetafile is
correct).

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-12 Thread Phil Rosenberg
This thread is becoming a bit unwieldy, but I will try to answer below

@Jim
I had already written and tested a fix for the hatchings and have just
committed it, sorry if you spent time on this.
Regarding the plhrsh issue, my build is fine  - although it is a
static build, so perhaps that is the difference. However I couldn't
see any reference to plhersh in plmeta.c. I will commit your change
though as exposing it should not affect anything else.

@Alan, Andrew and Arjen
I followed the link you gave Andrew, then a link to a further page
http://wiki.tcl.tk/1831. The tests on this page give correct results
on my Centos machine, although it is of note that there is a post on
that page with someone reporting correct test result onCentos, but the
same issue. I will check my Ubuntu machine tonight, presumably there
is little point performing tests of x via ssh with x forwarding. My
tcl version is 8.6 on Ubuntu, but only 8.5 on Centos, so perhaps the
tcl version explains the Centos problems. Note my tests on Ubuntu have
all been via shh with x forwarding, maybe trying direct connection
would help.

Phil

On 12 March 2015 at 04:03, Jim Dishaw j...@dishaw.org wrote:
 I made a fix for double line fill bug.  Please see attached file




 I noticed a different bug.  If you don't resize a plot, pressing enter 
 advances to the next page.  After resizing a plot, it takes more than one key 
 press to advance.  I'm not sure the cause, my suspicion is that there are 
 some additional commands (perhaps EOPs) creeping in at the end of the plot 
 buffer.  I will investigate further.


 On Mar 11, 2015, at 11:36 PM, Jim Dishaw j...@dishaw.org wrote:


 On Mar 11, 2015, at 4:59 PM, Phil Rosenberg p.d.rosenb...@gmail.com wrote:

 Hi Alan

 A quick bit of stepping through my code has confirmed my suspicion
 from below. In plfill_soft plP_draphy is called for each line of the
 pattern and these lines are saved in the buffer, so basically writing
 to buffer needs switching off in this function. the change is about 3
 lines of code, but I will save it for post release if you prefer.


 That is essentially correct.  It appears that the issue is there is both a 
 PLESC_FILL in the buffer and then the lines that were generated by plP_fill. 
  There should be only one and not both and the PLESC_FILL should be the one 
 to stay in the buffer.

 The first solution that comes to my mind is to set plsc-plbuf_write = 0 
 after the plbuf_esc() call and restore the original value at the end of the 
 function.

 Phil

 On 11 March 2015 at 18:31, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
 On 2015-03-11 13:01- Phil Rosenberg wrote:


 * Example 13; extra lines in Maurice, Vince, and Rafael parts
 of the pie chart, but the other slices are fine.

 This isn't shown on Windows. Perhaps the cause is that both the lines
 and the fill are being saved to the buffer meaning the lines get
 rendered twice. This is just a guess though



 --
 Dive into the World of Parallel Programming The Go Parallel Website, 
 sponsored
 by Intel and developed in partnership with Slashdot Media, is your hub for 
 all
 things parallel software development, from weekly thought leadership blogs to
 news, videos, case studies, tutorials and more. Take a look and join the
 conversation now. http://goparallel.sourceforge.net/
 ___
 Plplot-devel mailing list
 Plplot-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/plplot-devel



--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status: plmeta/plrender

2015-03-12 Thread Jim Dishaw


 On Mar 12, 2015, at 6:08 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
 
 Hi Jim:
 
 Could you clarify the purpose of the -mfi and -mfo options
 and the plreadmetafile routine?
 

-mfi sets the file name that plreadmetafile will use if one is not otherwise 
specified by the caller. Nothing will happen unless there is a plreadmetafile() 
call in the program. 

-mfo option is a placeholder at this point. What it will do is save all the 
plots to a metafile simultaneous with the output device. I have not decided 
what to do if plmeta is selected. 

 It appears the options simply set metafile input and output file names without
 doing anything else contrary to their self documentation in src/plargs.c
 of Read the specified PLplot metafile and Write the plot to the
 specified PLplot metafile.
 
 The only potential actual use of mf_infile I can find within the
 source tree is in plreadmetafile.  That function appears to do
 something similar to plrender, and it is only used in
 examples/c/test_plbuf.c with an explicit name rather than NULL so the
 result is mf_infile is just a placeholder (i.e., never actually used
 in our current source tree).

I set a name in test_plbuf just to make it easier during testing. I set it up 
to support both ways because both ways are useful. Right now the metafile is 
rendered with a plreadmetafile() call. I experimented with different 
approaches, but settled on triggering the rendering with a function call. This 
merits further discussion after release. 

 
 By the way, if my interpretation of the purpose of plreadmetafile is
 correct, can plrender simply call plreadmetafile (with an explicit
 name for the plmeta file as read from the command line) to allow
 removal of a lot of (redundant) code from plrender?

Absolutely. After release I'm going to remove all the parsing code. I'm also 
going to add the capability to read from shared memory and over the network. 

 
 I can also find no actual use of mf_outfile anywhere in the source
 tree.  So this appears to be a placeholder as well.

Yep, it will be the tee command in Unix. 

 
 Since we are in deep freeze now, we should leave these placeholders in
 place for this release and not mess with plrender, but post-release
 (or on a topic branch now), you should remove these options or
 actually use them for something (with better documentation strings
 such as Set an input plmetafile name and Set an output plmetafile
 name), and you might also wish to call plreadmetafile from plrender
 (if my above interpretation of the purpose of plreadmetafile is
 correct).
 
 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
 __

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-11 Thread Phil Rosenberg
Hi Alan
Thanks for the screenshots. Comments below

On 11 March 2015 at 18:31, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
 On 2015-03-11 13:01- Phil Rosenberg wrote:


 * Example 13; extra lines in Maurice, Vince, and Rafael parts
 of the pie chart, but the other slices are fine.

 This isn't shown on Windows. Perhaps the cause is that both the lines
 and the fill are being saved to the buffer meaning the lines get
 rendered twice. This is just a guess though


 A screenshot is attached as the second attachment

I have checked and see the same on my Linux machines. I will have to
look into the cause, which I can only assume must be within the plplot
core/buffer code as the wxWidgets driver does not do native hatch
filling. My previous guess is still my best guess


 * Example 28.04 has a strange colour change for certain ranges indicated
 below of the rendering of the

 The future of our civilization depends on software freedom.
 ^^^


 I don't see this on Windows wx3.0, Ubuntu wx3.0 or Centos wx3.0 so
 you'll have to send me a screen shot.


 A screenshot is attached as the first attachment.


I have no idea what is causing this. I think it is an antialiasing
effect which is almost certainly is related to whatever rendering
engine your version of wxWidgets is wrapping (which I would have
guessed would be cairo, but that is only a guess). Whatever it is
there is certainly nothing I am able to do about it so we need to just
chalk this up to one of those things

 * To get proper interactive capability, must implement an
 attached driver option that does not launch a separate
 wxPLViewer instance.


 This will not happen (well at least not from me). The whole point of
 the changes was to detach the driver, because wxWidgets is not
 designed to be attached.


 It sounds like this will be difficult to provide this driver option,
 but I hope it is not impossible and you can put this on your long-term
 agenda because true interactive capability is an important use case
 for any device driver that is not file oriented. Think of the example
 of a sophisticated interactive app that manipulates data according to
 what key or mouse button is struck and the position of the cursor at
 the time of the key/mouse strike.  Octave comes to mind (which
 requires true interactivity for plot devices as demonstrated by some
 of our p octave examples), but I also ran into an interactive
 application to manipulate astronomical spectra in the 90's that made a
 big impression on me since that application was the basis of ~20
 astronomers research work for at least a decade.  You could link up
 such a sophisticated interactive application with PLplot (as is done
 with the octave binding), and then run it with any of our interactive
 devices (xwin, tk, qtwidgets, xcairo, wingcc?) that provide cursor
 capability.  But currently that important use case is not possible
 with the new version of wxwidgets.

I didn't mean interactivity wouldn't happen, just that an attached
model of how this will be done won't happen. wxWidgets just isn't
really built to be run from within a library. Although apparently it
can be done, but it is an edge case. I made some attempt at it about a
year ago, but I gave up because it was just too much of a nightmare -
the biggest of the many problems that I hit being that it requires two
threads and plplot isn't thread safe.
The new code basically uses a client server model. The plplot
application sends commands (via the memory map) to the viewer to
render things. There is also some limited communication back (e.g.
locate mode), but I have deliberately kept this to a minimum for
simplicity. There is no reason (other than the time taken to code it)
why there cannot be extensive two way comms.


Phil

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-11 Thread Andrew Ross

Phil,

Try reading http://wiki.tcl.tk/1829 for the tk problem. It suggests an 
issue with your X security which you probably want to investigate anyway.

For me things just work with Ubuntu. Though I should perhaps be more
precise that it is Kubuntu (with KDE as the window manager) that I use 
rather than vanilla Ubuntu. I'd be very surprised if X was not set up 
securely by default though.

Andrew

On Wed, Mar 11, 2015 at 08:35:50PM +, Phil Rosenberg wrote:
 Hi Alan
 Unfortunately you can probably ignore that email.
 
 On my work centos machine I tried running an example under the xwin
 device - thinking that a buffer problem would be likely to show up
 there as well as in the tk device. I then got just a black window and
 a hang. Moving back in time I found that the commit I listed gave the
 same black window and hang but the one before gave fine results.
 I've just looked at this from home and both on my Ubuntu PC and my
 Centos PC (both SSH'd in with x forwarding from Cygwin) ant the tip of
 master runs fin in both cases.
 
 So now I am utterly confused and have not got the tk driver running.
 
 Phil
 
 On 11 March 2015 at 19:27, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
  On 2015-03-11 12:32- Arjen Markus wrote:
 
  Hi Phil,
 
 
  The message is due to a security problem in the X server if you use
 
  the default security settings. I know of it but I do not have a handy
  receipe to solve it. Tk's send command allows you to send any command
  to the X host, which is why this message pops up.
 
  Hi Phil:
 
  I think Arjen is right.  Hopefully Andrew (who uses Ubuntu a lot for
  testing) will know the recipe to properly authorize -dev tk on Ubuntu.  For
  some reason I have never run into this authorization issue on Debian
  stable, but that is probably because (by design) Debian default
  security settings are quite weak.
 
  I also noticed in another message that you presumably had solved that
  authorization issue and found a commit (id = 1e402417c1f) that your
  tests showed introduced a -dev tk rendering regression, but I cannot
  figure out what that regression might be so could you describe it?
 
  The issue is that both 1e402417c1f^ and 1e402417c1f give single GUI
  -dev tk results here that both look fine to me (other than the zoom
  issue) for example 1 while for master tip I get two GUI's (one with
  the Tk decorations and no plot, and the other an undecorated xwin-like
  plot).  I have attached a screenshot of that master tip result so you will
  know exactly what I am referring too.
 
  I will now do my own git bisects to find when the zoom issue was
  introduced and when the two-GUI issue was introduced.
 
 
  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
  __

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-11 Thread Andrew Ross
On Wed, Mar 11, 2015 at 02:30:04PM -0700, Alan Irwin wrote:
 Phil said:
 
  Hi Alan
  Unfortunately you can probably ignore that email.
 
  On my work centos machine I tried running an example under the xwin
 device - thinking that a buffer problem would be likely to show up
 there as well as in the tk device. I then got just a black window and
 a hang. Moving back in time I found that the commit I listed gave the
 same black window and hang but the one before gave fine results.
 I've just looked at this from home and both on my Ubuntu PC and my
 Centos PC (both SSH'd in with x forwarding from Cygwin) ant the tip of
 master runs fin in both cases.
 
  So now I am utterly confused and have not got the tk driver running.
 
 My guess is that SSH with X forwarding has figured out all the X
 authorization issues, while those may still occur whenever you try to
 use direct access.  So I would encourage you to test that hypothesis
 by trying -dev tk over an SSH X forwarded connection.  That may allow
 you to verify the two-GUI issue for -dev tk for master tip.
 
 Assuming that hypothesis is correct, the change (for direct access for
 you) from working screen to black screen from 1e402417c1f^ to
 1e402417c1f may not be a regression, but instead the result of
 (inadvertently) tightening up the X security model with that plbuf
 change.
 
 @Andrew:
 I hope you respond to this by advising Phil the best way
 to have properly authorized X access when using Ubuntu
 directly, checking whether the above plbuf change makes a difference
 in your -dev xwin and -dev tk results on Ubuntu, etc.
 
 For what it is worth, for the direct case I am just using the default
 X authorization for Debian that you get with the traditional startx
 method of starting my (KDE) desktop.  In other words, I don't use any
 of the xdm, kdm, or gdm3 display-manager methods of starting X for the
 direct case, but I am not sure whether that is relevant or not. But
 apparently, X is properly authorized by this method at least for
 Debian so the plbuf change referred to above has no effect on -dev tk
 results for me.

Actually, dredging my memories I vaguely remember problems in the past 
with this. Lo and behold I searched the list archive and found the
following thread from 2009

http://sourceforge.net/p/plplot/mailman/plplot-general/thread/1258412677.12670.12.camel%40dventimi-laptop/#msg23989000

which documents a lot of this. Phil - which version of Ubuntu / Tcl / Tk 
are you using? It seems this was fixed in the Ubuntu Tcl 8.5 packages a 
long time ago.

Andrew

 
~ 

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-11 Thread Alan W. Irwin
Phil said:

 I didn't mean interactivity wouldn't happen, just that an attached
model of how this will be done won't happen. wxWidgets just isn't
really built to be run from within a library. Although apparently it
can be done, but it is an edge case. I made some attempt at it about a
year ago, but I gave up because it was just too much of a nightmare -
the biggest of the many problems that I hit being that it requires two
threads and plplot isn't thread safe.

Point taken.

 The new code basically uses a client server model. The plplot
application sends commands (via the memory map) to the viewer to
render things. There is also some limited communication back (e.g.
locate mode), but I have deliberately kept this to a minimum for
simplicity. There is no reason (other than the time taken to code it)
why there cannot be extensive two way comms.

I am very glad to hear there is this future possibility of providing
the important full interactivity capability for -dev wxwidgets. So in
my report you should mentally substitute needs full interactivity
capability to be developed wherever before I remarked about requiring
an attached capability.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-11 Thread Alan W. Irwin
Phil said:

 Hi Alan
 Unfortunately you can probably ignore that email.

 On my work centos machine I tried running an example under the xwin
device - thinking that a buffer problem would be likely to show up
there as well as in the tk device. I then got just a black window and
a hang. Moving back in time I found that the commit I listed gave the
same black window and hang but the one before gave fine results.
I've just looked at this from home and both on my Ubuntu PC and my
Centos PC (both SSH'd in with x forwarding from Cygwin) ant the tip of
master runs fin in both cases.

 So now I am utterly confused and have not got the tk driver running.

My guess is that SSH with X forwarding has figured out all the X
authorization issues, while those may still occur whenever you try to
use direct access.  So I would encourage you to test that hypothesis
by trying -dev tk over an SSH X forwarded connection.  That may allow
you to verify the two-GUI issue for -dev tk for master tip.

Assuming that hypothesis is correct, the change (for direct access for
you) from working screen to black screen from 1e402417c1f^ to
1e402417c1f may not be a regression, but instead the result of
(inadvertently) tightening up the X security model with that plbuf
change.

@Andrew:
I hope you respond to this by advising Phil the best way
to have properly authorized X access when using Ubuntu
directly, checking whether the above plbuf change makes a difference
in your -dev xwin and -dev tk results on Ubuntu, etc.

For what it is worth, for the direct case I am just using the default
X authorization for Debian that you get with the traditional startx
method of starting my (KDE) desktop.  In other words, I don't use any
of the xdm, kdm, or gdm3 display-manager methods of starting X for the
direct case, but I am not sure whether that is relevant or not. But
apparently, X is properly authorized by this method at least for
Debian so the plbuf change referred to above has no effect on -dev tk
results for me.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-11 Thread Phil Rosenberg
Hi Alan
Unfortunately you can probably ignore that email.

On my work centos machine I tried running an example under the xwin
device - thinking that a buffer problem would be likely to show up
there as well as in the tk device. I then got just a black window and
a hang. Moving back in time I found that the commit I listed gave the
same black window and hang but the one before gave fine results.
I've just looked at this from home and both on my Ubuntu PC and my
Centos PC (both SSH'd in with x forwarding from Cygwin) ant the tip of
master runs fin in both cases.

So now I am utterly confused and have not got the tk driver running.

Phil

On 11 March 2015 at 19:27, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
 On 2015-03-11 12:32- Arjen Markus wrote:

 Hi Phil,


 The message is due to a security problem in the X server if you use

 the default security settings. I know of it but I do not have a handy
 receipe to solve it. Tk's send command allows you to send any command
 to the X host, which is why this message pops up.

 Hi Phil:

 I think Arjen is right.  Hopefully Andrew (who uses Ubuntu a lot for
 testing) will know the recipe to properly authorize -dev tk on Ubuntu.  For
 some reason I have never run into this authorization issue on Debian
 stable, but that is probably because (by design) Debian default
 security settings are quite weak.

 I also noticed in another message that you presumably had solved that
 authorization issue and found a commit (id = 1e402417c1f) that your
 tests showed introduced a -dev tk rendering regression, but I cannot
 figure out what that regression might be so could you describe it?

 The issue is that both 1e402417c1f^ and 1e402417c1f give single GUI
 -dev tk results here that both look fine to me (other than the zoom
 issue) for example 1 while for master tip I get two GUI's (one with
 the Tk decorations and no plot, and the other an undecorated xwin-like
 plot).  I have attached a screenshot of that master tip result so you will
 know exactly what I am referring too.

 I will now do my own git bisects to find when the zoom issue was
 introduced and when the two-GUI issue was introduced.


 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
 __

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-11 Thread Alan W. Irwin
On 2015-03-11 11:33- Arjen Markus wrote:

 I just ran all the examples with the wingcc device under Cygwin (of
course after having retrieved the latest version from git and building
Plplot again) and as far as I can tell everything is looking fine. At
the very least there are no strange gaps or oddly placed text strings
or unexpected colours. Short of a formal comparison against previously
saved screenshots (should I have had these) I cannot see any
differences. Which is a good thing.

Thanks, Arjen, for performing this most reassuring (at least for
wingcc) test.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-11 Thread Alan W. Irwin

On 2015-03-11 12:32- Arjen Markus wrote:


Hi Phil,



The message is due to a security problem in the X server if you use

the default security settings. I know of it but I do not have a handy
receipe to solve it. Tk's send command allows you to send any command
to the X host, which is why this message pops up.

Hi Phil:

I think Arjen is right.  Hopefully Andrew (who uses Ubuntu a lot for
testing) will know the recipe to properly authorize -dev tk on Ubuntu.  For
some reason I have never run into this authorization issue on Debian
stable, but that is probably because (by design) Debian default
security settings are quite weak.

I also noticed in another message that you presumably had solved that
authorization issue and found a commit (id = 1e402417c1f) that your
tests showed introduced a -dev tk rendering regression, but I cannot
figure out what that regression might be so could you describe it?

The issue is that both 1e402417c1f^ and 1e402417c1f give single GUI
-dev tk results here that both look fine to me (other than the zoom
issue) for example 1 while for master tip I get two GUI's (one with
the Tk decorations and no plot, and the other an undecorated xwin-like
plot).  I have attached a screenshot of that master tip result so you will
know exactly what I am referring too.

I will now do my own git bisects to find when the zoom issue was
introduced and when the two-GUI issue was introduced.

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
__--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-11 Thread Alan W. Irwin
On 2015-03-10 21:41- Phil Rosenberg wrote:

 Hi Alan and Jim
 Right, well Jim's patch series is committed and I have just made one
 more additional commit regarding the buffer which I think now gives us
 a buffer which is (pretty close to, if not completely) bug free!!! Or
 at the very least it is sufficient to allow the wxWidgets driver to
 render as well as from direct commands.

Note, to everybody.  There is an official deep freeze notice near
the end of this e-mail.

@ Andrew, Phil, and Jim:

Before getting to wxwidgets test results I regret to say that a recent
plbuf change has nailed us again.  There is now a release showstopper
where -dev tk produces really strange looking results.  I found this
issue via checking -dev tk for the zoom regression where hitting the
zoom button just produces a blank (black) plot.  I confirm that
regression as well as a newly introduced regression for that device
(two windows are displayed rather than one with one of them without a
plot but with the plframe decorations and the other showing an
xwin-like plot windows with no decorations). This new regression and
the zoom regression are showstoppers for the current release so your
confirmation and fix for these rendering regressions will be much
appreciated.  You should also look carefully at -dev wingcc to see
whether recent plbuf changes have introduced rendering regressions
there as well (assuming you have looked in detail before at wingcc
results for all examples, and therefore know what rendered nicely in
the old days).

If none of you beat me to it, I will follow up starting roughly 12 hours
from now with a git bisect to find out the first commit that caused
each of these regressions, and hopefully the fix for each regression
will be straightforward after that.

@Arjen:
Just in case you remember how well wingcc rendered before, I would
appreciate you double-checking how wingcc renders now.

@Phil:

Naturely, I found the above new rendering regression right at the end
of a very long series of tests of wxwidgets which I will probably have
to repeat once the above plbuf issue(s) are fixed (sigh).  So for what
it is worth, here is the current status of wxwidgets on Linux as of
commit id = afd37a9.

I did this long test with the following command:

for SEQ in $(seq -w 0 33); do
   examples/c/x${SEQ}c -dev wxwidgets
   read ANSWER
done

(where read ANSWER supplies a pause between examples
so you don't have one zillion instances of wxPLViewer going
at the same time).

There is a definite improvement compared to when I ran such a test
before, but I note the following large number of minor issues (mostly
rendering issues and non of them are release critical) that still
exist on Linux:

* text much too small for all examples.  Increasing
all text sizes by something close to a factor of two (say
to fill all the squares by the numbers in example 2.2 just like
for the xcairo, qtwidget, and xwin device) is needed.

* Example 13; extra lines in Maurice, Vince, and Rafael parts
of the pie chart, but the other slices are fine.

* Example 17 is extremely slow to display and the erases are not getting
done when the plot is rescaled.  Attached mode?

* Example 20 is extremely slow to display and does not have any
interactive capability (the third page should allow you to select a
region with the cursor).  Compare the cursor capability shown with
this example for -dev xwin.

Note -dev wxwidgets cursor capability is currently similar to
that of -dev xcairo and -dev qtwidget.  All three devices print
out cursor position results for example 1 with the -locate option,
but all three devices fail to allow the user to select
a region in example 3.03.  So all three have to be updated
to have the same cursor capabilities as -dev xwin.
In addition, I presume this capability would only work
for the qtwidgets case in attached mode (see below).

* Example 26.02 still has an issue with too large a legend for
the Cyrillic version of the plot.

* Example 28.04 has a strange colour change for certain ranges indicated
below of the rendering of the

The future of our civilization depends on software freedom.
 ^^^

3D string.  Those colour changes occur when the letters in the string
are mostly reduced to the (expected) straight lines by the 3D affine
transformation.  This may be due to some strange issue with my Debian
stable wxwidgets software library and have nothing to do with PLplot.
If you cannot reproduce those colour changes, I will send a screen
shot.

* Example 28.05 affine transformation issues.

* Example 30.02 ugly looking gradient results are due to falling back
to core software emulation of a linear gradient.  Instead, as
discussed before a linear gradient based on the wxwidgets API should
be used instead to get very nice results for this example (such as
those from the cairo and qt devices).

* Example 34: the qtwidgets device does not support draw mode.
However, if you want to 

Re: [Plplot-devel] Release status

2015-03-11 Thread Phil Rosenberg
Hi Alan
Sorry I only just spotted your email.
I have just made a commit, but it was technically a bug fix (or at
least half of it was), but I won't make any further commits.

Phil

On 11 March 2015 at 10:49, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
 On 2015-03-10 21:41- Phil Rosenberg wrote:

 Hi Alan and Jim
 Right, well Jim's patch series is committed and I have just made one
 more additional commit regarding the buffer which I think now gives us
 a buffer which is (pretty close to, if not completely) bug free!!! Or
 at the very least it is sufficient to allow the wxWidgets driver to
 render as well as from direct commands.


 Note, to everybody.  There is an official deep freeze notice near
 the end of this e-mail.

 @ Andrew, Phil, and Jim:

 Before getting to wxwidgets test results I regret to say that a recent
 plbuf change has nailed us again.  There is now a release showstopper
 where -dev tk produces really strange looking results.  I found this
 issue via checking -dev tk for the zoom regression where hitting the
 zoom button just produces a blank (black) plot.  I confirm that
 regression as well as a newly introduced regression for that device
 (two windows are displayed rather than one with one of them without a
 plot but with the plframe decorations and the other showing an
 xwin-like plot windows with no decorations). This new regression and
 the zoom regression are showstoppers for the current release so your
 confirmation and fix for these rendering regressions will be much
 appreciated.  You should also look carefully at -dev wingcc to see
 whether recent plbuf changes have introduced rendering regressions
 there as well (assuming you have looked in detail before at wingcc
 results for all examples, and therefore know what rendered nicely in
 the old days).

 If none of you beat me to it, I will follow up starting roughly 12 hours
 from now with a git bisect to find out the first commit that caused
 each of these regressions, and hopefully the fix for each regression
 will be straightforward after that.

 @Arjen:
 Just in case you remember how well wingcc rendered before, I would
 appreciate you double-checking how wingcc renders now.

 @Phil:

 Naturely, I found the above new rendering regression right at the end
 of a very long series of tests of wxwidgets which I will probably have
 to repeat once the above plbuf issue(s) are fixed (sigh).  So for what
 it is worth, here is the current status of wxwidgets on Linux as of
 commit id = afd37a9.

 I did this long test with the following command:

 for SEQ in $(seq -w 0 33); do
   examples/c/x${SEQ}c -dev wxwidgets
   read ANSWER
 done

 (where read ANSWER supplies a pause between examples
 so you don't have one zillion instances of wxPLViewer going
 at the same time).

 There is a definite improvement compared to when I ran such a test
 before, but I note the following large number of minor issues (mostly
 rendering issues and non of them are release critical) that still
 exist on Linux:

 * text much too small for all examples.  Increasing
 all text sizes by something close to a factor of two (say
 to fill all the squares by the numbers in example 2.2 just like
 for the xcairo, qtwidget, and xwin device) is needed.

 * Example 13; extra lines in Maurice, Vince, and Rafael parts
 of the pie chart, but the other slices are fine.

 * Example 17 is extremely slow to display and the erases are not getting
 done when the plot is rescaled.  Attached mode?

 * Example 20 is extremely slow to display and does not have any
 interactive capability (the third page should allow you to select a
 region with the cursor).  Compare the cursor capability shown with
 this example for -dev xwin.

 Note -dev wxwidgets cursor capability is currently similar to
 that of -dev xcairo and -dev qtwidget.  All three devices print
 out cursor position results for example 1 with the -locate option,
 but all three devices fail to allow the user to select
 a region in example 3.03.  So all three have to be updated
 to have the same cursor capabilities as -dev xwin.
 In addition, I presume this capability would only work
 for the qtwidgets case in attached mode (see below).

 * Example 26.02 still has an issue with too large a legend for
 the Cyrillic version of the plot.

 * Example 28.04 has a strange colour change for certain ranges indicated
 below of the rendering of the

 The future of our civilization depends on software freedom.
 ^^^

 3D string.  Those colour changes occur when the letters in the string
 are mostly reduced to the (expected) straight lines by the 3D affine
 transformation.  This may be due to some strange issue with my Debian
 stable wxwidgets software library and have nothing to do with PLplot.
 If you cannot reproduce those colour changes, I will send a screen
 shot.

 * Example 28.05 affine transformation issues.

 * Example 30.02 ugly looking gradient results are due to falling 

Re: [Plplot-devel] Release status

2015-03-11 Thread Arjen Markus
Hi Alan,

 -Original Message-
 From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
 Sent: Wednesday, March 11, 2015 11:49 AM
 To: Andrew Ross; Phil Rosenberg; Jim Dishaw
 Cc: PLplot development list
 Subject: Re: [Plplot-devel] Release status

 @Arjen:
 Just in case you remember how well wingcc rendered before, I would appreciate 
 you
 double-checking how wingcc renders now.



I just ran all the examples with the wingcc device under Cygwin (of course 
after having retrieved the latest version from git and building Plplot again) 
and as far as I can tell everything is looking fine. At the very least there 
are no strange gaps or oddly placed text strings or unexpected colours. Short 
of a formal comparison against previously saved screenshots (should I have had 
these) I cannot see any differences. Which is a good thing.

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.
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-11 Thread Phil Rosenberg
I've just tested the tk device over my lunch break. I don't get the tk
driver on my windows build, just ntk.

On my work Cento machine and my home Ubuntu machine (The latter of
which I connected to via ssh with X11 forwarding) both give the
following

$ examples/c/x00c -dev tk
X server insecure (must use xauth-style authorization); command ignored
while executing
send $client set server_name [list $server_name]
(procedure plserver_link_init line 25)
invoked from within
plserver_link_init
(procedure plserver_init line 85)
invoked from within
plserver_init

Then they just hang. No window is displayed at all. At first I thought
the error was something to do with the X11 forwarding, but I get it on
my Centos machine which I am sat in front of too.

Phil

On 11 March 2015 at 11:33, Arjen Markus arjen.mar...@deltares.nl wrote:
 Hi Alan,

 -Original Message-
 From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
 Sent: Wednesday, March 11, 2015 11:49 AM
 To: Andrew Ross; Phil Rosenberg; Jim Dishaw
 Cc: PLplot development list
 Subject: Re: [Plplot-devel] Release status

 @Arjen:
 Just in case you remember how well wingcc rendered before, I would
 appreciate you
 double-checking how wingcc renders now.


 I just ran all the examples with the wingcc device under Cygwin (of course
 after having retrieved the latest version from git and building Plplot
 again) and as far as I can tell everything is looking fine. At the very
 least there are no strange gaps or oddly placed text strings or unexpected
 colours. Short of a formal comparison against previously saved screenshots
 (should I have had these) I cannot see any differences. Which is a good
 thing.

 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.

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-11 Thread Arjen Markus
Hi Phil,



The message is due to a security problem in the X server if you use the default 
security settings. I know of it but I do not have a handy receipe to solve it. 
Tk's send command allows you to send any command to the X host, which is why 
this message pops up.



The Tk driver requires some Unix-specific routines and therefore they are not 
buildable on Windows. The ntk driver does not. Something I might look into 
post-release.



Regards,



Arjen








 -Original Message-
 From: Phil Rosenberg [mailto:p.d.rosenb...@gmail.com]
 Sent: Wednesday, March 11, 2015 1:23 PM
 To: Arjen Markus
 Cc: Alan W. Irwin; Andrew Ross; Jim Dishaw; PLplot development list
 Subject: Re: [Plplot-devel] Release status

 I've just tested the tk device over my lunch break. I don't get the tk driver 
 on my
 windows build, just ntk.

 On my work Cento machine and my home Ubuntu machine (The latter of which I
 connected to via ssh with X11 forwarding) both give the following

 $ examples/c/x00c -dev tk
 X server insecure (must use xauth-style authorization); command ignored while
 executing send $client set server_name [list $server_name]
 (procedure plserver_link_init line 25) invoked from within 
 plserver_link_init
 (procedure plserver_init line 85)
 invoked from within
 plserver_init

 Then they just hang. No window is displayed at all. At first I thought the 
 error was
 something to do with the X11 forwarding, but I get it on my Centos machine 
 which I
 am sat in front of too.

 Phil

 On 11 March 2015 at 11:33, Arjen Markus arjen.mar...@deltares.nl wrote:
  Hi Alan,
 
  -Original Message-
  From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
  Sent: Wednesday, March 11, 2015 11:49 AM
  To: Andrew Ross; Phil Rosenberg; Jim Dishaw
  Cc: PLplot development list
  Subject: Re: [Plplot-devel] Release status
 
  @Arjen:
  Just in case you remember how well wingcc rendered before, I would
  appreciate you double-checking how wingcc renders now.
 
 
  I just ran all the examples with the wingcc device under Cygwin (of course
  after having retrieved the latest version from git and building Plplot
  again) and as far as I can tell everything is looking fine. At the very
  least there are no strange gaps or oddly placed text strings or unexpected
  colours. Short of a formal comparison against previously saved screenshots
  (should I have had these) I cannot see any differences. Which is a good
  thing.
 
  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.

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.
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-11 Thread Jim Dishaw
I will take a look at it when I get to my machine. I think I know the problem. 



 On Mar 11, 2015, at 8:22 AM, Phil Rosenberg p.d.rosenb...@gmail.com wrote:
 
 I've just tested the tk device over my lunch break. I don't get the tk
 driver on my windows build, just ntk.
 
 On my work Cento machine and my home Ubuntu machine (The latter of
 which I connected to via ssh with X11 forwarding) both give the
 following
 
 $ examples/c/x00c -dev tk
 X server insecure (must use xauth-style authorization); command ignored
 while executing
 send $client set server_name [list $server_name]
 (procedure plserver_link_init line 25)
 invoked from within
 plserver_link_init
 (procedure plserver_init line 85)
 invoked from within
 plserver_init
 
 Then they just hang. No window is displayed at all. At first I thought
 the error was something to do with the X11 forwarding, but I get it on
 my Centos machine which I am sat in front of too.
 
 Phil
 
 On 11 March 2015 at 11:33, Arjen Markus arjen.mar...@deltares.nl wrote:
 Hi Alan,
 
 -Original Message-
 From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
 Sent: Wednesday, March 11, 2015 11:49 AM
 To: Andrew Ross; Phil Rosenberg; Jim Dishaw
 Cc: PLplot development list
 Subject: Re: [Plplot-devel] Release status
 
 @Arjen:
 Just in case you remember how well wingcc rendered before, I would
 appreciate you
 double-checking how wingcc renders now.
 
 I just ran all the examples with the wingcc device under Cygwin (of course
 after having retrieved the latest version from git and building Plplot
 again) and as far as I can tell everything is looking fine. At the very
 least there are no strange gaps or oddly placed text strings or unexpected
 colours. Short of a formal comparison against previously saved screenshots
 (should I have had these) I cannot see any differences. Which is a good
 thing.
 
 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.

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-11 Thread Phil Rosenberg
I can now put my hands up and say the regression was me. At least on
my Centos machine running the xwin driver results in a blank window
and a hang until I checkout before this commit

commit 1e402417c1f3e87c391fe428f936153c2a10e8cc
Author: Phil Rosenberg p.d.rosenb...@gmail.com
Date: Fri Feb 27 17:12:03 2015 +
Fixed bug in rdbuf_di.
Save cursubpage on replot
call plP_eop() on replot which ensures that the first plP_bop() call
actually does something.

I guess that somehow I have set up an infinite loop of eop/bop calls
or something.

If someone would like to confirm that this is the faulty commit then
please let me know. The commit before this is
1e3786c758f78bff13086cf26ab81145b4e2e14d which works for me.

I will try to find some time to work on this tonight or tomorrow night.

Phil

On 11 March 2015 at 13:01, Phil Rosenberg p.d.rosenb...@gmail.com wrote:

 * Example 13; extra lines in Maurice, Vince, and Rafael parts
 of the pie chart, but the other slices are fine.
 This isn't shown on Windows. Perhaps the cause is that both the lines
 and the fill are being saved to the buffer meaning the lines get
 rendered twice. This is just a guess though

 * Example 17 is extremely slow to display and the erases are not getting
 done when the plot is rescaled.  Attached mode?

 I will add this to my to do list


 * Example 20 is extremely slow to display and does not have any
 interactive capability (the third page should allow you to select a
 region with the cursor).  Compare the cursor capability shown with
 this example for -dev xwin.

 Note -dev wxwidgets cursor capability is currently similar to
 that of -dev xcairo and -dev qtwidget.  All three devices print
 out cursor position results for example 1 with the -locate option,
 but all three devices fail to allow the user to select
 a region in example 3.03.  So all three have to be updated
 to have the same cursor capabilities as -dev xwin.
 In addition, I presume this capability would only work
 for the qtwidgets case in attached mode (see below).

 Again I will add it to my list


 * Example 26.02 still has an issue with too large a legend for
 the Cyrillic version of the plot.
 See my post to a different thread.

 * Example 28.04 has a strange colour change for certain ranges indicated
 below of the rendering of the

 The future of our civilization depends on software freedom.
 ^^^

 I don't see this on Windows wx3.0, Ubuntu wx3.0 or Centos wx3.0 so
 you'll have to send me a screen shot.


 3D string.  Those colour changes occur when the letters in the string
 are mostly reduced to the (expected) straight lines by the 3D affine
 transformation.  This may be due to some strange issue with my Debian
 stable wxwidgets software library and have nothing to do with PLplot.
 If you cannot reproduce those colour changes, I will send a screen
 shot.

 * Example 28.05 affine transformation issues.

 Already known, but better than it was


 * Example 30.02 ugly looking gradient results are due to falling back
 to core software emulation of a linear gradient.  Instead, as
 discussed before a linear gradient based on the wxwidgets API should
 be used instead to get very nice results for this example (such as
 those from the cairo and qt devices).

 Same as the old driver - I will add native gradient fill to my to do
 list, but I would guess that shading with alpha is broken in general.
 This is due to outlining as a workaround to the seaming problem for
 solid colour shading. It will need some changes to the core code to
 fix.


 * Example 34: the qtwidgets device does not support draw mode.
 However, if you want to implement this someday you should follow what
 is done for xcairo (which is the only device so far that has draw mode
 capability).

 Again I'll add it to the list


 * To get proper interactive capability, must implement an
 attached driver option that does not launch a separate
 wxPLViewer instance.

 This will not happen (well at least not from me). The whole point of
 the changes was to detach the driver, because wxWidgets is not
 designed to be attached.


 * There was also a the following warning being emitted by g++

 /home/software/plplot/HEAD/plplot.git/drivers/wxwidgets.cpp: In
 function ‘void plD_init_wxwidgets(PLStream*)’:
 /home/software/plplot/HEAD/plplot.git/drivers/wxwidgets.cpp:186:23:
 warning: converting to non-pointer type ‘PLINT {aka int}’ from NULL
 [-Wconversion-null]

 Did you really want to set the device id (which is just an integer) to
 zero here?  If so, you should use 0 rather than NULL.  But I thought
 that device id integer was supposed to be fixed and unique to each
 device in which case it would generally not be a good idea to zero it.  But
 on
 the other hand, I so far have not detected any issues from this
 zeroing so I don't think there is any urgency here
 (i.e., you can deal with this post-release).

 This is a bug, it was supposed to be pls-dev = NULL. This has

Re: [Plplot-devel] Release status

2015-03-10 Thread Phil Rosenberg
 Hi Alan and Jim
Right, well Jim's patch series is committed and I have just made one
more additional commit regarding the buffer which I think now gives us
a buffer which is (pretty close to, if not completely) bug free!!! Or
at the very least it is sufficient to allow the wxWidgets driver to
render as well as from direct commands.

Firstly I wanted to say a big thanks Jim for all your input with that
as well as with the plmeta driver. It's been much appreciated.

Secondly, I guess that means you can freeze the core code Alan. I'm
going to just make a couple of wxWidgets mods this evening and then I
am going to stop meddling until after the release. I do still need to
sort the docs out as well.

Phil

On 9 March 2015 at 21:09, Phil Rosenberg p.d.rosenb...@gmail.com wrote:


 Please take a look at his patch series he sent this weekend.  One of those
 patches
 apparently was to fix a wxwidgets issue so part/all of that series may
 be exactly what you need, but I am leaving it to you to evaluate which
 of his commits should be applied to master now, and which should wait
 until post-release (if they don't affect wxwidgets).

 I will


 3) is straightforward and I will do

 that this evening. 2) is a bit trickier as I don't really have a good
 understanding of why it is wrong - it uses the same maths as the old
 driver, but I wonder if the aspect ratio code has changed (for fixed
 aspect) and there is some similar change required in the text. As
 issue 4 is a rotated plot I consider this a bit of an edge case for an
 interactive driver - it does need fixing, but I can live with it in
 the short term.

 If you can live with 2 and 4, then we are pretty well ready to go.


 If you can live with them for now, then I can too.  However, I would
 appreciate you figuring out what was wrong with my patch to fix the
 wide legend box issues for the unicode case. At the time, you said you
 were getting complaints from Windows about unicode fonts, but since my
 patch simply used a facility you had already developed to determine
 physical width and height of the string that would be rendered by the
 wxwidgets libraries, I suspect that issue was attributable to other
 Windows issues you were having at that exact same time so please take
 another look.

 I will look - the Unicode issue was related to you setting use of utf8
 fonts which you said matched the wxWidgets example. I have now changed
 (back?) to using default font encoding. I think that Windows font
 files must generally use a different encoding. Note that this does not
 affect the text encoding (which is dealt with on conversion from char
 * to wxString) it only deals with font encodings - although I must
 confess to not fully understanding how font encodings work.

 One question I had though, is there any different behaviour required
 for the no pause state? Currently the driver does not pause at all
 regardless of this state. It sends all its data to the viewer then
 continues - for the examples it then exits as it reaches the end of
 main(), but leaves the viewer open with the plots.


 I think the fundamental issue here is that new wxwidgets launches a
 viewer that runs in a completely detached state.  That can be good in
 certain circumstances, but it obviously goes against the paradigm that
 is used for every other interactive device.  So I believe the solution
 here is to implement a wxwidgets driver option that allows detached
 mode (as now), but by default operates in attached mode. Once attached
 mode works, then that makes it possible to control the plot directly
 from the example, e.g., by specifying the nopause option.  I assume
 attached mode would also allow -locate mode to work for example 1,
 sort out some of the example 17 issues, etc.

 Locate is already possible, I have a flag in the memory map which
 indicates locate mode is on and halts execution of the calling
 program. This should be reusable to pause execution of the calling
 program, but this may have to wait until post release.


 In sum, all of the above are would-be-nices in my opinion rather
 than showstoppers.  So you are free to tackle as few or many of them
 as you like in the next few days, and we should look again where we
 jointly stand near the end of this week.


 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
 __

--
Dive into the 

Re: [Plplot-devel] Release status

2015-03-09 Thread Alan W. Irwin
Hi Phil:

From all your commits last week it appears you are continuing to make
progress on fixing the wxwidgets bugs, but I have no idea how much
more (if anything) you want to do before release.  Also, I rely on you
to evaluate Jim's Saturday patch series to decide which of his commits
should be applied before the release and which should be applied
after.

I am looking forward to that feedback from you so I will be in a
better position to make a meaningful estimate of the release date.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-09 Thread Phil Rosenberg
Hi Alan

 (1) Bad abort operation for the Unkown error which causes
 substantial memory managment issues.
 (2) Error message itself needs a spelling change: Unkown -- Unknown
 (3) regression for -geometry option
 (4) regression of an added surface pattern artifact for example 8


Issue (4) is now solved. Issue (2) I will fix now.

Issue (1)/(3) turned out to be some bad cleanup of a thrown exception
which is a 1 line fix I am about to commit.

However, perhaps more important was why the exception was thrown. It
was an exception I coded in to be thrown when the user set the size of
the canvas, but failed to set the dpi. (On windows I get a rather more
specific error message, not sure why the default unknown error message
is displayed on linux). I guess pragmatically I should use the same
default dpi as if the size hasn't been set, but I thought that if the
user has set the size then the dpi should be also set to ensure
consistency. This however does make the PLStream::pageset variable
rather useless as it gets set whether or not the dpi is valid.

Anyway, there should be a new commit fixing these issues in about 10 mins.

Phil

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-09 Thread Phil Rosenberg
Hi Alan

Here is a status update on wxWidgets, but the headline is that I now
feel that the wxWidgets driver is at an appropriate stage for release.

The issues that still exist are on trello, so you can view them is you
want. However I now think that the new driver is of generally the same
quality as the previous one.

Of the remaining issues the ones that I feel are of highest priority are

1) The preservation of the bop state in the buffer
2) 3d text is not quite correctly aligned.
3) Adding wxStream constuctors that mirror plstream constructors.
4) There are some aspect ratio issues with x03, but only when resized
and only on Linux. I think this is related to the rotated orientation.

My understanding is that Jim is doing 1), but if he is busy with other
stuff I'd be happy to sort that. 3) is straightforward and I will do
that this evening. 2) is a bit trickier as I don't really have a good
understanding of why it is wrong - it uses the same maths as the old
driver, but I wonder if the aspect ratio code has changed (for fixed
aspect) and there is some similar change required in the text. As
issue 4 is a rotated plot I consider this a bit of an edge case for an
interactive driver - it does need fixing, but I can live with it in
the short term.

If you can live with 2 and 4, then we are pretty well ready to go.

One question I had though, is there any different behaviour required
for the no pause state? Currently the driver does not pause at all
regardless of this state. It sends all its data to the viewer then
continues - for the examples it then exits as it reaches the end of
main(), but leaves the viewer open with the plots.

Phil


On 9 March 2015 at 11:37, Phil Rosenberg p.d.rosenb...@gmail.com wrote:
 Hi Alan

 (1) Bad abort operation for the Unkown error which causes
 substantial memory managment issues.
 (2) Error message itself needs a spelling change: Unkown -- Unknown
 (3) regression for -geometry option
 (4) regression of an added surface pattern artifact for example 8


 Issue (4) is now solved. Issue (2) I will fix now.

 Issue (1)/(3) turned out to be some bad cleanup of a thrown exception
 which is a 1 line fix I am about to commit.

 However, perhaps more important was why the exception was thrown. It
 was an exception I coded in to be thrown when the user set the size of
 the canvas, but failed to set the dpi. (On windows I get a rather more
 specific error message, not sure why the default unknown error message
 is displayed on linux). I guess pragmatically I should use the same
 default dpi as if the size hasn't been set, but I thought that if the
 user has set the size then the dpi should be also set to ensure
 consistency. This however does make the PLStream::pageset variable
 rather useless as it gets set whether or not the dpi is valid.

 Anyway, there should be a new commit fixing these issues in about 10 mins.

 Phil

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-09 Thread Phil Rosenberg
On 9 March 2015 at 20:43, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
 Hi Phil:

 One thing I failed to cover in my prior post this morning is it sounds
 like you have one more round of plbuf changes you would like to commit
 to master (probably including some or all commits from Jim's series)
 before release. That is fine, but you should also aim to put plbuf
 changes into a deep freeze (no further changes allowed before release
 except to sort out rendering regressions for all of PLplot) as early
 as possible this week.  In other words, for the wxwidgets issues we
 discussed, if you cannot get the fix done in the next day or so, and
 the fix also involves plbuf changes, you should put off fixing the
 issue until after the release.

I will aim to do that asap

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-09 Thread Phil Rosenberg


 Please take a look at his patch series he sent this weekend.  One of those
 patches
 apparently was to fix a wxwidgets issue so part/all of that series may
 be exactly what you need, but I am leaving it to you to evaluate which
 of his commits should be applied to master now, and which should wait
 until post-release (if they don't affect wxwidgets).

I will


 3) is straightforward and I will do

 that this evening. 2) is a bit trickier as I don't really have a good
 understanding of why it is wrong - it uses the same maths as the old
 driver, but I wonder if the aspect ratio code has changed (for fixed
 aspect) and there is some similar change required in the text. As
 issue 4 is a rotated plot I consider this a bit of an edge case for an
 interactive driver - it does need fixing, but I can live with it in
 the short term.

 If you can live with 2 and 4, then we are pretty well ready to go.


 If you can live with them for now, then I can too.  However, I would
 appreciate you figuring out what was wrong with my patch to fix the
 wide legend box issues for the unicode case. At the time, you said you
 were getting complaints from Windows about unicode fonts, but since my
 patch simply used a facility you had already developed to determine
 physical width and height of the string that would be rendered by the
 wxwidgets libraries, I suspect that issue was attributable to other
 Windows issues you were having at that exact same time so please take
 another look.

I will look - the Unicode issue was related to you setting use of utf8
fonts which you said matched the wxWidgets example. I have now changed
(back?) to using default font encoding. I think that Windows font
files must generally use a different encoding. Note that this does not
affect the text encoding (which is dealt with on conversion from char
* to wxString) it only deals with font encodings - although I must
confess to not fully understanding how font encodings work.

 One question I had though, is there any different behaviour required
 for the no pause state? Currently the driver does not pause at all
 regardless of this state. It sends all its data to the viewer then
 continues - for the examples it then exits as it reaches the end of
 main(), but leaves the viewer open with the plots.


 I think the fundamental issue here is that new wxwidgets launches a
 viewer that runs in a completely detached state.  That can be good in
 certain circumstances, but it obviously goes against the paradigm that
 is used for every other interactive device.  So I believe the solution
 here is to implement a wxwidgets driver option that allows detached
 mode (as now), but by default operates in attached mode. Once attached
 mode works, then that makes it possible to control the plot directly
 from the example, e.g., by specifying the nopause option.  I assume
 attached mode would also allow -locate mode to work for example 1,
 sort out some of the example 17 issues, etc.

Locate is already possible, I have a flag in the memory map which
indicates locate mode is on and halts execution of the calling
program. This should be reusable to pause execution of the calling
program, but this may have to wait until post release.


 In sum, all of the above are would-be-nices in my opinion rather
 than showstoppers.  So you are free to tackle as few or many of them
 as you like in the next few days, and we should look again where we
 jointly stand near the end of this week.


 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
 __

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-09 Thread Alan W. Irwin
On 2015-03-09 12:22- Phil Rosenberg wrote:

 Hi Alan

 Here is a status update on wxWidgets, but the headline is that I now
 feel that the wxWidgets driver is at an appropriate stage for release.

That is excellent news indeed!

I still have lots on my PLplot agenda so the headline from my
perspective is the release date is still not settled, but I
hope to firm up the date late this week.

There are, of course, still a lot of wxwidgets would be nices that
we jointly mention below, but nothing release critical as far as I am
concerned because of the USE_OLD_WXWIDGETS cmake option I discussed
with you (not implemented yet, but I plan to).

For the others here this option will give the users the chance to
choose the old wxwidgets device, associated library, etc., at cmake
time (not run time where there would be a lot of clash issues to sort
out between old and new wxwidgets device). So if one of the issues
below (or some other issue we are unaware of) is a showstopper for
them, we will have provided them a CMake option to go back to using
the old (deprecated) wxwidgets code for at least this release.

More below in context.


 The issues that still exist are on trello, so you can view them is you
 want. However I now think that the new driver is of generally the same
 quality as the previous one.

 Of the remaining issues the ones that I feel are of highest priority are

 1) The preservation of the bop state in the buffer
 2) 3d text is not quite correctly aligned.
 3) Adding wxStream constuctors that mirror plstream constructors.
 4) There are some aspect ratio issues with x03, but only when resized
 and only on Linux. I think this is related to the rotated orientation.

 My understanding is that Jim is doing 1), but if he is busy with other
 stuff I'd be happy to sort that.

Please take a look at his patch series he sent this weekend.  One of those 
patches
apparently was to fix a wxwidgets issue so part/all of that series may
be exactly what you need, but I am leaving it to you to evaluate which
of his commits should be applied to master now, and which should wait
until post-release (if they don't affect wxwidgets).

3) is straightforward and I will do
 that this evening. 2) is a bit trickier as I don't really have a good
 understanding of why it is wrong - it uses the same maths as the old
 driver, but I wonder if the aspect ratio code has changed (for fixed
 aspect) and there is some similar change required in the text. As
 issue 4 is a rotated plot I consider this a bit of an edge case for an
 interactive driver - it does need fixing, but I can live with it in
 the short term.

 If you can live with 2 and 4, then we are pretty well ready to go.

If you can live with them for now, then I can too.  However, I would
appreciate you figuring out what was wrong with my patch to fix the
wide legend box issues for the unicode case. At the time, you said you
were getting complaints from Windows about unicode fonts, but since my
patch simply used a facility you had already developed to determine
physical width and height of the string that would be rendered by the
wxwidgets libraries, I suspect that issue was attributable to other
Windows issues you were having at that exact same time so please take
another look.

 One question I had though, is there any different behaviour required
 for the no pause state? Currently the driver does not pause at all
 regardless of this state. It sends all its data to the viewer then
 continues - for the examples it then exits as it reaches the end of
 main(), but leaves the viewer open with the plots.

I think the fundamental issue here is that new wxwidgets launches a
viewer that runs in a completely detached state.  That can be good in
certain circumstances, but it obviously goes against the paradigm that
is used for every other interactive device.  So I believe the solution
here is to implement a wxwidgets driver option that allows detached
mode (as now), but by default operates in attached mode. Once attached
mode works, then that makes it possible to control the plot directly
from the example, e.g., by specifying the nopause option.  I assume
attached mode would also allow -locate mode to work for example 1,
sort out some of the example 17 issues, etc.

In sum, all of the above are would-be-nices in my opinion rather
than showstoppers.  So you are free to tackle as few or many of them
as you like in the next few days, and we should look again where we
jointly stand near the end of this week.

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);

Re: [Plplot-devel] Release status

2015-03-09 Thread Alan W. Irwin
Hi Phil:

One thing I failed to cover in my prior post this morning is it sounds
like you have one more round of plbuf changes you would like to commit
to master (probably including some or all commits from Jim's series)
before release. That is fine, but you should also aim to put plbuf
changes into a deep freeze (no further changes allowed before release
except to sort out rendering regressions for all of PLplot) as early
as possible this week.  In other words, for the wxwidgets issues we
discussed, if you cannot get the fix done in the next day or so, and
the fix also involves plbuf changes, you should put off fixing the
issue until after the release.

The point of such a deep freeze is that plbuf changes have the
potential to introduce rendering regressions for all of PLplot (not
just wxwidgets) as was demonstrated by Andrew's fix for example 2.02.
Also, the zoom regression for -dev tk may also be another example of
such a plbuf-generated rendering regression, but I should know more
about that once I git bisect that issue.

So to get at least one foot on dry land we want to get to a state
where we _know_ there will be no more plbuf changes (except for PLplot
rendering regression fixes) in this release cycle in the next day or
so.  Once I hear that announcement from you that a deep freeze has
gone into effect for plbuf changes, then I plan to look very carefully
at every page of our examples for any recently introduced rendering
issues for, say, xcairo. But I would not want to do all the work
associated with such a test until I know there will be no further
plbuf changes other than rendering regression fixes.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-04 Thread Alan W. Irwin
Hi Phil:

Your latest commit (f6dcf09703 = Fixed reentrant behaviour in
wxPLViewer...) mostly works.  For example, it builds without
issues, and examples 1 and 4 (the first two run by the
test_c_wxwidgets target) appear to work at run-time with
no obvious issues.  However, example 8 now has a subtle
pattern superimposed on the surface that wasn't there
before (and which is not there for any other device), and example 14
segfaults, i.e.,

software@raven examples/c/x14c -dev wxwidgets

*** PLPLOT ERROR, ABORTING OPERATION ***
Unkown error in plD_init_wxwidgets., aborting operation
Segmentation fault

The valgrind summary for examples 1, 4, and 8 is

ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 6 from 6)

which is good.  But the equivalent result for example 14 is

ERROR SUMMARY: 1586 errors from 50 contexts (suppressed: 6 from 6)

I can give you the full report if you like, but for now I only
give you the first part of that report below since that is probably the
part of the report that you will find of most use for tracking down
the issue.
==23600== Memcheck, a memory error detector
==23600== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==23600== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==23600== Command: examples/c/x14c -dev wxwidgets
==23600==

*** PLPLOT ERROR, ABORTING OPERATION ***
Unkown error in plD_init_wxwidgets., aborting operation
==23600== Invalid read of size 8
==23600==at 0x6E26914: wxPLDevice::BeginPage(PLStream*) 
(wxwidgets_dev.cpp:867)
==23600==by 0x6E22848: plD_bop_wxwidgets(PLStream*) (wxwidgets.cpp:352)
==23600==by 0x4E51FFC: plP_bop (plcore.c:211)
==23600==by 0x4E56EC3: c_plinit (plcore.c:2271)
==23600==by 0x4017B9: main (x14c.c:84)
==23600==  Address 0x6a6aba8 is 8 bytes inside a block of size 1,312 free'd
==23600==at 0x4C279DC: operator delete(void*) (vg_replace_malloc.c:457)
==23600==by 0x6E224BE: plD_init_wxwidgets(PLStream*) (wxwidgets.cpp:174)
==23600==by 0x4E51DEC: plP_init (plcore.c:144)
==23600==by 0x4E56EBE: c_plinit (plcore.c:2270)
==23600==by 0x4017B9: main (x14c.c:84)

Line 84, of course, is the plinit call, and the only difference there
with other examples use of plinit is the use of the geometry option.

Indeed, I get the same issue for example 1 when -geometry is specified
on the command line:

examples/c/x01c -dev xwin -geometry 800x600
PLplot library version: 5.10.0

*** PLPLOT ERROR, ABORTING OPERATION ***
Unkown error in plD_init_wxwidgets., aborting operation
Segmentation fault

In sum there are 4 issues here introduced or exposed by your recent series of
commits.

(1) Bad abort operation for the Unkown error which causes
substantial memory managment issues.
(2) Error message itself needs a spelling change: Unkown -- Unknown
(3) regression for -geometry option
(4) regression of an added surface pattern artifact for example 8

I suspect issues (1) and (2) have been with us since the start of your
new wxwidgets development, and we are just lucky that issue (3)
provides the test case that exposes (1) and (2).  So to make sure that
the fixes for (1) and (2) are correct, I suggest you fix them before fixing
(3).

Also, please don't get too discouraged by these small but annoying
issues we both keep finding. Instead, just keep plugging away at the
fixes no matter how trivial (such as the above spelling fix).

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel


Re: [Plplot-devel] Release status

2015-03-04 Thread Phil Rosenberg
Thanks for the heads up Alan, especially the Valgrind output and the
reproduction method. Very handy!

Regardign the surface pattern artefacts. I had already spotted them
and x08.1 is on the trello page. It appears to be a bad antiaiasing
issue or rounding issue, basically adjacent polygons don't quite fit
next to each other correctly and you are seeing through the gaps. To
be honest right now I don't have a good answer to this.

Regarding the old and new wxWidgets, I think that is an excellent idea.

Phil

On 4 March 2015 at 19:36, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
 Hi Phil:

 Your latest commit (f6dcf09703 = Fixed reentrant behaviour in
 wxPLViewer...) mostly works.  For example, it builds without
 issues, and examples 1 and 4 (the first two run by the
 test_c_wxwidgets target) appear to work at run-time with
 no obvious issues.  However, example 8 now has a subtle
 pattern superimposed on the surface that wasn't there
 before (and which is not there for any other device), and example 14
 segfaults, i.e.,

 software@raven examples/c/x14c -dev wxwidgets

 *** PLPLOT ERROR, ABORTING OPERATION ***
 Unkown error in plD_init_wxwidgets., aborting operation
 Segmentation fault

 The valgrind summary for examples 1, 4, and 8 is

 ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 6 from 6)

 which is good.  But the equivalent result for example 14 is

 ERROR SUMMARY: 1586 errors from 50 contexts (suppressed: 6 from 6)

 I can give you the full report if you like, but for now I only
 give you the first part of that report below since that is probably the
 part of the report that you will find of most use for tracking down
 the issue.
 ==23600== Memcheck, a memory error detector
 ==23600== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
 ==23600== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
 ==23600== Command: examples/c/x14c -dev wxwidgets
 ==23600==

 *** PLPLOT ERROR, ABORTING OPERATION ***
 Unkown error in plD_init_wxwidgets., aborting operation
 ==23600== Invalid read of size 8
 ==23600==at 0x6E26914: wxPLDevice::BeginPage(PLStream*)
 (wxwidgets_dev.cpp:867)
 ==23600==by 0x6E22848: plD_bop_wxwidgets(PLStream*) (wxwidgets.cpp:352)
 ==23600==by 0x4E51FFC: plP_bop (plcore.c:211)
 ==23600==by 0x4E56EC3: c_plinit (plcore.c:2271)
 ==23600==by 0x4017B9: main (x14c.c:84)
 ==23600==  Address 0x6a6aba8 is 8 bytes inside a block of size 1,312 free'd
 ==23600==at 0x4C279DC: operator delete(void*) (vg_replace_malloc.c:457)
 ==23600==by 0x6E224BE: plD_init_wxwidgets(PLStream*) (wxwidgets.cpp:174)
 ==23600==by 0x4E51DEC: plP_init (plcore.c:144)
 ==23600==by 0x4E56EBE: c_plinit (plcore.c:2270)
 ==23600==by 0x4017B9: main (x14c.c:84)

 Line 84, of course, is the plinit call, and the only difference there
 with other examples use of plinit is the use of the geometry option.

 Indeed, I get the same issue for example 1 when -geometry is specified
 on the command line:

 examples/c/x01c -dev xwin -geometry 800x600
 PLplot library version: 5.10.0

 *** PLPLOT ERROR, ABORTING OPERATION ***
 Unkown error in plD_init_wxwidgets., aborting operation
 Segmentation fault

 In sum there are 4 issues here introduced or exposed by your recent series
 of
 commits.

 (1) Bad abort operation for the Unkown error which causes
 substantial memory managment issues.
 (2) Error message itself needs a spelling change: Unkown -- Unknown
 (3) regression for -geometry option
 (4) regression of an added surface pattern artifact for example 8

 I suspect issues (1) and (2) have been with us since the start of your
 new wxwidgets development, and we are just lucky that issue (3)
 provides the test case that exposes (1) and (2).  So to make sure that
 the fixes for (1) and (2) are correct, I suggest you fix them before fixing
 (3).

 Also, please don't get too discouraged by these small but annoying
 issues we both keep finding. Instead, just keep plugging away at the
 fixes no matter how trivial (such as the above spelling fix).


 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
 __

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to

Re: [Plplot-devel] Release status

2015-03-02 Thread Phil Rosenberg
To add to that regarding wxWidgets
The current master branch with wxWidgets still has some issues that I
would not be happy releasing. Most importantly is how we go about
selecting whether to use a user wxDC or use the wxPLViewer. After
Friday's discussion I have added a plsdevdata function which can be
used to pass the dc in. However somehow I appear to have broken
something else and when I tested on Ubuntu I got some very strange
issues when trying to select the wxWidgets device with an error
message that implied that the xwin device was selected instead
followed by some garbage characters.  So I now need to try and ppick
through my commit to work out what has caused this break. The moral
here being commit often then git bisect becomes your friend.

Also Alan I pulled down your character changes and they cause issues
on Windows. I now get a popup error message about fonts not supporting
utf8 encoding.

I'm sorry the description here isn't great. I'm also sorry in advance
that I probably won't be on email most of today as I have a very busy
day ahead. But the take home message unfortunately is that the
wxWidgets driver isn't ready yet.

Phil

On 2 March 2015 at 07:56, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
 To get the ball rolling on the promised Monday discussion of the
 current release status, and what that implies for the release date,
 here is what I have been up to this weekend.

 I decided to comprehensively test PLplot on Linux using the epa_build
 procedure (documented in cmake/epa_build/README) for doing that.  That
 procedure ran into memory management issues for Qt5 that happen
 (according to valgrind) whenever an attempt is made to exit Plplot or
 (curiously) whenever an attempt is made to exit the cursor-mode OK
 button for qt_example.  These memory management issues do not occur at
 all for Qt4 (which likely explains Andrew's reported success with
 preliminary testing of PLplot for this release).  But for Qt5, these
 issues resulted in at least one segfault which motivated the valgrind
 investigation that showed these specific memory management issues. I
 don't think we have changed our exit procedures since the last time I
 tested Qt-5.3.1 this way so I suspect the memory management issues
 were always there, but they only generated a segfault by luck just
 this time.

 I then shifted from epa_building Qt 5.3.1 to 5.4.1, but that version
 of Qt5 would not even compile!  I then shifted to trying 5.3.2, and
 that built without issues, but gave the same memory managment
 valgrind-reported errors for the same specific PLplot situations plus the
 segfault.  At this stage I don't know whether the issue is in Qt5.3.x or
 my epa_build of that software or something else, but what I intend to
 do about this for the rest of this release cycle is simply to avoid
 (with a WARNING) all qt testing in my comprehensive tests when Qt5
 is being used to allow me to complete such comprehensive testing.

 So tomorrow (Monday my time) I will implement that constraint on no
 comprehensive testing of Qt5, and then try the comprehensive test on
 Linux of an epa_built PLplot version again.

 At this stage it is already clear that at mimimum it is going to be
 next weekend (March 7th) for the release date because of everything I
 have to do to finish comprehensive testing and a number of other
 pre-release steps.  Of course, that ETA is still quite uncertain and
 could be even a wekk later.  But I will do another summary of the
 situation late tomorrow (Monday) with results depending on whether I
 can get all the way through a comprehensive test on Linux tomorrow,
 and also depending on reports from Phil and Jim about how their
 plwidgets/plbuf and plmeta/plbuf debugging efforts are proceeding.

 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
 __

 --
 Dive into the World of Parallel Programming The Go Parallel Website, sponsored
 by Intel and developed in partnership with Slashdot Media, is your hub for all
 things parallel software development, from weekly thought leadership blogs to
 news, videos, case studies, tutorials and more. Take a look and join the
 conversation now. http://goparallel.sourceforge.net/
 ___
 Plplot-devel mailing list
 Plplot-devel@lists.sourceforge.net
 

Re: [Plplot-devel] Release status

2015-03-02 Thread Alan W. Irwin
On 2015-03-02 09:33- Phil Rosenberg wrote:

 []But the take home message unfortunately is that the
 wxWidgets driver isn't ready yet.

Hi Phil:

If it is any consolation, my comprehensive testing and other
pre-release items I have to do are in similar shape.  Also, note that
once Jim's new plmeta/plrender is text-simplified along the lines I
discussed with him, it should be a great tool for helping to find the
remaining plbuf issues which should simplify your life.

So for now, the release date target is still quite uncertain, i.e.,
next weekend at the earliest.  However, let's review that again near
the end of this week to see where we stand.

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
__

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel