I have looked over the docs at http://www.boost.org/doc/libs/1_55_0/doc/html/mpi/getting_started.html#mpi.c... and I just don't really understand what the <find-shared-library> option does in this: using mpi : : <find-shared-library>lammpio <find-shared-library>lammpi++ <find-shared-library>mpi <find-shared-library>lam <find-shared-library>dl ; I don't understand how this maps into the instructions here: http://www.boost.org/build/doc/html/bbv2/reference/tools.html

Date: Wed, 10 Jun 2015 18:42:17 +0000 From: "Cook, Rich" To: "boost-users@lists.boost.org" Subject: Re: [Boost-users] Boost-users Digest, Vol 4163, Issue 2 Message-ID: <4F5E3BDC-CDF6-442E-BB02-054510A61C61@llnl.gov> Content-Type: text/plain; charset="utf-8"

...

Hi, here is the output of those commands, modified to reflect the actual tool I told boost to use, which is mpiCC, not mpicxx. What should I do with this output, and why does boost not accept it? Thanks!

rcook@rzgpu2 (~ ): /usr/local/tools/openmpi-intel-debug-1.8.4/bin/mpicxx --showme:compile -I/usr/local/tools/openmpi-intel-debug-1.8.4/include/openmpi/opal/mca/hwloc/hwloc191/hwloc/include -I/usr/local/tools/openmpi-intel-debug-1.8.4/include/openmpi/opal/mca/event/libevent2021/libevent -I/usr/local/tools/openmpi-intel-debug-1.8.4/include/openmpi/opal/mca/event/libevent2021/libevent/include -I/usr/local/tools/openmpi-intel-debug-1.8.4/include -I/usr/local/tools/openmpi-intel-debug-1.8.4/include/openmpi -pthread

rcook@rzgpu2 (~ ): /usr/local/tools/openmpi-intel-debug-1.8.4/bin/mpicxx --showme:link -pthread -Wl,-rpath -Wl,/usr/local/tools/openmpi-intel-debug-1.8.4/lib -Wl,--enable-new-dtags -L/usr/local/tools/openmpi-intel-debug-1.8.4/lib -lmpi

Subject: Re: [Boost-users] Cannot build boost with MPI using Intel openMPI wrapper From: Alain Miniussi (alain.miniussi_at_[hidden]) Date: 2015-06-10 10:07:41

* Next message: Hadidi, Lars: "[Boost-users] Boost Random Numbers: Normal Distribution"http://lists.boost.org/boost-users/2015/06/84409.php * Previous message: Boris Sch??ling: "Re: [Boost-users] Cannot build boost with MPI using Intel openMPI wrapper"http://lists.boost.org/boost-users/2015/06/84407.php * In reply to: Boris Sch??ling: "Re: [Boost-users] Cannot build boost with MPI using Intel openMPI wrapper"http://lists.boost.org/boost-users/2015/06/84407.php

________________________________

What is the result of: $/usr/local/tools/openmpi-intel-debug-1.8.4/bin/mpicxx --showme:compile $/usr/local/tools/openmpi-intel-debug-1.8.4/bin/mpicxx --showme:link ?

On 10/06/2015 11:08, Boris Sch?ling wrote:

...

On Wed, 10 Jun 2015 02:37:26 +0200, Cook, Rich wrote:

...

Hello, I'm seeing this in my build output. I'm hoping someone can help me find out what the actual problem is. Thanks for any assistance.

===============MPI Auto-configuration=============== MPI auto-detection failed: unknown wrapper compiler /usr/local/tools/openmpi-intel-debug-1.8.4/bin/mpiCC Please report this error to the Boost mailing list: http://www.boost.orghttp://www.boost.org/ You will need to manually configure MPI support. MPI launcher: mpirun -np ====================================================

-- ?Richard Cook ? Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ? (office) (925) 423-9605 ? (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL)

------------------------------

