Ganglia might help:
http://ganglia.sourceforge.net/
Could be too high-level though.
Damien
On 2015-03-17 8:59 AM, Ralph Castain wrote:
Not at the moment - at least, not integrated into OMPI at this time.
We used to have sensors for such purposes in the OMPI code itself, but
they weren’t
if it doesn't use
that 100% wisely, which is a whole other flame war) and hyperthreading
doesn't help you.
Damien
On 2015-04-10 2:22 PM, namu patel wrote:
Hello All,
I am using OpenMPI 1.8.4 on my workstation with 2 CPUs, each with 12
processors (6 with hyper-threading). When I run simulations using
Walt,
I don't remember seeing a response to this. OpenMPI isn't supported on
native Windows anymore. The last version for Windows was the 1.6 series.
Damien
On 2015-05-11 3:07 PM, Walt Brainerd wrote:
Is it possible to build OpenMPI for Windows
not running Cygwin?
I know it uses /dev/shm
Depending on what you need, the old 1.6 version might still work.
Damien
On 2015-05-13 2:19 PM, Walt Brainerd wrote:
No, I hadn't received any response.
That is too bad.
Knowing that earlier would have saved some hours.
Some day I'll look again at extracting some set of stuff
from Cygwin
/lis/
Both of these can handle very large problems in shared-memory and have
good scale-up.
Damien
On 18/11/2013 7:09 AM, Florian Bruckner wrote:
hi,
how can i call an MPI parallelized solver routine from a sequential
code. The sequential code is already existing and the structure looks
like
Guys,
Don't do it. It doesn't work at all. I couldn't pick up maintenance of
it either, and the majority of the Windows support is removed as Ralph
said. Just use MPICH for Windows work and save yourself the pain.
Cheers,
Damien
On 2014-07-16 9:57 AM, Nathan Hjelm wrote:
It likely
, there's a lot happening. Would it be a better business model
for MS to piggy-back off of Open-MPI ongoing innovation, and put their
resources into maintaining a Windows build of Open-MPI instead?
Damien
On 2014-07-17 11:42 AM, Jed Brown wrote:
Rob Latham <r...@mcs.anl.gov> writes:
W
Visual Studio can link libs compiled with Intel. We used to make
binaries available for Windows with Open-MPI.
On 2014-07-17 12:58 PM, Ralph Castain wrote:
Well, yeah - I dig that. However, barring doing something stupid, I am hopeful
we'll be okay if I continue OMPI's practice of staying
icc is the Intel C/C++ compiler. Do you have it installed on your system?
Damien
On 29/11/2010 10:43 AM, Maurício Rodrigues wrote:
HI, I need to install opnmpi 1.4.2 in Ubuntu 4.10 64bit, and giving
this error all the time ... I would like to help.
below follows the lines of the error
Hi Hiral,
The 1.4 series doesn't have Fortran support on Windows. You need to use
1.5.
Damien
On 16/03/2011 4:47 AM, hi wrote:
Greetings!!!
I am trying to build openmpi-1.3.4 and openmpi-1.4.3 on Windows 7
(64-bit OS), but getting some difficuty...
My build environment:
OS : Windows
Hiral,
To add to Shiqing's comments, 1.5 has been running great for me on
Windows for over 6 months since it was in beta. You should give it a try.
Damien
On 16/03/2011 8:34 AM, Shiqing Fan wrote:
Hi Hiral,
> it's only experimental in 1.4 series. And there is only F77
bingdi
, but not
_MPI_NULL_COPY_FN. In the 1.5.2.2 libmpi.lib there's symbols for both.
Damien
Shiqing,
I'm using Composer XE2011 and Visual Studio 2008. VS2008 is doing the
linking. I'll do a build of 1.5.3 myself and see how the symbols turn out.
Damien
On 16/04/2011 1:50 PM, Shiqing Fan wrote:
Hi Damien,
Which version of Intel MPI do you use? The only difference between
1.5.3
That last error is because you don't have permission to install to /opt
as a regular user. You need to run that command as "sudo make install".
Damien
On 03/05/2011 1:55 PM, Steph Bredenhann wrote:
I think you are a genius!
The new result is attached, it was only the last step ma
MPI can get through your firewall, right?
Damien
On 20/05/2011 12:53 PM, Jason Mackay wrote:
I have verified that disabling UAC does not fix the problem. xhlp.exe
starts, threads spin up on both machines, CPU usage is at 80-90% but
no progress is ever made.
>From this state, Ctrl-br
in 32-bit and you still need to link with 32-bit OpenMPI.
Damien
On 24/06/2011 12:16 PM, Jeffrey A Cummings wrote:
I'm having a problem using the prebuilt Windows version 1.5.3 with my
app built with MS VisualStudio 2010. I get an error message (for each
node) that says: "The procedure
Yeah, and I'm wrong too, InterlockedCompareExchange64 is available on
32-bit. I think this is one for Shiqing.
You could build OpenMPI yourself if you have VS2008. It's pretty easy
to do.
Damien
On 24/06/2011 1:51 PM, Jeffrey A Cummings wrote:
Damien -
I'm using the 32 bit version
and locks
the executable because it thinks it's a virus. A few seconds later when
nothing bad happens, it releases it again, but often too late for other
users of the exe.
If you're running antivirus software, turn it off or add an exception
for your build directory, and try again.
Damien
On 12/06/
Once you've run the installer, you'll have a set of OpenMPI debug and
release dlls, libraries to link to and the necessary include files. If
you're installing the 64-bit version, it will end up here by default:
C:\Program Files (x86)\OpenMPI_v1.6-x64
Damien
On 13/06/2012 1:35 PM, vimalmat
Funny you should ask for that, I'm doing that right now. First pass
I'll post right here as specific instructions for Vimal in a few
minutes, then you and Shiqing and I can assemble something complete
off-list.
Damien
On 13/06/2012 2:56 PM, Jeff Squyres wrote:
Yes, I guess it is fair
l they're bulletproof. I can help you build with
whatever compilers you have on your system, just post back to the list.
I don't do Cygwin though. Doing HPC on Windows is weird enough. :-)
Damien
On 13/06/2012 1:35 PM, vimalmat...@eaton.com wrote:
What do I do after I run it?
it contains.
VS is a project and build system that drives the configuration for the
compiler, just like autotools and make are on Linux. Nothing's done for
you, you have to set them up for yourself.
Damien
On 13/06/2012 4:21 PM, Shiqing Fan wrote:
This is definitely NOT a good solution
I was just typing that... :-)
On 14/06/2012 8:19 AM, vimalmat...@eaton.com wrote:
Sorry Damien, my mistake.
Selected the wrong version of VS.
--
Vimal
*From:*users-boun...@open-mpi.org [mailto:users-boun...@open-mpi.org]
*On Behalf Of *vimalmat...@eaton.com
*Sent:* Thursday, June 14
include, lib and bin directories from there.
This will give you a simple VS project that you can use to start
building your own stuff.
Damien
On 14/06/2012 8:55 AM, vimalmat...@eaton.com wrote:
Everything went as you expected.
No errors except that I don't have Fortran compilers so checking
OM
That goes in Configuration Properties - C/C++ - Preprocessor -
Preprocessor Definitions.
Damien
On 14/06/2012 10:07 AM, vimalmat...@eaton.com wrote:
Thanks a lot Damien.
When I compile the code that they've used in the link you sent, I get
this error: *error LNK2001: unresolved external
"*The Program can't start because MSVCR100.dll is missing from
your computer*".
What did I miss?
--
Vimal
*From:*users-boun...@open-mpi.org [mailto:users-boun...@open-mpi.org]
*On Behalf Of *Damien
*Sent:* Thursday, June 14, 2012 12:11 PM
*To:* Open MPI Users
*Subject:* Re: [
directory and it will use all your
OpenMPI exes and dlls because it will look there first.
Welcome to path pain. Happens on every operating system.
Damien
On 14/06/2012 11:19 AM, vimalmat...@eaton.com wrote:
No, it's the VS 2008 Express edition.
--
Vimal
*From:*users-boun...@open-mpi.org
OK. We might need to see the code for the program you're trying to run
with mpiexec to help with that one. Is that the full output?
Damien
On 14/06/2012 11:41 AM, vimalmat...@eaton.com wrote:
Did the copy paste.
Now I get a message saying: *mpiexec noticed that the job aborted, but
has
project. And change
printf ("Number of threads = %d, My rank = %d\n", nTasks, rank);
to
std::cout << "Number of threads = " << nTasks << ", My rank = " << rank
<< "\n";
Damien
On 14/06/2012 11:52 AM, vimalmat...@eaton.
I.exe". Then
change the -n 1 to -n x where x is the number of cores you have. Say
yes to allowing mpiexec firewall access if that comes up.
If this bombs out, there's something wrong on your machine.
Damien
On 14/06/2012 1:07 PM, vimalmat...@eaton.com wrote:
Anything else that you can
*
--
Vimal
*From:*users-boun...@open-mpi.org [mailto:users-boun...@open-mpi.org]
*On Behalf Of *Damien
*Sent:* Thursday, June 14, 2012 3:38 PM
*To:* Open MPI Users
*Subject:* Re: [OMPI users] Building MPI on Windows
Here's a MPI Hello World project based on your code. It runs fine on
my ma
t lib path in the Linker options. Linking to VS2008 libs and
trying to run with VS2010 dlls/exes could cause problems too.
Damien
On 15/06/2012 11:44 AM, vimalmat...@eaton.com wrote:
Hi Damien,
I installed MS Visual Studio 2010 and tried the whole procedure again
and it worked!
That's the great
eigh in with what that is.
Damien
On 15/06/2012 1:10 PM, vimalmat...@eaton.com wrote:
Just figured it out.
The only thing different from when it ran yesterday to today was I was
connected to a network. So I connected my laptop to a network and it
worked again.
Thanks for all your help, Damien!
you can do anything on a cluster.
Damien
On 19/06/2012 10:53 AM, vimalmat...@eaton.com wrote:
Damien, Shiqing, Jeff?
--
Vimal
*From:*users-boun...@open-mpi.org [mailto:users-boun...@open-mpi.org]
*On Behalf Of *vimalmat...@eaton.com
*Sent:* Monday, June 18, 2012 3:32 PM
*To:* us...@open
defined.
Also, make sure you're not set to a 64-bit project type using 32-bit
OpenMPI.
Damien
On 25/06/2012 8:57 PM, Dr AD wrote:
Hello,
I installed the windows binaries by running OpenMPI_v1.6-1_win32.exe
In VS2008 professional I set the following project preferences:
Configuration
Yep.
On 18/07/2012 8:53 AM, Kumar, Sudhir wrote:
Hi
Just wondering if Fortran90 bindings are available for OpemMPI 1.6
Thanks
*Sudhir Kumar*
___
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
on Windows. :-(
Damien
On 18/07/2012 9:00 AM, Kumar, Sudhir wrote:
Hi had meant to say if Fortran90 bindings for Windows
*Sudhir Kumar*
*From:*users-boun...@open-mpi.org [mailto:users-boun...@open-mpi.org]
*On Behalf Of *Damien
*Sent:* Wednesday, July 18, 2012 9:56 AM
*To:* Open MPI Users
Sudhir,
F77 works on both.
Damien
On 25/07/2012 8:55 AM, Kumar, Sudhir wrote:
Hi
I have one more related question. Is the F77 bindings available for
both 64bit and 32 bit windows environments or just for the 32 bit
environment.
Thanks
*From:*users-boun...@open-mpi.org [mailto:users
Hmmm. My 64-bit builds create mpif77.exe, libmpi_f77.lib and
libmpi_f77.dll, and they work.
Damien
On 25/07/2012 10:11 AM, Kumar, Sudhir wrote:
Hi
I am new to Open MPI so please pardon my ignorance, I just came across
an article which refers to F77 bindings available for 32 bit windows
Do you have
OMPI_IMPORTS, OPAL_IMPORTS and ORTE_IMPORTS
defined in your preprocessor flags? You need those.
Damien
On 26/07/2012 3:56 PM, Sayre, Alan N wrote:
I'm trying to replace the usage of platform mpi with open mpi. I am
trying to compile on Windows 7 64 bit using Visual Studio
OK, I give. I think this is a Shiqing question.
Damien
On 02/10/2012 12:25 AM, Gib Bogle wrote:
They don't make any difference. I had them in, but dropped them when I found
that the mpicc build didn't need them.
Gib
From: users-boun...@open-mpi.org
No worries. It's good to see that it compiles.
Damien
On 02/10/2012 2:25 PM, Gib Bogle wrote:
Hi Shiqing,
Your post made me realize my mistake! I was thinking only of the
preprocessor definitions for compiling cvAdvDiff_non_p.c, forgetting
about the previously built library
of MPI. The networks are separate
because it's more efficient.
Damien
On 27/10/2012 11:00 AM, Jeff Squyres wrote:
On Oct 27, 2012, at 12:47 PM, Mahmood Naderan wrote:
Because communicating through shared memory when sending messages between
processes on the same server is far faster than
Mathieu,
Where is the crash? Without that info, I'd suggest turning off all the
optimisations and just compile it without any flags other than what you
need to compile it cleanly (so no /O flags) and see if it crashes.
Damien
On 26/10/2012 10:27 AM, Mathieu Gontier wrote:
Dear all,
I am
Is there a series of error messages or anything at all that you can post
here?
Damien
On 29/10/2012 2:30 PM, Mathieu Gontier wrote:
Hi guys.
Finally, I compiled with /O: the options is deprecated and, like I did
previously, I used /Od instead... unsuccessfully.
I also compiled my code
That's a null pointer access. It's not necessarily OpenMPI causing that.
You'll need to supply more info about what you're running.
Damien
Sent from my android device.
-Original Message-
From: "Jeff Squyres (jsquyres)" <jsquy...@cisco.com>
To: Open MPI Users <
Ignore what I posted, Hristo is right. On my phone screen the C looked like
a 0. Sorry.
Damien
Sent from my android device.
-Original Message-
From: "Jeff Squyres (jsquyres)" <jsquy...@cisco.com>
To: Open MPI Users <us...@open-mpi.org>
Cc: "us..
binaries each time.
Damien
On 03/12/2012 9:55 AM, Iliev, Hristo wrote:
Hi,
0xC07B is STATUS_INVALID_IMAGE_FORMAT. It mostly means that some of the
dynamic link libraries (DLLs) that the executable is linked against are of
different "bitness", e.g. 32-bit. It could be a packa
on Windows with OpenMPI, maybe we can see what can be done if you're
interested.
Damien
advantages apply on Windows and would they justify ongoing Windows
support?
Damien
On 03/12/2012 11:59 AM, John R. Cary wrote:
Dear OpenMPI community,
This email is about whether a commercial version of OpenMPI for Windows
could be successful. I hesitated before sending this, but upon asking
So far, I count three people interested in OpenMPI on Windows. That's
not a case for ongoing support.
Damien
On 04/12/2012 11:32 AM, Durga Choudhury wrote:
All
Since I did not see any Microsoft/other 'official' folks pick up the
ball, let me step up. I have been lurking in this list
of their HPC
team I think OpenMPI on Windows lost the actual business driver for a
critical mass of users, and that's what we're seeing now. I'll still
use OpenMPI on Linux, but I think on Windows it will be HPC Pack or MPICH.
Damien
On 18/12/2012 10:20 AM, JR Cary wrote:
So a question - why do
More or less. There's just not enough critical mass to keep it going.
Damien
Sent from my android device.
-Original Message-
From: "Hartman, Todd W." <thart...@mst.edu>
To: 'Open MPI Users' <us...@open-mpi.org>
Sent: Thu, 21 Feb 2013 10:13 AM
Subject: Re:
on
this I'm happy to test or help out.
Damien
wipes the CMAKE_Fortran_COMPILER variable and complains
about a missing Fortran compiler. Any suggestions?
Damien
On 07/05/2010 3:09 AM, Shiqing Fan wrote:
Hi Damien,
Currently only Fortran 77 bindings are supported in Open MPI on
Windows. You could set the Intel Fortran compiler
re's an installation error on mpi_portable_platform.h. That
file isn't generated as part of the build, and the installation command
is around line 150 of ompi/CMakeLists.txt. If you comment out the
installation of that file the installation works correctly.
I used the 1.5a1r23092 snapshot for this.
Now to make sure
Ah. So it is. I'll try to remember to look there first.
Damien
On 10/05/2010 2:33 PM, Shiqing Fan wrote:
Hi Damien,
That's a known problem. see this ticket
https://svn.open-mpi.org/trac/ompi/ticket/2404 . It will be applied
into 1.5 branch very soon. But if you apply the patch by yourself
I ended up using the SVN Trunk from today, everything is working fine on
that.
Damien
On 10/05/2010 2:33 PM, Shiqing Fan wrote:
Hi Damien,
That's a known problem. see this ticket
https://svn.open-mpi.org/trac/ompi/ticket/2404 . It will be applied
into 1.5 branch very soon. But if you apply
narrow this down.
Damien
t errors about error code -31 and mt.exe
at the end of the build, that's your virus scanner locking the new
exe/dll files and the install project complains. Keep right-clicking
and Build Solution until it goes through. The final Open MPI include
files and binaries are in the C:\Users\Alex's\Downloads..
You should check out the MUMPS parallel linear solver.
Damien
Sent from my iPhone
On 2010-07-17, at 5:16 PM, Daniel Janzon <jan...@gmail.com> wrote:
Dear OpenMPI Users,
I successfully installed OpenMPI on some FreeBSD machines and I can
run MPI programs on the cluster. Yippie!
B
successfully. BUT: the Install project will fail, because it tries to
install libopen-pald.pdb (possibly others too, I didn't check). It's a
minor thing, only nuisance value. If you set a Release project in
CMake, everything works fine.
Damien
This might be the wrong list to ask this on. I work in a shop that does
cross-platform HPC. Can I get on a list for testing the Windows version
of OpenMPI when it's ready to be banged on? I realise it's a while away
yet.
Damien
the same as you change the number of cores or processes, although you
should reach the same overall error tolerance in approximately the same
number of iterations.
Damien
On 2015-10-28 3:51 PM, Diego Avesani wrote:
dear Andreas, dear all,
The code is quite long. It is a conjugate gradient algorithm
If you look around on Ebay, you can find old 16-core Opteron servers for
a few hundred dollars. It's not screaming performance, but 16 cores is
enough to get you started on scaling and parallelism in MPI. It's a
cheap cluster in a box.
Damien
On 5/20/2016 12:40 PM, MM wrote:
Hello,
Say I
include "seed/mpi_info.cc.hh"
#endif
$ cat include/seed/mpi_info.cc.hh
#ifndef INCLUDE_SEED_MPI_INFO_CC_HH
#define INCLUDE_SEED_MPI_INFO_CC_HH
#include "seed/mpi_info.hh"
inline shor::seed::Mpi_info::operator MPI::Info() const
{
return impl_;
}
#endif
$ cat src/mpi_info.cc
#include &quo
On May 14, 2013, at 1:46 PM, Ralph Castain
wrote:
> Problem is that comm_accept isn't thread safe in 1.6 series - we have a devel
> branch that might solve it, but is still under evaluation
So then probably the only way to implement an MPI server which handles multiple
On May 14, 2013, at 3:02 PM, Ralph Castain <r...@open-mpi.org>
wrote:
>
> On May 14, 2013, at 12:56 PM, Damien Kick <dk...@shoretel.com> wrote:
>
>>
>> On May 14, 2013, at 1:46 PM, Ralph Castain <r...@open-mpi.org>
>> wrote:
>>
>>>
as amazing every 18 months.
Chuck Norris is infinitely scalable.
MPI_COMM_WORLD is only a small part of Chuck Norris's mind.
Chuck Norris can power Exascale. Twice.
:-)
Damien
On 23/10/2013 4:26 PM, Shamis, Pavel wrote:
+1 for Chuck Norris
Pavel (Pasha) Shamis
---
Computer Science Research Group
You didn't mention complete Fortran support on Windows, thanks to
Shiqing. :-)
Damien
On 10/10/2010 5:50 PM, Jeff Squyres wrote:
The Open MPI Team, representing a consortium of research, academic, and
industry partners, is pleased to announce the release of Open MPI version 1.5
Jeff, Shiqing, anyone...
I notice there's no Fortan support in the Windows binary versions of
1.5.1 on the website. Is that a deliberate decision?
Damien
./configure --prefix=/usr/local/OpenMPI-intel --enable-static
--enable-shared
You might have to do the same full path for CXX, F77, FC flags too.
Damien
CC=On 28/01/2011 7:18 PM, Greef, T.F.A. de wrote:
Hi everybody,
I try to compile openmpi with intel compilers on ubuntu 10.10
Everything
Manoj,
Those binaries were built for use with Visual Studio 2008, not MinGW. I
don't know if OpenMPI has been built with MinGW before, maybe someone on
the list knows.
Damien
On 27/02/2011 4:42 AM, Manoj Vaghela wrote:
Hi All,
I have downloaded the latest version OpenMPI binaries
Gib,
If you have OMPI_IMPORTS set that usually removes those symbol errors.
Are you absolutely sure you have everything set to 32-bit in Visual Studio?
Damien
On 01/10/2012 7:55 PM, Gib Bogle wrote:
I am building the Sundials examples, with MS Visual Studio 2005
version 8 (i.e. 32-bit
So mpicc builds it completely? The only thing I can think of is look
closely at both the compile and link command lines and see what's
different. It might be going sideways at the compile from something in
an include with a preprocessor def.
Damien
On 01/10/2012 9:57 PM, Gib Bogle wrote
There's two imports missing from there, OPAL_IMPORTS and ORTE_IMPORTS.
That might be part of it.
Damien
On 01/10/2012 10:20 PM, Gib Bogle wrote:
I guess it's conceivable that one of these Sundials include files is
doing something:
#include /* prototypes for CVODE
fcts
I've never seen that, but someone else might have.
Damien
On 30/10/2012 1:43 AM, Mathieu Gontier wrote:
Hi Damien,
The only message I have is:
[vs2010:09300] [[56007,0],0]-[[56007,1],0] mca_oob_tcp_msg_recv: readv
failed: Unknown error (108)
[vs2010:09300] 2 more processes have sent help
I can probably fix the 1.6.3 build. I think it's just bumping CMake
support and tweaks so that VS2012 works. But yeah, it looks a bit grim
going forward.
Damien
On 07/12/2012 8:28 AM, Jeff Squyres wrote:
Sorry for my late reply; I've been in the MPI Forum and Open MPI engineering
meetings
I know 1.6.3 is broken for Win builds with VS2012 and Intel. I'm not a
MinGW expert by any means, I've hardly ever used it. I'll try and look
at this on the weekend. If you can post on Friday to job my memory that
would help. :-)
Damien
On 12/12/2012 3:31 AM, Ilias Miroslav wrote:
Ad
, that link should fail too. Is the C++ version
of OpenMPI actually broken overall?
The Windows support is another issue. I think it's semi-officially
deprecated.
Damien
On 20/02/2013 11:20 PM, Hartman, Todd W. wrote:
I'm trying to build a simple Open MPI application for Windows. I've
erything's in there, a dumpbin shows all the MPI::Datatype symbols.
Those symbols are missing all the way back into 1.5 shared-lib builds as
well.
Damien
On 21/02/2013 12:19 PM, Jeff Squyres (jsquyres) wrote:
On Feb 21, 2013, at 10:59 AM, Damien Hocking <dam...@khubla.com> wrote:
Well thi
directory. You're probably getting the OpenMPI headers instead of the
dummy ones. I can't open your bz2, my machine tells me it's borked, so
I can't read your log and see exactly where it's going wrong.
Damien
Roberto C. Sánchez wrote:
Hi,
I am in the process of packaging coinor-ipopt for Debian
? I can keep going with CMake 2.6.4 if need be.
Damien
OK, thanks, I'll do that.
Damien
Shiqing Fan wrote:
Hi Damien,
r22405 was the fix for the trunk, it hasn't been patched into 1.4
branch yet, see the open ticket for v1.4 branch:
https://svn.open-mpi.org/trac/ompi/ticket/2169, it's RM approved, so
it will be moved very soon. And please
Can anyone tell me how to enable Fortran bindings on a Windows build?
Damien
)
FILE(INSTALL DESTINATION "${CMAKE_INSTALL_PREFIX}/bin" TYPE FILE
FILES "C:/projects2/openmpi-1.4.1/build64/Debug/libopen-rted.pdb")
ENDIF(NOT CMAKE_INSTALL_COMPONENT OR "${CMAKE_INSTALL_COMPONENT}"
STREQUAL "Unspecified")
Damien
Hmmm. I did try setting release and I think I still got pdbs. I'll try
again from a totally clean source tree and post back.
Damien
On 10-02-04 4:41 AM, Shiqing Fan wrote:
Hi Damien,
I did a clean build on my 64 bit Windows 7, but I didn't see the same
problem. Could you please make sure
setups for 32 and 64-bit builds. I set mine up with build32 and build64
directories, and install32 and install64 directories to keep everything
separate.
HTH,
Damien
On 04/02/2010 7:34 AM, Marcus G. Daniels wrote:
Hmmm. I did try setting release and I think I still got pdbs. I'll try
again from
Hi all,
Does OpenMPI support dynamic process management without launching
through mpirun or mpiexec? I need to use some MPI code in a
shared-memory environment where I don't know the resources in advance.
Damien
Yes, that's right. It will launch a singleton, and then add slaves as
required. Thank you.
Damien
On 24/02/2010 6:17 PM, Ralph Castain wrote:
Let me see if I understand your question. You want to launch an initial MPI code using
mpirun or as a singleton. This code will then determine
return 0;
}
Also, this only starts up correctly if I kick it off with orterun.
Ideally I'd like to run it as "master.exe" and have it initialise the
MPI environment from there. Can anyone tell me what setup I need to do
that?
Thanks in advance,
Damien
Thanks Shiqing. I'll checkout a trunk copy and try that.
Damien
On 04/03/2010 7:29 AM, Shiqing Fan wrote:
Hi Damien,
Sorry for late reply, I was trying to dig inside the code and got some
information.
First of all, in your example, it's not correct to define the MPI_Info
as an pointer
A few people have looked at EC2 for this lately. This one's a good read.
http://insidehpc.com/2009/08/03/comparing-hpc-cluster-amazons-ec2-nas-benchmarks-linpack/
There was another paper published too, if I can find it again I'll post
the link.
Damien
On 19/03/2010 9:17 PM, Joshua
Thanks Shiqing. I'll try that. I'm not sure which bindings MUMPS uses,
I'll post back if I need F90.
My apologies for not asking a clearer question, when I said Fortran 90
support on Windows, I meant Open MPI, not compilers.
Damien
On 07/05/2010 3:09 AM, Shiqing Fan wrote:
Hi Damien
Absolutely. I'll get a package of stuff put together.
Damien
On 12/05/2010 2:24 AM, Shiqing Fan wrote:
Hi Damien,
I know there will be more problems, and your feedback is always
helpful. :-)
Could you please provide me a Visual Studio solution file for MUMPS? I
would like to test
You don't need to check anything alse in the red window, OpenMPI doesn't
know it's in a virtual machine. If you're running Windows in a virtual
cluster, are you running as 32-bit or 64-bit?
Damien
On 12/07/2010 5:05 PM, Alexandru Blidaru wrote:
Wow thanks a lot guys. I'll try it tomorrow
slightly wrong for 32-bit Windows, there won't be a Win64 x64 prompt.
There will be only one command prompt option on a 32-bit install (use
that), and CMake will have set you up with a 32-bit build by default, so
you'll be fine. Post back if you need help.
Damien
On 12/07/2010 5:47 PM, Alexand
It does. The big difference is that MUMPS is a 3-minute compile, and
PETSc, erm, isn't. It's..longer...
D
On 19/07/2010 12:56 PM, Daniel Janzon wrote:
Thanks a lot! PETSc seems to be really solid and integrates with MUMPS
suggested by Damien.
All the best,
Daniel Janzon
On 7/18/10
Is there a timeline for the Windows version yet?
Damien
Outstanding. I'll have two.
Damien
George Bosilca wrote:
The Open MPI Team, representing a consortium of bailed-out banks, car
manufacturers, and insurance companies, is pleased to announce the
release of the "unbreakable" / bug-free version Open MPI 2009,
(expected to be availa
1 - 100 of 102 matches
Mail list logo