That fixed it! Thanks. I knew it would be something silly like that.
On Fri, Aug 28, 2015 at 12:53 PM, Derek Gaston wrote:
> Are you using std::cout to print a message out?
>
> libMesh (by default) eats all std::cout output on all processors other
> than processor zero. You can use the command
On Fri, Aug 28, 2015 at 10:49 AM, Andrew Donaldson Davis
wrote:
> Hello all,
>
> You might have to forgive me if this is a silly question but I'm having
> some trouble understanding how LibMesh initializes MPI.
>
> I have the code:
>
> using namespace std;
> namespace mpi = boost::mpi;
>
> int ma
Are you using std::cout to print a message out?
libMesh (by default) eats all std::cout output on all processors other than
processor zero. You can use the command-line option of "--keep-cout" to
keep that from happening... or you can print to std::err (which is
normally what I do in these cases
Hello all,
You might have to forgive me if this is a silly question but I'm having
some trouble understanding how LibMesh initializes MPI.
I have the code:
using namespace std;
namespace mpi = boost::mpi;
int main(int argc, char **argv) {
mpi::environment env(argc, argv);
unique_ptr worldC
