[Trilinos-Users] Tpetra Running Error

[Hoemmen, Mark]

Thanks to Mike for asking the relevant question.  MPI must be initialized before you may call any Tpetra functions or create instances of any Tpetra classes.  Please refer to the following Tpetra lesson, which explains different ways to initialize MPI for use with Tpetra:

http://trilinos.sandia.gov/packages/docs/dev/packages/tpetra/doc/html/Tpetra_Lesson01.html

mfh

On Jan 6, 2014, at 12:00 PM, <trilinos-users-request at software.sandia.gov>
 wrote:
> Message: 1
> Date: Mon, 6 Jan 2014 15:16:39 +0900
> From: "Sunghwan Choi" <sunghwanchoi91 at gmail.com>
> Subject: [Trilinos-Users] Tpetra Running Error
> To: trilinos-users at software.sandia.gov
> Message-ID: <000001cf0aa6$e09e18a0$a1da49e0$@gmail.com>
> Content-Type: text/plain; charset="us-ascii"
> 
> Dear Trilinos user,
> 
> I am a newbie of tpetra. 
> 
> I installed tpetra and I tried to test it. But whenever I tried to run it, I
> got the same message like below
> 
> 
> 
> *** The MPI_Comm_set_errhandler() function was called before MPI_INIT was
> invoked.
> 
> *** This is disallowed by the MPI standard.
> 
> *** Your MPI job will now abort.
> 
> [messi:29111] Local abort before MPI_INIT completed successfully; not able
> to aggregate error messages, and not able to guarantee that all other
> processes were killed!
> 
> --------------------------------------------------------------------------
> 
> mpirun noticed that the job aborted, but has no info as to the process
> 
> that caused that situation.
> 
> --------------------------------------------------------------------------  
> 
> 
> 
> 
> 
> 
> 
> What is the problem? If you have any clue, please let me know.
> 
> 
> 
> 
> 
> Graduate Student @ Chemistry Department, KAIST (South Korea)
> 
> Sunghwan Choi
> 
> 
> 
> 
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: https://software.sandia.gov/pipermail/trilinos-users/attachments/20140106/20da77b3/attachment-0001.html 
> 
> ------------------------------
> 
> Message: 2
> Date: Mon, 6 Jan 2014 16:37:34 +0000
> From: "Heroux, Mike" <MHeroux at csbsju.edu>
> Subject: Re: [Trilinos-Users] Tpetra Running Error
> To: "Sunghwan Choi" <sunghwanchoi91 at gmail.com>
> Cc: "trilinos-users at software.sandia.gov"
> 	<trilinos-users at software.sandia.gov>
> Message-ID: <C7BF52E5-4183-40BD-A9C3-7EDE9054D108 at CSBSJU.EDU>
> Content-Type: text/plain; charset=us-ascii
> 
> Just asking the obvious:  Did you call MPI_Init before calling any Tpetra functions?
> 
> Mike
> 
> On Jan 6, 2014, at 12:19 AM, "Sunghwan Choi" <sunghwanchoi91 at gmail.com<mailto:sunghwanchoi91 at gmail.com>> wrote:
> 
> Dear Trilinos user,
> I am a newbie of tpetra.
> I installed tpetra and I tried to test it. But whenever I tried to run it, I got the same message like below
> 
> *** The MPI_Comm_set_errhandler() function was called before MPI_INIT was invoked.
> *** This is disallowed by the MPI standard.
> *** Your MPI job will now abort.
> [messi:29111] Local abort before MPI_INIT completed successfully; not able to aggregate error messages, and not able to guarantee that all other processes were killed!
> --------------------------------------------------------------------------
> mpirun noticed that the job aborted, but has no info as to the process
> that caused that situation.
> --------------------------------------------------------------------------
> 
> 
> 
> What is the problem? If you have any clue, please let me know.
> 
> 
> Graduate Student @ Chemistry Department, KAIST (South Korea)
> Sunghwan Choi
> 
> 
> _______________________________________________
> Trilinos-Users mailing list
> Trilinos-Users at software.sandia.gov<mailto:Trilinos-Users at software.sandia.gov>
> http://software.sandia.gov/mailman/listinfo/trilinos-users
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> Trilinos-Users mailing list
> Trilinos-Users at software.sandia.gov
> http://software.sandia.gov/mailman/listinfo/trilinos-users
> 
> 
> End of Trilinos-Users Digest, Vol 101, Issue 2
> **********************************************