Thanks for your hints,
but I don't understand the question concerning the copyright, because it's GNU 
software.
What is your strategy when you improve JWE and others developers code?
Do you simple add your name ?
I guess my policy is the same of Michael Creel ,JWE and the author of MPITB for 
octave.
Am i right? Is it clear from the Octave forge contribution?
Thanks a lot
Riccardo Corradini
--- Ven 20/11/09, Jaroslav Hajek <high...@gmail.com> ha scritto:

Da: Jaroslav Hajek <high...@gmail.com>
Oggetto: Re: [OctDev] Contribution to Octave-forge with a simple Open-MPI  
Package
A: "Riccardo Corradini" <riccardocorrad...@yahoo.it>
Cc: "Søren Hauberg" <so...@hauberg.org>, octave-dev@lists.sourceforge.net
Data: Venerdì 20 novembre 2009, 12:46



On Thu, Nov 19, 2009 at 10:13 PM, Jaroslav Hajek <high...@gmail.com> wrote:



On Mon, Nov 16, 2009 at 4:48 PM, Riccardo Corradini 
<riccardocorrad...@yahoo.it> wrote:




Dear Jaroslav,
I have just uploaded into octave-forge extra the openmpi_ext folder containing 
all the files
I sent you introducing the MPI toolbox that uses MPI Derived datatypes to send 
and receive almost any octave_value.


Please let me know about your suggestions or if there is something really wrong.
Thanks a lot to all of you for all your patience.
Bests
Riccardo Corradini


Hi Riccardo,

thanks for the info. I'll have a look as soon as I have time.

regards

Excellent. I think I just made it work under Intel's C++ and MPI on an AMD 
cluster.

I have a few comments/questions:

1. info is the first output argument in all functions. I think it should be the 
second one, so that it can be easily ignored if wanted.
In particular, the check in examples


if not(MPI_Initialized)
   info = MPI_Init();
end

makes no sense (unless I'm missing something) because it's the info output from 
MPI_Initialized that is tested and that is always zero.

2. include "mpi.h" should precede include "oct.h" everywhere, because oct.h 
takes some system headers in. Some MPI libs require this (Intel's MPI does).


3. what's your copyright policy? If I improve some of your functions, can I 
retain the copyright?

thx and best regards
it seems this will be a viable (less convenient but more powerful) alternative 
to parcellfun/pararrayfun for me.


-- 
RNDr. Jaroslav Hajek
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz





      
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev

Reply via email to