Message: 2 Date: Wed, 10 Jun 2015 16:56:04 -0700 From: Nicholas Yue To: boost-users@lists.boost.org Subject: Re: [Boost-users] Modify an asio echo server so that it does not send message back to client Message-ID: <5578CE94.9000304@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed

On 2015-06-09 5:14 PM, Gavin Lambert wrote:

...

You need to pass the bytes_transferred to process as well, so that it knows how much data was actually read and therefore how much of data_ is actually valid. Don't forget that this may be less than max_length and may be different from what the client actually sent (ie. data sent in one chunk may be received in multiple chunks).

Thanks Gavin.

I now have a process() method with the bytes_transferred parameter.

Newbie question, how do I know the last chunk has been sent, so that I can now process the data (which will be binary) ?

Is there some simple example which illustrate this I can refer to ?

Cheers Nicholas Yue

------------------------------

Message: 3 Date: Thu, 11 Jun 2015 12:16:06 +1200 From: Gavin Lambert To: boost-users@lists.boost.org Subject: Re: [Boost-users] Modify an asio echo server so that it does not send message back to client Message-ID: Content-Type: text/plain; charset=windows-1252; format=flowed

On 11/06/2015 11:56, Nicholas Yue wrote:

...

I now have a process() method with the bytes_transferred parameter.

Newbie question, how do I know the last chunk has been sent, so that I can now process the data (which will be binary) ?

Is there some simple example which illustrate this I can refer to ?

There isn't any inherent way to know. TCP is a stream protocol -- you just receive a continuous stream of bytes with no demarcation of any kind.

You will need to define something at the application layer of the protocol to decide when a logical unit is complete, typically either by inserting some delimiter that you know can never occur mid-message or by sending the length of the following data early on.

Note that ASIO does provide some helper methods for these scenarios -- instead of using async_read_some, which just returns data as it becomes available, you can use asio::async_read (which you can tell to not return until it has read a specific number of bytes) or asio::async_read_until (read until a specific delimiter). (It's tricky, though not impossible, to do a combination of the two -- but it's something you should avoid if you have a choice.)

So for a line-based protocol you could async_read_until a CRLF (or just LF, depending on the other end), or for a binary protocol that sends a 4-byte length followed by a payload you could async_read 4 bytes to get the length, then async_read that many bytes to get the payload.

------------------------------

Message: 4 Date: Wed, 10 Jun 2015 23:00:42 -0400 From: Tim Song To: boost-users@lists.boost.org Subject: Re: [Boost-users] Boost Random Numbers: Normal Distribution Message-ID: Content-Type: text/plain; charset="utf-8"

On Wed, Jun 10, 2015 at 11:59 AM, Hadidi, Lars < lhadidi@students.uni-mainz.de> wrote:

...

I'd like to know which method is employed here.

Have you tried reading the implementation ( http://www.boost.org/doc/libs/1_58_0/boost/random/normal_distribution.hpp)?

Hint: The first comment after the includes is

// tables for the ziggurat algorithm -------------- next part -------------- HTML attachment scrubbed and removed

------------------------------

Message: 5 Date: Thu, 11 Jun 2015 08:06:04 +0200 From: Oswin Krause To: boost-users@lists.boost.org Subject: Re: [Boost-users] Boost Random Numbers: Normal Distribution Message-ID: Content-Type: text/plain; charset=UTF-8; format=flowed

Recently, it changed to Ziggurat's method.

On 2015-06-10 17:59, Hadidi, Lars wrote:

...

Hello,

I tried to find out which method is used by the boost library to transform random numbers from a random number engine to the Gaussian Distribution.

There are the Box-Muller-Method, Marsaglia's Polar Method and Ziggurat's algorithm out there, but i could not determine which of those is actually used by

boost::normal_distribution<double>?

I'd like to know which method is employed here.

Thanks for reply in advance,

sincerely,

Lars

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

------------------------------

Subject: Digest Footer

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

------------------------------

End of Boost-users Digest, Vol 4164, Issue 1 ********************************************

-- ✐Richard Cook ✇ Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ☎ (office) (925) 423-9605 ☎ (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL)