Re: [Plplot-devel] Continuous Integration

2016-11-22 Thread Arjen Markus 
Hi Hazen,



Gfortran 4.8.0 was released in march 2013, the last version of that series was 
4.8.5, released in june 2015. The current development version is 7.x. Version 5 
has seen four releases since the first one in april 2015. While I can imagine 
there are problems with the new binding if you use this rather old version of 
gfortran, note that we have been testing this with three unrelated compilers 
(gfortran 5.x, Intel Fortran 15 and NAG Fortran). I may actually be able to 
test it with a fourth one, Oracle Fortran, before the freeze date. So I am 
pretty sure that a recent enough version of any Fortran compiler will be 
useable.

Nevertheless, do you have an error report for gfortran 4.8? We have seen a few 
issues when we started on this, but I do not remember whether they were serious 
and with the newer version they have disappeared. (The NAG compiler is rather 
picky about not following the standard ;)).

Regards,

Arjen



> -Original Message-
> From: Hazen Babcock [mailto:hbabc...@mac.com]
> Sent: Wednesday, November 23, 2016 5:07 AM
> To: Tom Schoonjans
> Cc: PLplot development list
> Subject: Re: [Plplot-devel] Continuous Integration
>
>
> On 11/20/2016 01:12 PM, Tom Schoonjans wrote:
> > That's exactly how I do it though: trial and error :-)
>
> I think I have at least sort of figured out travis-vi. To make it easier I've 
> been doing
> all the experiments on a personal copy of the PLplot repo. It is pretty cool 
> to be able
> to build 5 different versions at the same time :).
>
> If anyone is interested, you can see the results of all the tests here:
> https://travis-ci.org/HazenBabcock/PLplot/builds
>
> So far I have learned the new fortran95 bindings fail with gfortran4.8 (and
> presumably lower). I also had trouble with ada, wxwidgets, lua and ocaml, but 
> I'm
> not sure whether these are dependency issues.
>
> -Hazen
>
>
> --
> ___
> Plplot-devel mailing list
> Plplot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/plplot-devel

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

Re: [Plplot-devel] Continuous Integration

2016-11-22 Thread Hazen Babcock 

On 11/20/2016 01:12 PM, Tom Schoonjans wrote:
> That’s exactly how I do it though: trial and error :-)

I think I have at least sort of figured out travis-vi. To make it easier 
I've been doing all the experiments on a personal copy of the PLplot 
repo. It is pretty cool to be able to build 5 different versions at the 
same time :).

If anyone is interested, you can see the results of all the tests here:
https://travis-ci.org/HazenBabcock/PLplot/builds

So far I have learned the new fortran95 bindings fail with gfortran4.8 
(and presumably lower). I also had trouble with ada, wxwidgets, lua and 
ocaml, but I'm not sure whether these are dependency issues.

-Hazen


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

Re: [Plplot-devel] Soft freeze on December 3rd and release on December17th?

2016-11-22 Thread Pedro Vicente 
Hi Alan
Those dates look good to me, and I will investigate my 3 thread issues 
(wxWidgets, Qt, error messages ) well before the freezing date
-Pedro

- Original Message - 
From: "Alan W. Irwin" 
To: "PLplot development list" 
Sent: Tuesday, November 22, 2016 7:50 PM
Subject: [Plplot-devel] Soft freeze on December 3rd and release on 
December17th?


> Tom Schoonjans made some good points on plplot-general about
> officially releasing timely fixes for PLplot rather than expecting
> packagers and others to dig those out of git, and I also feel it is
> critical to give our users good access to the recent big improvements
> in both our Fortran and Tcl bindings.  So to answer these concerns my
> plan is to release PLplot-5.12.0 on ** December 17th **.
> That is roughly the last release date possible in December without
> intruding on Christmas holiday time, and I don't want to put off this
> release until January for the above reasons.
>
> Note, I don't want the release any sooner than the above date because
> there are a lot of (fairly minor) topics I am still working on that I
> would like to get into this release.  Therefore, I plan to continue
> working on those topics for the rest of this week and the next one and
> declare a soft freeze (where only minor bug fixing and documentation
> improvements should occur after that freeze date until the release) on
> ** December 3rd **. That freeze date should give us
> two weeks for extensive testing of PLplot (and fixing all bugs that
> are turned up by such testing) on all platforms accessible to PLplot
> developers and users.  (Note, I do plan to ask our users on
> plplot-general to help with testing during those two critical weeks on
> the platforms accessible to them.)
>
> Please speak out if either of the two dates above need an adjustment
> from your perspective.  For example, another freeze date alternative
> could be December 10th (which still gives us the minimum one week of
> time we need for testing).  But that freeze date would be completely
> inflexible, and I would prefer a more flexible freeze date (to
> accommodate last-minute requests to change it for those developers who
> discover they need a few more days to get their topics merged) which
> is why I have suggested December 3rd as the freeze date.
>
> If nobody has any suggestions for changes in the above two critical
> dates by (say) late Wednesday I will follow up by announcing the above
> two critical dates on PLplot-general.
>
> Alan (your friendly release manager).
> __
> 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
> 


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

