You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
(14) |
Jun
(1) |
Jul
(3) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(16) |
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(13) |
Feb
(22) |
Mar
(7) |
Apr
(8) |
May
(8) |
Jun
(11) |
Jul
(2) |
Aug
|
Sep
(5) |
Oct
(31) |
Nov
(23) |
Dec
(3) |
2002 |
Jan
(1) |
Feb
(17) |
Mar
(10) |
Apr
(3) |
May
(1) |
Jun
(2) |
Jul
|
Aug
|
Sep
(11) |
Oct
(5) |
Nov
(21) |
Dec
(20) |
2003 |
Jan
(27) |
Feb
(13) |
Mar
(20) |
Apr
(11) |
May
(12) |
Jun
(7) |
Jul
(16) |
Aug
(21) |
Sep
(9) |
Oct
(28) |
Nov
(24) |
Dec
(30) |
2004 |
Jan
(31) |
Feb
(5) |
Mar
|
Apr
(8) |
May
(12) |
Jun
(7) |
Jul
(13) |
Aug
(12) |
Sep
(2) |
Oct
(14) |
Nov
(42) |
Dec
(14) |
2005 |
Jan
|
Feb
|
Mar
(20) |
Apr
(17) |
May
(9) |
Jun
|
Jul
(7) |
Aug
(3) |
Sep
(17) |
Oct
(14) |
Nov
(9) |
Dec
|
2006 |
Jan
|
Feb
|
Mar
(13) |
Apr
(2) |
May
(46) |
Jun
(2) |
Jul
(20) |
Aug
(26) |
Sep
(31) |
Oct
(5) |
Nov
(9) |
Dec
(13) |
2007 |
Jan
(24) |
Feb
(22) |
Mar
(13) |
Apr
(25) |
May
(25) |
Jun
(9) |
Jul
(20) |
Aug
(9) |
Sep
(26) |
Oct
(3) |
Nov
(4) |
Dec
(3) |
2008 |
Jan
(92) |
Feb
(35) |
Mar
(39) |
Apr
(15) |
May
|
Jun
|
Jul
(18) |
Aug
(5) |
Sep
(5) |
Oct
(7) |
Nov
(10) |
Dec
(27) |
2009 |
Jan
(35) |
Feb
(34) |
Mar
(13) |
Apr
(9) |
May
(18) |
Jun
(9) |
Jul
(15) |
Aug
(13) |
Sep
(64) |
Oct
(7) |
Nov
(43) |
Dec
|
2010 |
Jan
(75) |
Feb
(22) |
Mar
(44) |
Apr
(34) |
May
(47) |
Jun
(77) |
Jul
(28) |
Aug
(7) |
Sep
(45) |
Oct
(1) |
Nov
(19) |
Dec
(7) |
2011 |
Jan
(14) |
Feb
|
Mar
(6) |
Apr
(12) |
May
(19) |
Jun
(3) |
Jul
(8) |
Aug
(4) |
Sep
(3) |
Oct
(21) |
Nov
(11) |
Dec
(4) |
2012 |
Jan
(2) |
Feb
(9) |
Mar
|
Apr
(1) |
May
(2) |
Jun
|
Jul
(1) |
Aug
(5) |
Sep
(5) |
Oct
(1) |
Nov
(18) |
Dec
(2) |
2013 |
Jan
(15) |
Feb
(16) |
Mar
(8) |
Apr
(5) |
May
|
Jun
(1) |
Jul
(17) |
Aug
(3) |
Sep
(17) |
Oct
(43) |
Nov
(25) |
Dec
(9) |
2014 |
Jan
(4) |
Feb
(8) |
Mar
(20) |
Apr
(14) |
May
(49) |
Jun
(1) |
Jul
|
Aug
(18) |
Sep
(2) |
Oct
(1) |
Nov
(22) |
Dec
(3) |
2015 |
Jan
(41) |
Feb
(2) |
Mar
(34) |
Apr
(30) |
May
(14) |
Jun
(17) |
Jul
(29) |
Aug
(3) |
Sep
(3) |
Oct
(1) |
Nov
(7) |
Dec
(4) |
2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
(4) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
(25) |
Oct
(9) |
Nov
(14) |
Dec
(13) |
2017 |
Jan
(11) |
Feb
(8) |
Mar
(12) |
Apr
(4) |
May
(25) |
Jun
(2) |
Jul
|
Aug
(5) |
Sep
(10) |
Oct
(25) |
Nov
|
Dec
(6) |
2018 |
Jan
(18) |
Feb
(6) |
Mar
(6) |
Apr
(1) |
May
(7) |
Jun
(13) |
Jul
(8) |
Aug
|
Sep
(5) |
Oct
(2) |
Nov
(17) |
Dec
(3) |
2019 |
Jan
(11) |
Feb
(4) |
Mar
(13) |
Apr
(19) |
May
(1) |
Jun
(2) |
Jul
(8) |
Aug
(4) |
Sep
(32) |
Oct
(51) |
Nov
(1) |
Dec
(9) |
2020 |
Jan
(9) |
Feb
(6) |
Mar
|
Apr
|
May
(3) |
Jun
(2) |
Jul
(5) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(7) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(3) |
Dec
|
2022 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Alan W. I. <ir...@be...> - 2017-03-21 19:00:08
|
Hi Arjen and John: On 2017-03-21 09:58-0000 Arjen Markus wrote: > Hi John, > > Well, a quick search revealed: > > - CMake does not support Silverfrost out-of-the-box, at least I could not find a module for it > - Silverfrost FTN95 is limited to Fortran 95, so it will not support the current binding @Arjen: For the record do you have a reference for that second result? I looked for that myself last night but could not find the definitive statement about what versions of Fortran were supported by FTN95. @John: Arjen has nicely summarized above the two hurdles to overcome before you could use FTN95 (or any other Fortran compiler) to build the PLplot Fortran bindings. One is CMake support for FTN95 and the other is FTN95 support for Fortran 2003. Both of these are the responsibility of Silverfrost so I suggest you contact them to see what they say about their plans in these areas. Meanwhile, I suggest you try a better supported Fortran compiler such as ifort which _we know_ works fine to build the Fortran binding of PLplot. @Everybody here: Our experience is the PLplot Fortran binding and examples work fine with the NAG fortran compiler (nagfor), Intel Fortran compiler (ifort) and the Fortran compiler (gfortran) that is part of the gcc suite of compilers. But has anybody here tried other well-known Fortan compilers such as those from Absoft or the Portland Group? My understanding is CMake supports both the Absoft and Portland Group Fortran compilers so the question really boils down to whether those compilers have the necessary support for Fortran 2003. 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 __________________________ |
From: Alan W. I. <ir...@be...> - 2017-03-21 11:27:28
|
On 2017-03-21 07:01+0100 John AUSTIN wrote: > Hello, > > I've just discovered PLPLOT and am very impressed with the documented > features. > > I am interesed in getting it to work with the Silverfrost FTN95 FORTRAN > compiler and specifially with the CLEARWIN+ GUI capabilities within it , > more specifically within a %gr graphics window. > > Aft e r a quick perusal of the PLPLOT documentation I see:- > > a) for installation via MAKEFILE compilation there are no 'specific' > instructions for SF FTN95 (there are for other compilers) > b) in the section regarding 'output to interactive devices' the situation is > even less clear for a novice like myself in these matters. What is in fact > 'an interactive device' ? > c) in section 1.2.4 (Interactive Platforms) GDI driver compatability is > mentionedand I know FTN95 'supports' this , however I don't know if that in > itself is sufficient to guarantee it will work. > > At the end of the day I guess my question is "Will PLPLOT work in SF FTN95 > 'out of the box' ?" after following the basic install instructions or am I > likely to have some problems ? > Also , will it work for both 32bit and 64bit in FTN95 ? or maybe PLPLOT > needs to be 'compiled' in both for use in each case as necessary ? > > Has anyone had experience with getting it to work with SF FTN95 ? Hi John: I had frankly not heard of that Fortran compiler (which I have now discovered is described in <https://en.wikipedia.org/wiki/Silverfrost_FTN95> and <http://www.silverfrost.com/default.aspx>). And I am uncertain about whether it is going to work because the PLplot build system is completely based on cmake, and google searches for cmake and ftn95 do show a few questions about that combination, but no answers. So since cmake is ubiquitous, I think that means you compiler choice is fairly non-standard. Therefore, I suggest you start small with a simple project to see how far you get. For example, try to follow the directions in cmake/test_fortran/README which configures and builds a simple test project (just a "hello world" library and test executable) using your Fortran compiler of choice (in this case ftn95). Note those directions are focussed on Linux at the moment. But on Windows platforms, I would modify the current cmake -DCMAKE_INSTALL_PREFIX=$(pwd)/install_tree -DBUILD_TEST=ON .. make hello directions to cmake.exe -G "NMake Makefiles" -DCMAKE_INSTALL_PREFIX=$(pwd)/install_tree -DBUILD_TEST=ON .. nmake.exe hello (The cmake -G option allows you to choose a wide variety of CMake generators. In the above case, the chosen generator will configure nmake Makefiles so that the following "nmake.exe hello" command should "just work" on Windows for most Fortran compilers.) However, if with our help you cannot get that simple project to work with ftn95, then one alternative would be to ask on the cmake mailing list for help with ftn95 and cmake. But the answer may be that cmake currently does not support ftn95. In which case I would strongly suggest you try a more standard fortran compiler such as ifort. For example, we know ifort works fine with PLplot (and presumbably also works fine with the above simple project). Good luck, and let us know how it goes with that simple project first. 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 __________________________ |
From: Arjen M. <Arj...@de...> - 2017-03-21 09:58:37
|
Hi John, Well, a quick search revealed: - CMake does not support Silverfrost out-of-the-box, at least I could not find a module for it - Silverfrost FTN95 is limited to Fortran 95, so it will not support the current binding So I conclude that getting PLplot built using Silverfrost FT95 will be a bigger project than "just try", unfortunately. Regards, Arjen From: Arjen Markus [mailto:Arj...@de...] Sent: Tuesday, March 21, 2017 8:56 AM To: John AUSTIN; plp...@li... Subject: Re: [Plplot-general] PLPLOT & Getting It To Work with Silverfrost FTN95 Fortran Hi John, As one of the maintainers of PLplot and in particular the Fortran binding, I would like to try and answer your questions. See below in context. Regards, Arjen From: John AUSTIN [mailto:joh...@wa...] Sent: Tuesday, March 21, 2017 7:01 AM To: plp...@li...<mailto:plp...@li...> Subject: [Plplot-general] PLPLOT & Getting It To Work with Silverfrost FTN95 Fortran Hello, I've just discovered PLPLOT and am very impressed with the documented features. I am interesed in getting it to work with the Silverfrost FTN95 FORTRAN compiler and specifially with the CLEARWIN+ GUI capabilities within it , more specifically within a %gr graphics window. >>AM: It has been a long time since I used that compiler, so I do not remember all the particulars. The current binding is based on the Fortran 2003 features for C-Fortran interfacing. If Silverfrost FTN95 supports these features, then there should be no problem - we have successfully used three unrelated compilers (gfortran, Intel Fortran and NAG Fortran) on various platforms (Linux, Cygwin, MinGW-w64/MSYS2 and bare Windows) to build PLplot. If Silverfrost FTN95 is limited to the Fortran 95 standard, then you would have to use the previous binding, which relies on the C side to solve the "impedance" problem. I hope that is not the case ;), as we do not maintain that anymore. Aft e r a quick perusal of the PLPLOT documentation I see:- a) for installation via MAKEFILE compilation there are no 'specific' instructions for SF FTN95 (there are for other compilers) >>AM: If I remember correctly, Silverfrost FTN95 had a different philosophy for building programs and libraries than via Makefiles. But that does not preclude the use of Makefiles of course, as long as you have a make utility available. The crux however is whether CMake supports that compiler. If not, we would have to create special support for it. Not impossible nor particular difficult, but it is an extra step. The main message is: try running CMake and then "make" (or whatever name the make utility has). If this succeeds, you're in business for at least the first couple of steps. If not, we will need the full report of both steps to see what can be done about it. b) in the section regarding 'output to interactive devices' the situation is even less clear for a novice like myself in these matters. What is in fact 'an interactive device' ? >>AM: PLplot supports devices such as PostScript or PDF, which are basically file-based, that is, they produce a file instead of a window on the screen. The interactive devices do produce a window and you can click on it to get the next page, for instance. c) in section 1.2.4 (Interactive Platforms) GDI driver compatability is mentionedand I know FTN95 'supports' this , however I don't know if that in itself is sufficient to guarantee it will work. >>AM: That is a good question. I cannot reliably answer that one. The devices are supposed to be independent of direct support from the compiler, as they use system libraries. So I suppose it will not be a problem. At the end of the day I guess my question is "Will PLPLOT work in SF FTN95 'out of the box' ?" after following the basic install instructions or am I likely to have some problems ? Also , will it work for both 32bit and 64bit in FTN95 ? or maybe PLPLOT needs to be 'compiled' in both for use in each case as necessary ? >>AM: You need to clarify this requirement: 32bits versus 64bits _data_ - the new binding makes that transparant. In the previous version you had to build two separate versions, one for single-precision data and one for double-precision data. 32bits versus 64bits _applications_ - the OS does not allow the combination of 32bits and 64bits libraries or programs. So if that is what you mean, you will have to build it twice, once for each word size. Has anyone had experience with getting it to work with SF FTN95 ? >>AM: Not to my knowledge. It might be an interesting experiment. That said, the one big unknown in this situation is how PLplot can cooperate with ClearWin and its GUI capabilities. That will depend on the way the event loops may be combined or not. 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. |
From: Arjen M. <Arj...@de...> - 2017-03-21 07:56:26
|
Hi John, As one of the maintainers of PLplot and in particular the Fortran binding, I would like to try and answer your questions. See below in context. Regards, Arjen From: John AUSTIN [mailto:joh...@wa...] Sent: Tuesday, March 21, 2017 7:01 AM To: plp...@li... Subject: [Plplot-general] PLPLOT & Getting It To Work with Silverfrost FTN95 Fortran Hello, I've just discovered PLPLOT and am very impressed with the documented features. I am interesed in getting it to work with the Silverfrost FTN95 FORTRAN compiler and specifially with the CLEARWIN+ GUI capabilities within it , more specifically within a %gr graphics window. >>AM: It has been a long time since I used that compiler, so I do not remember all the particulars. The current binding is based on the Fortran 2003 features for C-Fortran interfacing. If Silverfrost FTN95 supports these features, then there should be no problem - we have successfully used three unrelated compilers (gfortran, Intel Fortran and NAG Fortran) on various platforms (Linux, Cygwin, MinGW-w64/MSYS2 and bare Windows) to build PLplot. If Silverfrost FTN95 is limited to the Fortran 95 standard, then you would have to use the previous binding, which relies on the C side to solve the "impedance" problem. I hope that is not the case ;), as we do not maintain that anymore. Aft e r a quick perusal of the PLPLOT documentation I see:- a) for installation via MAKEFILE compilation there are no 'specific' instructions for SF FTN95 (there are for other compilers) >>AM: If I remember correctly, Silverfrost FTN95 had a different philosophy for building programs and libraries than via Makefiles. But that does not preclude the use of Makefiles of course, as long as you have a make utility available. The crux however is whether CMake supports that compiler. If not, we would have to create special support for it. Not impossible nor particular difficult, but it is an extra step. The main message is: try running CMake and then "make" (or whatever name the make utility has). If this succeeds, you're in business for at least the first couple of steps. If not, we will need the full report of both steps to see what can be done about it. b) in the section regarding 'output to interactive devices' the situation is even less clear for a novice like myself in these matters. What is in fact 'an interactive device' ? >>AM: PLplot supports devices such as PostScript or PDF, which are basically file-based, that is, they produce a file instead of a window on the screen. The interactive devices do produce a window and you can click on it to get the next page, for instance. c) in section 1.2.4 (Interactive Platforms) GDI driver compatability is mentionedand I know FTN95 'supports' this , however I don't know if that in itself is sufficient to guarantee it will work. >>AM: That is a good question. I cannot reliably answer that one. The devices are supposed to be independent of direct support from the compiler, as they use system libraries. So I suppose it will not be a problem. At the end of the day I guess my question is "Will PLPLOT work in SF FTN95 'out of the box' ?" after following the basic install instructions or am I likely to have some problems ? Also , will it work for both 32bit and 64bit in FTN95 ? or maybe PLPLOT needs to be 'compiled' in both for use in each case as necessary ? >>AM: You need to clarify this requirement: 32bits versus 64bits _data_ - the new binding makes that transparant. In the previous version you had to build two separate versions, one for single-precision data and one for double-precision data. 32bits versus 64bits _applications_ - the OS does not allow the combination of 32bits and 64bits libraries or programs. So if that is what you mean, you will have to build it twice, once for each word size. Has anyone had experience with getting it to work with SF FTN95 ? >>AM: Not to my knowledge. It might be an interesting experiment. That said, the one big unknown in this situation is how PLplot can cooperate with ClearWin and its GUI capabilities. That will depend on the way the event loops may be combined or not. 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. |
From: John A. <joh...@wa...> - 2017-03-21 06:01:39
|
Hello, I've just discovered PLPLOT and am very impressed with the documented features. I am interesed in getting it to work with the Silverfrost FTN95 FORTRAN compiler and specifially with the CLEARWIN+ GUI capabilities within it , more specifically within a %gr graphics window. Aft e r a quick perusal of the PLPLOT documentation I see:- a) for installation via MAKEFILE compilation there are no 'specific' instructions for SF FTN95 (there are for other compilers) b) in the section regarding 'output to interactive devices' the situation is even less clear for a novice like myself in these matters. What is in fact 'an interactive device' ? c) in section 1.2.4 (Interactive Platforms) GDI driver compatability is mentionedand I know FTN95 'supports' this , however I don't know if that in itself is sufficient to guarantee it will work. At the end of the day I guess my question is "Will PLPLOT work in SF FTN95 'out of the box' ?" after following the basic install instructions or am I likely to have some problems ? Also , will it work for both 32bit and 64bit in FTN95 ? or maybe PLPLOT needs to be 'compiled' in both for use in each case as necessary ? Has anyone had experience with getting it to work with SF FTN95 ? |
From: Arjen M. <Arj...@de...> - 2017-02-24 15:01:32
|
Hi Peter, > > Hello Alan > I did some testing last night: for each choice of format parameters for > (a) fixed point the Postscript output file was correct ; for (b) floating point output the > Postscript output was wrong. > Has anybody tested my example program for Postscript output files for the data > shown? It would be helpful. > > This morning I tried output to the wingcc device. The output for floating point was > correct. This suggests that the contouring routines are Ok and the problem is > writing the Postscript file. There is still a problem, at least for me! > I import Postscript files into .tex documents. > > I use Plplot.5-12.0 (the most recent version?) . Built with Cmake3.7.2 and > MinGW5.3.0 on Windows 7 Pro 64bit. > Can you use PDF files in Latex? (That is what I do) Not sure if the PDF drivers are capable of correctly representing the exponential, but you have a better chance with that format than with PS (it tends to be limited to a small set of characters) 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. |
From: Peter W. <pet...@nt...> - 2017-02-24 14:57:41
|
On 23/02/2017 18:32, Alan W. Irwin wrote: > On 2017-02-23 12:24-0000 Peter Williams wrote: > >> I need to label my contours with floating point values. However, I seem >> to get strange results. >> I have a simplified example of what occurs in the program below. It >> draws an ellipse with contour value 1.0e10, i.e. x*x/4 + y*y = 1.0e10. >> The contour is good. The label is written as 1.0?#???10 where ? stands >> for a character I cannot recognise in this context. What am I doing >> wrong? > > Hi Peter: > > As a general rule (for everybody here), check with the examples first > to see what they do since > those examples are tested thoroughly before each release. > > In this case examples/c/x09.c is an example of contour labels which do > work, but I notice the data values do not have the huge scale that > yours do (so our testing never tests the exponential option that is > documented in > <http://plplot.sourceforge.net/docbook-manual/plplot-html-5.12.0/pl_setcontlabelformat.html>). > > > As a first step, could you let us know your exact platform and also > build example 9 for yourself to confirm it works fine on that > platform? > > Assuming that does work, then as a second step to make sure all other > aspects of your own simplified testing example are working properly > what happens if you scale your example, (e.g., set the above 1.0e10 > value to something like 1.0) to a non-exponential range, and use > pl_setcontlabelformat( 4, 3 ); like example 9 does? If that also > works (as it should if example 9 works for you), then I would scale > your example to both single-digit positive and negative exponents, and > also explore what happens if you change the parameters of > pl_setcontlabelformat. That is, explore the problem a little to give > us an idea of the conditions (compared to the scale of our example 9) > where you are getting bad labels. Hello Alan I did some testing last night: for each choice of format parameters for (a) fixed point the Postscript output file was correct ; for (b) floating point output the Postscript output was wrong. Has anybody tested my example program for Postscript output files for the data shown? It would be helpful. This morning I tried output to the wingcc device. The output for floating point was correct. This suggests that the contouring routines are Ok and the problem is writing the Postscript file. There is still a problem, at least for me! I import Postscript files into .tex documents. I use Plplot.5-12.0 (the most recent version?) . Built with Cmake3.7.2 and MinGW5.3.0 on Windows 7 Pro 64bit. Any ideas? Best Wishes, Peter Williams |
From: Alan W. I. <ir...@be...> - 2017-02-23 18:32:12
|
On 2017-02-23 12:24-0000 Peter Williams wrote: > I need to label my contours with floating point values. However, I seem > to get strange results. > I have a simplified example of what occurs in the program below. It > draws an ellipse with contour value 1.0e10, i.e. x*x/4 + y*y = 1.0e10. > The contour is good. The label is written as 1.0?#???10 where ? stands > for a character I cannot recognise in this context. What am I doing wrong? Hi Peter: As a general rule (for everybody here), check with the examples first to see what they do since those examples are tested thoroughly before each release. In this case examples/c/x09.c is an example of contour labels which do work, but I notice the data values do not have the huge scale that yours do (so our testing never tests the exponential option that is documented in <http://plplot.sourceforge.net/docbook-manual/plplot-html-5.12.0/pl_setcontlabelformat.html>). As a first step, could you let us know your exact platform and also build example 9 for yourself to confirm it works fine on that platform? Assuming that does work, then as a second step to make sure all other aspects of your own simplified testing example are working properly what happens if you scale your example, (e.g., set the above 1.0e10 value to something like 1.0) to a non-exponential range, and use pl_setcontlabelformat( 4, 3 ); like example 9 does? If that also works (as it should if example 9 works for you), then I would scale your example to both single-digit positive and negative exponents, and also explore what happens if you change the parameters of pl_setcontlabelformat. That is, explore the problem a little to give us an idea of the conditions (compared to the scale of our example 9) where you are getting bad labels. I have just taken a quick look at the contour labelling code in src/plcont.c (which we haven't looked at in years), and its self-documentation says it should be able to handle the case of positive exponents with 4 digits or negative exponents with 3 digits but your results indicate there might be some bug there so your explorations of the problem may help us to find that bug assuming it exists. 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 __________________________ |
From: Jim D. <li...@di...> - 2017-02-23 12:31:09
|
> On Feb 23, 2017, at 7:24 AM, Peter Williams <pet...@nt...> wrote: > > I need to label my contours with floating point values. However, I seem > to get strange results. > I have a simplified example of what occurs in the program below. It > draws an ellipse with contour value 1.0e10, i.e. x*x/4 + y*y = 1.0e10. > The contour is good. The label is written as 1.0?#???10 where ? stands > for a character I cannot recognise in this context. What am I doing wrong? > What is the OS and which version of PLplot are you using? > /* Test of labelling contours by floats */ > #include "plplot.h" > > double xMin,xMax,yMin,yMax,dx,dy; > > double f(double x, double y) > { > return x*x/4 + y*y; > } > > void transform(double i, double j, double *x, double *y, void *psiData) > { > *x = xMin + i*dx; *y = yMin + j*dy; > } > > int main() > { > int i,j,m,n,nLevels= 1; > double x,y,**z; > double pLevels[] = {1.0e10}; > m = 32; n = 16; > xMin = -2.5e5; xMax = 2.5e5; yMin = -1.5e5; yMax =1.5e5; > dx = (xMax-xMin)/m; dy = (yMax-yMin)/n; > plAlloc2dGrid(&z,m+1,n+1); > for(i=0; i <= m; i++) for(j=0; j <= n; j++) > { > transform(i,j,&x,&y,NULL); z[i][j] = f(x,y); > } > plsfnam("Labelling.ps"); plsori(1);plsdev("ps");plinit(); > plenv(xMin,xMax,yMin,yMax,1,0); > pl_setcontlabelformat(1,2); pl_setcontlabelparam(0.01,0.5,0.3,1); > plcont((PLFLT_MATRIX)z,m+1,n+1,1,m,1,n,pLevels,nLevels,transform,NULL); > pllab("x","y","Ellipse"); > plFree2dGrid(z,m+1,n+1); > plend(); > return 1; > } > > -- > Peter Williams > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Plplot-general mailing list > Plp...@li... > https://lists.sourceforge.net/lists/listinfo/plplot-general |
From: Peter W. <pet...@nt...> - 2017-02-23 12:30:15
|
Sorry, I should have attached a graphic to my previous enquiry on labelling problems using floats -- Peter Williams |
From: Peter W. <pet...@nt...> - 2017-02-23 12:24:54
|
I need to label my contours with floating point values. However, I seem to get strange results. I have a simplified example of what occurs in the program below. It draws an ellipse with contour value 1.0e10, i.e. x*x/4 + y*y = 1.0e10. The contour is good. The label is written as 1.0?#???10 where ? stands for a character I cannot recognise in this context. What am I doing wrong? /* Test of labelling contours by floats */ #include "plplot.h" double xMin,xMax,yMin,yMax,dx,dy; double f(double x, double y) { return x*x/4 + y*y; } void transform(double i, double j, double *x, double *y, void *psiData) { *x = xMin + i*dx; *y = yMin + j*dy; } int main() { int i,j,m,n,nLevels= 1; double x,y,**z; double pLevels[] = {1.0e10}; m = 32; n = 16; xMin = -2.5e5; xMax = 2.5e5; yMin = -1.5e5; yMax =1.5e5; dx = (xMax-xMin)/m; dy = (yMax-yMin)/n; plAlloc2dGrid(&z,m+1,n+1); for(i=0; i <= m; i++) for(j=0; j <= n; j++) { transform(i,j,&x,&y,NULL); z[i][j] = f(x,y); } plsfnam("Labelling.ps"); plsori(1);plsdev("ps");plinit(); plenv(xMin,xMax,yMin,yMax,1,0); pl_setcontlabelformat(1,2); pl_setcontlabelparam(0.01,0.5,0.3,1); plcont((PLFLT_MATRIX)z,m+1,n+1,1,m,1,n,pLevels,nLevels,transform,NULL); pllab("x","y","Ellipse"); plFree2dGrid(z,m+1,n+1); plend(); return 1; } -- Peter Williams |
From: Alan W. I. <ir...@be...> - 2017-02-08 02:54:57
|
On 2017-02-07 14:31-0800 John Baumgardner wrote: > Hi Alan, > > Thanks for your quick reply and your explanation that the Fortran binding > drops the redundant dimension argument. After I sent my email to you I > recalled that I was getting color using the wingcc plotting option, one that > does not open an X-window. I realized that was an important clue as to what > was awry. My hardware was new, and I checked and I did not have a good > .xinitrc file. When I fixed that, I got good color with PLPLOT. So the issue > is resolved. Thanks again for your responsiveness and help. You are welcome, and good plotting! 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 __________________________ |
From: Alan W. I. <ir...@be...> - 2017-02-07 07:32:56
|
On 2017-02-06 20:39-0800 John Baumgardner wrote: > Dear Alan, > > Today I downloaded and installed version 5.12.0 on my Windows 10 machine > under Cygwin. It installed with no glitches whatever. However, when I > recompiled and ran my graphics program, some of the plots had no color. I > got the following runtime warning: > Plplot Fortran Warning: plscmap1la: inconsistent sizes for intensity, coord1, > coord2, coord3, alpha, and/or alt_hue_path > which tipped me off that there was likely a problem with how I was calling > plscmap1la, which loads the color map. In checking the PLPLOT documentation > for version 5.12.0, I noticed that there was a new argument,/npts/, that had > not been present in the earlier version I had been using. I then checked the > example program in examples/f95, x30f.f90, and noticed that the call there to > plscmap1la surprisingly lacked that new argument /npts/. When I added that > argument in my program, I found that my program would not compile properly > with /npts/ present. I then found the cause of the earlier warning message. > It was that the dimension of the final argument, alt_hue_path, was incorrect. > When I fixed that problem and left out the /npts/ argument, the program > compiled with no complaints, the earlier warning message went away, but the > plots still had no color. It is my suspicion that somehow in the 5.12.0 > there is something wrong with routine plscmap1la and that it has to do with > that new argument. > > Would you mind checking this out for me? Hi John: I hope you don't mind I put your question and my response on the list because I think other Fortran users will be interested. Yes, the new Fortran binding (as we mentioned in the release notes) is now much more careful about the consistency of array sizes passed in a given call to one of the subroutines/functions in our Fortran API. Also, to be specific, plscmap1la is documented at <http://plplot.sourceforge.net/docbook-manual/plplot-html-5.12.0/plscmap1la.html>, but you should be aware that our Fortran binding (in fact all our supported languages other than C and C++) uses the redacted form of our API where redundant dimension arguments (for those languages since that same dimension information is carried in the arrays themselves) are dropped. In this case, the npts argument is one of those redacted arguments as can be seen from near the end of the above webpage where the redacted form of the plscmap1la is documented (with npts dropped). So it sounds to me like you are doing everything right (using the redacted API with consistent dimension information now for each of the array arguments to this routine). Yet you are still not getting any color. To pursue that issue further, could you please try building and running Fortran standard example 30 (which works well for me on Debian Jessie) on your Cygwin platform? To do that, use the -DBUILD_TEST=ON option for cmake, and build Fortran example 30 (and all its prerequisites) as follows: make x30f95 Also, build your favorite Cygwin PLplot device driver (I am going to assume that is svg). make svg Then run the example (in the build tree) using that device examples/f95/x30f -dev svg -o test.svg Then view that test.svg result with an svg viewer. (If you don't have such a specific svg viewer, your browser normally should be able to view svg images). If those results look good (i.e., have color), then you should try to see in what way your application differs from examples/f95/x30.f90 in the source tree. I hope these suggestions help you to find a quick solution to the no-color issue you have encountered with plplot-5.12.0. 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 __________________________ |
From: Alan W. I. <ir...@be...> - 2017-01-29 20:33:51
|
On behalf of all the PLplot developers I am happy to announce a new release of PLplot is now available. We have put a substantial amount of effort into this release (some 400 commits) so downloading it and building it is highly recommended. For all the details concerning this release please follow the links given in <https://sourceforge.net/p/plplot/news/2017/01/plplot-5120-has-been-released/>. Note that the release notes linked there are especially important because they give details concerning backwards incompatibilities (an unfortunate necessity to support our on-going but slow battle against cruft) and concerning the following highlights of this release: Bug fixes Rewrite the CMake Ada language support Rewrite the Fortran binding Supply old Fortran binding and examples option Backwards incompatibilities introduced by the new Fortran binding Examples reworked for the -DPL_DOUBLE=OFF case Changes to our Ada bindings and examples Changes to our tclmatrix library Backwards-incompatible changes to our Tcl/Tk bindings and examples Substantial rewrite of the DocBook documentation Default page size consistency Updated D language support Modernized build-system support for Qt4 and Qt5 Implemented support for pyqt5 Addressed -DPL_DOUBLE=OFF issues Replaced "Lena" with "Chloe" Removed trailing blanks on most text files in our source tree Make our wxwidgets find module consistent with the official version for CMake-3.7.1 Introduction of two new generic pointer types to help protect against a planned future C API breakage Introduction of additional self-describing names for the types of arguments used in our C API Implement submission of dashboards to the <my.cdash.org> cdash server Substantial update and rename of the Python examples Linux efficiency improvements for the wxwidgets device driver Enjoy this new version of PLplot! 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 __________________________ |
From: Andrew M. <ve...@gm...> - 2017-01-16 13:35:56
|
2017-01-16 14:23 GMT+01:00 Jim Dishaw <ji...@di...>: > > On Jan 16, 2017, at 6:17 AM, Andrew Meir <ve...@gm...> > > 2017-01-16 11:51 GMT+01:00 Arjen Markus <Arj...@de...>: >> >> >> >> These libraries ought to be part of the system – on my system they are >> part of “MicroSoft SDKs” or “MicroSoft Kits” (residing in the Program Files >> directories). Maybe these are missing from your system? >> > > Thanks Arjen. Yes, on my system here I can see lots of entries in Program > Files (x86)/Microsoft SDKs, including Program Files (x86)/Microsoft > SDKs/Windows/v7.1A/Lib/x64/Gdi32.Lib > > I'm guessing that something is miss-detecting their presence. Is there > some way of checking/dumping the include and library search paths during > cmake? > > What compiler are you using on Windows? > I'm using MSVC 14.10.24728. It ships with VS 2017 RC Community Edition. > If you are interested, I can send you the other windows driver to try. > Yes please! If it helps you any, I can certainly try building it here and let you know how things go. I'm also exploring wxWidgets and it's less top-heavy than I'd first imagined. Perhaps wxWidgets is what I'll settle on. However, and if not, I'd like a back-up plan and your driver may be just the thing. Thanks again - awesome support :-). Andy |
From: Andrew M. <ve...@gm...> - 2017-01-16 11:17:28
|
2017-01-16 11:51 GMT+01:00 Arjen Markus <Arj...@de...>: > > > > These libraries ought to be part of the system – on my system they are > part of “MicroSoft SDKs” or “MicroSoft Kits” (residing in the Program Files > directories). Maybe these are missing from your system? > Thanks Arjen. Yes, on my system here I can see lots of entries in Program Files (x86)/Microsoft SDKs, including Program Files (x86)/Microsoft SDKs/Windows/v7.1A/Lib/x64/Gdi32.Lib I'm guessing that something is miss-detecting their presence. Is there some way of checking/dumping the include and library search paths during cmake? |
From: Arjen M. <Arj...@de...> - 2017-01-16 10:51:48
|
Hi Andrew, These libraries ought to be part of the system - on my system they are part of "MicroSoft SDKs" or "MicroSoft Kits" (residing in the Program Files directories). Maybe these are missing from your system? Regards, Arjen From: Andrew Meir [mailto:ve...@gm...] Sent: Monday, January 16, 2017 11:32 AM To: Jim Dishaw Cc: plp...@li... Subject: Re: [Plplot-general] Available output devices on Windows The wingcc driver should build in Visual Studio. I have been working on a new Windows driver, but have not had the time to move it past the advanced beta stage. If the wingcc does not build for you, let me know and I can push the alternative windows driver after the freeze is over. Thanks for the clues Jim. I did try forcing wingcc, via the addition of "-DPLD_wingcc=on" to cmake's args but all I see in the cmake output is: Looking for gdi32 header and library - not found WARNING: Setting PLD_wingcc to OFF. Presumably the build needs some additional encouragement to locate the gdi32 headers and lib files but I don't know what this may entail. Otherwise perhaps your new driver is the way to go. I've also been considering wxWidgets but it seems a little top-heavy for what I actually require. 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. |
From: Andrew M. <ve...@gm...> - 2017-01-16 10:32:34
|
> > > The wingcc driver should build in Visual Studio. I have been working on a > new Windows driver, but have not had the time to move it past the advanced > beta stage. If the wingcc does not build for you, let me know and I can > push the alternative windows driver after the freeze is over. > Thanks for the clues Jim. I did try forcing wingcc, via the addition of "-DPLD_wingcc=on" to cmake's args but all I see in the cmake output is: Looking for gdi32 header and library - not found WARNING: Setting PLD_wingcc to OFF. Presumably the build needs some additional encouragement to locate the gdi32 headers and lib files but I don't know what this may entail. Otherwise perhaps your new driver is the way to go. I've also been considering wxWidgets but it seems a little top-heavy for what I actually require. |
From: Andrew M. <ve...@gm...> - 2017-01-14 08:56:49
|
Hello plplot community, I'm a plplot newbie. I have a question regarding the available output devices available in Windows. I've built plplot 5.11.1 for a multi-platform application (Windows 7/CentOS 7). My requirements are fairly simple - to display some test data in a separate viewing window. The guts of the plotter calls are: pls = new plstream(); #ifdef BUILD_LINUX plsdev("xwin"); #else #ifndef _MSC_VER plsdev("wingcc"); #else //Hmm, now what should this be #endif #endif plspause(false); pls->init(); pls->env(0,1000, 0, ymax, 0, 0); pls->lab( "Something", "Frequency", "Something Histogram"); pls->bin(n, datax, datay, opt); As you can see, I'm hedging my bets with the output device, depending on the host OS and environment. I'm trying to support both Cygwin and VS builds on Windows and standard gcc on Linux. However, I can't seem to find a plplot device that will display a pop-up histogram window with Visual Studio/Windows. Is this possible? Is there some wingcc equivalent in VS? Thanks for listening. Andrew |
From: Alan W. I. <ir...@be...> - 2017-01-12 18:57:26
|
On 2017-01-12 16:21-0000 Phil Rosenberg wrote: > Regarding the docbook documentation. I would like to update the > wxWidgets documentation too, but don't want to generate any nightmare > merge issues by working on a file that you are making major changes > to. > > Do you think it is worth me waiting until you have finished and > commited your changes before making mine? Hi Phil: I have just committed all my current set of documentation changes. I still hope to make some more documentation changes in the next day or two. However, I have no plans for further changes in the wxwidgets-relevant sections so you should just feel free to go ahead with your own work on those. 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 __________________________ |
From: Phil R. <p.d...@gm...> - 2017-01-12 16:21:11
|
Hi Alan I have just emailed about the last fix I was working on - please see that thread. Regarding the docbook documentation. I would like to update the wxWidgets documentation too, but don't want to generate any nightmare merge issues by working on a file that you are making major changes to. Do you think it is worth me waiting until you have finished and commited your changes before making mine? Phil On 11 January 2017 at 19:00, Alan W. Irwin <ir...@be...> wrote: > On 2017-01-05 12:37-0800 Alan W. Irwin wrote: > >> The current status is the wxwidgets-related release-critical issues >> have just been fixed (actually as of this morning), but there is still >> one more wxwidgets fix that is still being worked on. Once that fix is >> finalized, we will make the decision whether to push it for this >> release or wait until post-release depending on the intrusiveness of >> the fix (i.e., how many components of PLplot will need retesting after >> the fix is pushed). > >> [...] But we will know a >> lot more by early next week, and I am hoping for the actual release to >> occur during that week. > > The current status is this uncertainty about the last wxwidgets fix > still continues. However, while waiting for another developer to > complete that work I have been spending a lot of my time on my project > to substantially update our ~200 pages of DocBook-generated > documentation, and there are lots of encouraging signs that I am close > to the end of that effort. So with some luck it is still possible we > will get the release done this week, but stay tuned to see how this > goes. > > 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 > __________________________ > > ------------------------------------------------------------------------------ > Developer Access Program for Intel Xeon Phi Processors > Access to Intel Xeon Phi processor-based developer platforms. > With one year of Intel Parallel Studio XE. > Training and support from Colfax. > Order your platform today. http://sdm.link/xeonphi > _______________________________________________ > Plplot-general mailing list > Plp...@li... > https://lists.sourceforge.net/lists/listinfo/plplot-general |
From: Alan W. I. <ir...@be...> - 2017-01-11 19:00:49
|
On 2017-01-05 12:37-0800 Alan W. Irwin wrote: > The current status is the wxwidgets-related release-critical issues > have just been fixed (actually as of this morning), but there is still > one more wxwidgets fix that is still being worked on. Once that fix is > finalized, we will make the decision whether to push it for this > release or wait until post-release depending on the intrusiveness of > the fix (i.e., how many components of PLplot will need retesting after > the fix is pushed). > [...] But we will know a > lot more by early next week, and I am hoping for the actual release to > occur during that week. The current status is this uncertainty about the last wxwidgets fix still continues. However, while waiting for another developer to complete that work I have been spending a lot of my time on my project to substantially update our ~200 pages of DocBook-generated documentation, and there are lots of encouraging signs that I am close to the end of that effort. So with some luck it is still possible we will get the release done this week, but stay tuned to see how this goes. 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 __________________________ |
From: Alan W. I. <ir...@be...> - 2017-01-05 20:37:43
|
On 2017-01-05 10:51-0700 Orion Poplawski wrote: > On 12/27/2016 07:02 PM, Alan W. Irwin wrote: >> On 2016-12-24 14:54-0800 Alan W. Irwin wrote: >> >>> So on the 27th we will see where we stand for the release and make a >>> new estimate of its ETA then. >> >> Currently, we have no generally accepted fix for a wxwidgets-related >> release-critical issue so I have decided to put the release of 5.12.0 >> on indefinite hold until we have a rock-solid fix. The PLplot >> developer who has the most knowledge of our wxwidgets-related software >> has several ideas for implementing the needed fix. So that is a big >> relief. However, he will only be able to start working on this in >> January so this hold is obviously going to be in effect for a while. >> >> Alan > > I'm wondering if it is time to bump the plplot version numbers in git. I'm > facing a situation in Fedora Rawhide where plplot currently fails to build > due the update to octave 4.2 (and perhaps other changes). As a result I'm > leaning towards packaging up a git snapshot - but the git version numbers are > still 5.11.1, and I figure we're a lot closer to 5.12.0 at this point. > > The other concern though would be whether or not all needed soversion bumps > have been made at this point. I haven't run the changes through any tools, > but I don't see any version changes, just the dropping of libplplotf95c. Hi Orion: I would advise you wait for 5.12.0 which might be as soon as next week. Is that possible or are you up against a Fedora freeze deadline? The current status is the wxwidgets-related release-critical issues have just been fixed (actually as of this morning), but there is still one more wxwidgets fix that is still being worked on. Once that fix is finalized, we will make the decision whether to push it for this release or wait until post-release depending on the intrusiveness of the fix (i.e., how many components of PLplot will need retesting after the fix is pushed). So the current release status is still on hold, but there are some excellent signs that the wxwidgets code changes will be finalized shortly (if that has not already occurred) and at that point I will start up the release process again (including bumping all (so)version- related information). Note part of that release process will be finishing an extensive update to our documentation (including as a "would be nice" a complete upgrade to our wxwidgets documentation that is consistent with all the changes done for that component of PLplot in this release cycle) so the actual release ETA will still be uncertain after the wxwidgets code changes have been finalized for this release. But we will know a lot more by early next week, and I am hoping for the actual release to occur during that 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 __________________________ |
From: Orion P. <or...@co...> - 2017-01-05 17:51:22
|
On 12/27/2016 07:02 PM, Alan W. Irwin wrote: > On 2016-12-24 14:54-0800 Alan W. Irwin wrote: > >> So on the 27th we will see where we stand for the release and make a >> new estimate of its ETA then. > > Currently, we have no generally accepted fix for a wxwidgets-related > release-critical issue so I have decided to put the release of 5.12.0 > on indefinite hold until we have a rock-solid fix. The PLplot > developer who has the most knowledge of our wxwidgets-related software > has several ideas for implementing the needed fix. So that is a big > relief. However, he will only be able to start working on this in > January so this hold is obviously going to be in effect for a while. > > Alan I'm wondering if it is time to bump the plplot version numbers in git. I'm facing a situation in Fedora Rawhide where plplot currently fails to build due the update to octave 4.2 (and perhaps other changes). As a result I'm leaning towards packaging up a git snapshot - but the git version numbers are still 5.11.1, and I figure we're a lot closer to 5.12.0 at this point. The other concern though would be whether or not all needed soversion bumps have been made at this point. I haven't run the changes through any tools, but I don't see any version changes, just the dropping of libplplotf95c. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane or...@co... Boulder, CO 80301 http://www.cora.nwra.com |
From: Alan W. I. <ir...@be...> - 2016-12-28 02:03:05
|
On 2016-12-24 14:54-0800 Alan W. Irwin wrote: > So on the 27th we will see where we stand for the release and make a > new estimate of its ETA then. Currently, we have no generally accepted fix for a wxwidgets-related release-critical issue so I have decided to put the release of 5.12.0 on indefinite hold until we have a rock-solid fix. The PLplot developer who has the most knowledge of our wxwidgets-related software has several ideas for implementing the needed fix. So that is a big relief. However, he will only be able to start working on this in January so this hold is obviously going to be in effect for a while. 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 __________________________ |