[Plplot-devel] Soft freeze on December 3rd and release on December 17th?

2016-11-22 Thread Alan W. Irwin 
Tom Schoonjans made some good points on plplot-general about
officially releasing timely fixes for PLplot rather than expecting
packagers and others to dig those out of git, and I also feel it is
critical to give our users good access to the recent big improvements
in both our Fortran and Tcl bindings.  So to answer these concerns my
plan is to release PLplot-5.12.0 on ** December 17th **.
That is roughly the last release date possible in December without
intruding on Christmas holiday time, and I don't want to put off this
release until January for the above reasons.

Note, I don't want the release any sooner than the above date because
there are a lot of (fairly minor) topics I am still working on that I
would like to get into this release.  Therefore, I plan to continue
working on those topics for the rest of this week and the next one and
declare a soft freeze (where only minor bug fixing and documentation
improvements should occur after that freeze date until the release) on
** December 3rd **. That freeze date should give us
two weeks for extensive testing of PLplot (and fixing all bugs that
are turned up by such testing) on all platforms accessible to PLplot
developers and users.  (Note, I do plan to ask our users on
plplot-general to help with testing during those two critical weeks on
the platforms accessible to them.)

Please speak out if either of the two dates above need an adjustment
from your perspective.  For example, another freeze date alternative
could be December 10th (which still gives us the minimum one week of
time we need for testing).  But that freeze date would be completely
inflexible, and I would prefer a more flexible freeze date (to
accommodate last-minute requests to change it for those developers who
discover they need a few more days to get their topics merged) which
is why I have suggested December 3rd as the freeze date.

If nobody has any suggestions for changes in the above two critical
dates by (say) late Wednesday I will follow up by announcing the above
two critical dates on PLplot-general.

Alan (your friendly release manager).
__
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] The wxwidgets device driver speed/idle time

2016-11-22 Thread Phil Rosenberg 
Hi Alan
It's on my list - I will do it as soon as I can :-). I actually think
I had a similar system like this set up - although I think I used
named semaphores. I would have to go back to the code to check.

Phil

On 19 November 2016 at 07:39, Alan W. Irwin  wrote:
> Hi Phil:
>
> I got tired of speculating about more efficient Linux IPC methods so I
> implemented (as of commit e166866) the "Unnamed semaphores example"
> paradigm outlined starting on page 73 of
> . (I
> discussed this possibility in earlier versions of this thread.)
> This test project is described in cmake/test_linux_ipc/README.  Follow
> the directions there to test it on your own Linux systems.
>
> My tests show this method is quite efficient for transferring data
> between processes on POSIX-compliant systems.  The transfer process is
> under complete control of unnamed semaphores that reside in the shared
> memory so coordinating required data transfer between two applications
> is completely straightforward, and there is very little idle time
> required during these transfers.
>
> The IPC-relevant routines that are called in this test project are
> shm_open, ftruncate, mmap, sem_init, sem_wait, sem_post, and
> shm_unlink, and according to the Linux man pages, all of these
> functions are provided by platforms that are compliant with POSIX.1-2001.
>
> So on the present evidence from this test project I think this method
> looks extremely promising for efficiently transferring data both ways
> between -dev wxwidgets and wxPLViewer for POSIX-compliant systems.
>
> If after trying the test of the method documented in
> cmake/test_linux_ipc/README you agree with this assessment, would you
> be willing to have a go at the required wxwidgets and wxPLViewer
> source code changes to see if that essentially eliminates the
> large idle times we have now on Linux?
>
>
> 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