December 2012 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] Different architectures
by Peter Kroon 09 Dec '12

09 Dec '12

Are you suggestion that I should install a 32b version on all machines because 32b can't *talk* to 64b? 2012/12/9 Jeff Hammond <jhammond(a)alcf.anl.gov> > It appears you're trying to use the 64b library (ELFCLASS64...) on the > 32b master. In any case, I don't believe MPICH works in the > heterogeneous case. In theory, you should be able to use a 32b > library across both machines though. > > Jeff > > On Sun, Dec 9, 2012 at 1:40 PM, Peter Kroon <plakroon(a)gmail.com> wrote: > > Hello, > > > > I've installed mpich2 on ubuntu i386(master) via > > https://help.ubuntu.com/community/MpichCluster > > I have another machine amd64(slave). > > > > When i run my script on master I get an error: error while loading shared > > libraries: linbmpich.so.3: wrong ELF CLASS: ELFCLASS64 > > > > Is mpich compatible with different architectures? If so what's the > easiest > > way for me to get rid of my error? > > > > Also note that I need this to work with x86-64 as well. > > > > Best, > > Peter > > > > > > > > _______________________________________________ > > discuss mailing list discuss(a)mpich.org > > To manage subscription options or unsubscribe: > > https://lists.mpich.org/mailman/listinfo/discuss > > > > -- > Jeff Hammond > Argonne Leadership Computing Facility > University of Chicago Computation Institute > jhammond(a)alcf.anl.gov / (630) 252-5381 > http://www.linkedin.com/in/jeffhammond > https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss >

1 0

Re: [mpich-discuss] Different architectures
by Jeff Hammond 09 Dec '12

09 Dec '12

It appears you're trying to use the 64b library (ELFCLASS64...) on the 32b master. In any case, I don't believe MPICH works in the heterogeneous case. In theory, you should be able to use a 32b library across both machines though. Jeff On Sun, Dec 9, 2012 at 1:40 PM, Peter Kroon <plakroon(a)gmail.com> wrote: > Hello, > > I've installed mpich2 on ubuntu i386(master) via > https://help.ubuntu.com/community/MpichCluster > I have another machine amd64(slave). > > When i run my script on master I get an error: error while loading shared > libraries: linbmpich.so.3: wrong ELF CLASS: ELFCLASS64 > > Is mpich compatible with different architectures? If so what's the easiest > way for me to get rid of my error? > > Also note that I need this to work with x86-64 as well. > > Best, > Peter > > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Jeff Hammond Argonne Leadership Computing Facility University of Chicago Computation Institute jhammond(a)alcf.anl.gov / (630) 252-5381 http://www.linkedin.com/in/jeffhammond https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond

1 0

Different architectures
by Peter Kroon 09 Dec '12

09 Dec '12

Hello, I've installed mpich2 on ubuntu i386(master) via https://help.ubuntu.com/community/MpichCluster I have another machine amd64(slave). When i run my script on master I get an error: error while loading shared libraries: linbmpich.so.3: wrong ELF CLASS: ELFCLASS64 Is mpich compatible with different architectures? If so what's the easiest way for me to get rid of my error? Also note that I need this to work with x86-64 as well. Best, Peter

1 0

Re: [mpich-discuss] Bug fix for dims_create
by Ian Hutchinson 08 Dec '12

08 Dec '12

Thanks Jeff Ian Hutchinson http://www.psfc.mit.edu/people/hutch/ - > Date: Sat, 8 Dec 2012 14:46:03 -0600 > From: Jeff Hammond <jhammond(a)alcf.anl.gov> > Reply-To: discuss(a)mpich.org > To: discuss(a)mpich.org > Subject: Re: [mpich-discuss] Bug fix for dims_create > > Hi Ian, > > I have created https://trac.mpich.org/projects/mpich/ticket/1765 on > your behalf so that this issue can be tracked by the developers. > > Best, > > Jeff > > On Sat, Dec 8, 2012 at 2:07 PM, Ian Hutchinson <hutch(a)psfc.mit.edu> wrote: >> >> The file src/mpi/topo/dims_create.c contains the code that determines the >> result of >> >> MPI_DIMS_CREATE >> >> It contains a bug which causes it to produce improper distributions of the >> processes among dimensions that do not satisfy the objective of being "as >> close to each other as possible". For example, if called in 3-dimensions, >> with 16 nodes, the topology returned is 4, 4, 1. It ought to be 4, 2, 2. >> >> This bug is caused by some longstanding cobbled-together code that is called >> when all the factors of the nnodes are 2 (which is not an unusual case). >> >> I attach (and include below) a patch to correct this bug. It would be great >> if it could find its way into the distribution. >> >> Thanks >> Ian Hutchinson >> http://www.psfc.mit.edu/people/hutch/ >> >> ========================================================================= >> >> --- dims_create.c.dist 2012-12-08 13:46:46.000000000 -0500 >> +++ dims_create.c 2012-12-08 13:48:02.000000000 -0500 >> @@ -317,28 +317,22 @@ >> int cnt = factors[0].cnt; /* Numver of factors left */ >> int cnteach = ( cnt + dims_needed - 1 ) / dims_needed; >> int factor_each; >> - - factor_each = factor; >> - for (i=1; i<cnteach; i++) factor_each *= factor; >> >> - for (i=0; i<ndims; i++) { >> - if (dims[i] == 0) { >> - if (cnt > cnteach) { >> - dims[i] = factor_each; >> - cnt -= cnteach; >> - } >> - else if (cnt > 0) { >> - factor_each = factor; >> - for (j=1; j<cnt; j++) - >> factor_each *= factor; >> - dims[i] = factor_each; >> - cnt = 0; >> - } >> - else { >> - dims[i] = 1; >> - } >> + for (i=0;i<ndims;i++){ + if(dims[i]==0)dims[i]=-1; >> + } >> + i=0; >> + while(cnt > 0){ >> + if(dims[i] < 0){ >> + dims[i]=dims[i]*factor; >> + cnt--; >> } >> + if(++i >= ndims)i=0; >> + } >> + for (i=0;i<ndims;i++){ >> + if(dims[i] < 0)dims[i]=-dims[i]; >> } >> + >> } >> else { >> /* Here is the general case. */ >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss > > > >

1 0

Re: [mpich-discuss] Bug fix for dims_create
by Jeff Hammond 08 Dec '12

08 Dec '12

Hi Ian, I have created https://trac.mpich.org/projects/mpich/ticket/1765 on your behalf so that this issue can be tracked by the developers. Best, Jeff On Sat, Dec 8, 2012 at 2:07 PM, Ian Hutchinson <hutch(a)psfc.mit.edu> wrote: > > The file src/mpi/topo/dims_create.c contains the code that determines the > result of > > MPI_DIMS_CREATE > > It contains a bug which causes it to produce improper distributions of the > processes among dimensions that do not satisfy the objective of being "as > close to each other as possible". For example, if called in 3-dimensions, > with 16 nodes, the topology returned is 4, 4, 1. It ought to be 4, 2, 2. > > This bug is caused by some longstanding cobbled-together code that is called > when all the factors of the nnodes are 2 (which is not an unusual case). > > I attach (and include below) a patch to correct this bug. It would be great > if it could find its way into the distribution. > > Thanks > Ian Hutchinson > http://www.psfc.mit.edu/people/hutch/ > > ========================================================================= > > --- dims_create.c.dist 2012-12-08 13:46:46.000000000 -0500 > +++ dims_create.c 2012-12-08 13:48:02.000000000 -0500 > @@ -317,28 +317,22 @@ > int cnt = factors[0].cnt; /* Numver of factors left */ > int cnteach = ( cnt + dims_needed - 1 ) / dims_needed; > int factor_each; > - - factor_each = factor; > - for (i=1; i<cnteach; i++) factor_each *= factor; > > - for (i=0; i<ndims; i++) { > - if (dims[i] == 0) { > - if (cnt > cnteach) { > - dims[i] = factor_each; > - cnt -= cnteach; > - } > - else if (cnt > 0) { > - factor_each = factor; > - for (j=1; j<cnt; j++) - > factor_each *= factor; > - dims[i] = factor_each; > - cnt = 0; > - } > - else { > - dims[i] = 1; > - } > + for (i=0;i<ndims;i++){ + if(dims[i]==0)dims[i]=-1; > + } > + i=0; > + while(cnt > 0){ > + if(dims[i] < 0){ > + dims[i]=dims[i]*factor; > + cnt--; > } > + if(++i >= ndims)i=0; > + } > + for (i=0;i<ndims;i++){ > + if(dims[i] < 0)dims[i]=-dims[i]; > } > + > } > else { > /* Here is the general case. */ > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Jeff Hammond Argonne Leadership Computing Facility University of Chicago Computation Institute jhammond(a)alcf.anl.gov / (630) 252-5381 http://www.linkedin.com/in/jeffhammond https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond

1 0

Bug fix for dims_create
by Ian Hutchinson 08 Dec '12

08 Dec '12

The file src/mpi/topo/dims_create.c contains the code that determines the result of MPI_DIMS_CREATE It contains a bug which causes it to produce improper distributions of the processes among dimensions that do not satisfy the objective of being "as close to each other as possible". For example, if called in 3-dimensions, with 16 nodes, the topology returned is 4, 4, 1. It ought to be 4, 2, 2. This bug is caused by some longstanding cobbled-together code that is called when all the factors of the nnodes are 2 (which is not an unusual case). I attach (and include below) a patch to correct this bug. It would be great if it could find its way into the distribution. Thanks Ian Hutchinson http://www.psfc.mit.edu/people/hutch/ ========================================================================= --- dims_create.c.dist 2012-12-08 13:46:46.000000000 -0500 +++ dims_create.c 2012-12-08 13:48:02.000000000 -0500 @@ -317,28 +317,22 @@ int cnt = factors[0].cnt; /* Numver of factors left */ int cnteach = ( cnt + dims_needed - 1 ) / dims_needed; int factor_each; - - factor_each = factor; - for (i=1; i<cnteach; i++) factor_each *= factor; - for (i=0; i<ndims; i++) { - if (dims[i] == 0) { - if (cnt > cnteach) { - dims[i] = factor_each; - cnt -= cnteach; - } - else if (cnt > 0) { - factor_each = factor; - for (j=1; j<cnt; j++) - factor_each *= factor; - dims[i] = factor_each; - cnt = 0; - } - else { - dims[i] = 1; - } + for (i=0;i<ndims;i++){ + if(dims[i]==0)dims[i]=-1; + } + i=0; + while(cnt > 0){ + if(dims[i] < 0){ + dims[i]=dims[i]*factor; + cnt--; } + if(++i >= ndims)i=0; + } + for (i=0;i<ndims;i++){ + if(dims[i] < 0)dims[i]=-dims[i]; } + } else { /* Here is the general case. */

1 0

MPI 64x installation problem
by Sam Liao 08 Dec '12

08 Dec '12

Hi, I have problem installing the MPI 64x application on my new PC with win7 OS. I was able to stall it to get it running on two PC previously. I had follow the exact steps as in the instruction. It indicated successful installation. Not sure why it is not running this time. The error msg is shown below after I run the example test. Sam ===================================================== c:\nm72gf64\run>nmfe72 foce_parallel.ctl foce_parallel.res -parafile=mpiwini2.pnm doing nmtran WARNINGS AND ERRORS (IF ANY) FOR PROBLEM 1 (WARNING 2) NM-TRAN INFERS THAT THE DATA ARE POPULATION. CREATING MUMODEL ROUTINE... 1 file(s) copied. recompiling certain components. starting wait ending wait Exiting lpreddo Finished compiling fsubs USING PARALLEL PROFILE mpiwini2.pnm MPI TRANSFER TYPE SELECTED Completed call to gfcompile.bat Starting MPI version of nonmem execution ... Error while connecting to host, No connection could be made because the target machine actively refused it. (10061) Connect on sock (host=localhost, port=8676) failed, exhaused all end points Unable to connect to 'localhost:8676', sock error: Error = -1 Could Not Find c:\nm72gf64\run\output c:\nm72gf64\run>

1 0

Re: [mpich-discuss] Hangup or stall at MPI_INIT
by Rajeev Thakur 07 Dec '12

07 Dec '12

I have thought the problem may have to do with stdin/stdout. Can you comment out any prints in the program and try. Rajeev On Dec 7, 2012, at 11:40 AM, Ryan Crocker wrote: > I haven't tried that specific example but i don't see the hang when i the use intel compiler sets. I wrote a quick "hello world" and that runs every time, compiled with gfortran. I was thinking it was something to do with running past the node memory but when i check to see how much each core is allocating that's not possible from my code. The other thing i thought to try to day was remove a lot of interface calls from the parallel module and make a stand alone parallel_init module that is the very first thing called, i don't know why that would work but i'm trying it anyway. > > On Dec 7, 2012, at 8:51 AM, Rajeev Thakur wrote: > >> Does the pi3f90 example in the examples/f90 directory work? I have had that hang with gfortran for unknown reasons. >> >> Rajeev >> >> On Dec 6, 2012, at 11:27 PM, Ryan Crocker wrote: >> >>> Hi all, >>> >>> I'm having a problem with hangups or some sort of stall. Basically the program will keep running, or look as it if is on the cluster i'm running on (i've noticed this issue on multiple clusters actually), But nothing is happening. When i have every processor print out they all do right before MPI_INIT and not after. I counted the files and all the processors are entering the call. What makes it even more odd is that the same exact simulation will run if i decrease the number of nodes/cores i'm using, i.e. i'll run on 96 cores (or more) and moving to 72 my program will run without issue. >>> >>> I'm using the latest gcc compiler set with the latest version of MPICH2 configured with: >>> >>> '--with-pbs=/PBS' '--with-default-comm=pmi' '--enable-pbspro-helper' 'CC=gcc' 'LDFLAGS=-lpthread' 'CPPFLAGS=-fpic' >>> >>> I've changed to the intel/mpich2 compiler set and have not had the same problem. I have no idea what this issue could be and have had little luck finding an answer with stackoverflow or google searches any help would be much appreciated. Also, hit me up for any more information you'd need to help. >>> >>> Thanks, >>> >>> My flow solver is written in fortran and here are the subroutines leading up to the MPI_INIT call, and the whole flow solver is compiled with '-O3 -ffree-line-length-none' : >>> >>> ! ====================================== ! >>> program main >>> >>> call main_init >>> call simulation_run >>> call main_stop >>> >>> end program main >>> >>> ! ====================================== ! >>> >>> subroutine main_init >>> use string >>> implicit none >>> character(len=str_medium) :: input_name >>> >>> call parallel_init >>> >>> ! Initialize the random number generator >>> call random_init >>> >>> ! Parse the input file >>> call parser_init >>> >>> input_name='input' >>> call parser_parsefile(input_name) >>> >>> ! Geometry initialization >>> call geometry_init >>> >>> ! Data initialization >>> call data_init >>> >>> ! Simulation initialization >>> call simulation_init >>> >>> return >>> end subroutine main_init >>> >>> ! ====================================== ! >>> >>> subroutine parallel_init >>> use parallel >>> use parser >>> implicit none >>> integer :: ierr >>> integer :: size_real,size_dp >>> >>> ! Initialize a first basic MPI environment >>> >>> !##### This is where it stall out ######### >>> >>> call MPI_INIT(ierr) >>> call MPI_COMM_RANK(MPI_COMM_WORLD,irank,ierr) >>> call MPI_COMM_SIZE(MPI_COMM_WORLD,nproc,ierr) >>> irank = irank+1 >>> iroot = 1 >>> >>> ! Set MPI working precision - WP >>> call MPI_TYPE_SIZE(MPI_REAL,size_real,ierr) >>> call MPI_TYPE_SIZE(MPI_DOUBLE_PRECISION,size_dp,ierr) >>> if (WP .eq. size_real) then >>> MPI_REAL_WP = MPI_REAL >>> else if (WP .eq. size_dp) then >>> MPI_REAL_WP = MPI_DOUBLE_PRECISION >>> else >>> call parallel_kill('Error in parallel_init: no WP equivalent in MPI') >>> end if >>> >>> ! Set MPI single precision >>> call MPI_TYPE_SIZE(MPI_REAL,size_real,ierr) >>> call MPI_TYPE_SIZE(MPI_DOUBLE_PRECISION,size_dp,ierr) >>> if (SP .eq. size_real) then >>> MPI_REAL_SP = MPI_REAL >>> else if (SP .eq. size_dp) then >>> MPI_REAL_SP = MPI_DOUBLE_PRECISION >>> else >>> call parallel_kill('Error in parallel_init: no SP equivalent in MPI') >>> end if >>> >>> ! For now, comm should point to MPI_COMM_WORLD >>> comm = MPI_COMM_WORLD >>> >>> return >>> end subroutine parallel_init >>> >>> ! ============================= ! >>> >>> _______________________________________________ >>> discuss mailing list discuss(a)mpich.org >>> To manage subscription options or unsubscribe: >>> https://lists.mpich.org/mailman/listinfo/discuss >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss > > Ryan Crocker > University of Vermont, School of Engineering > Mechanical Engineering Department > rcrocker(a)uvm.edu > 315-212-7331 > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] Hangup or stall at MPI_INIT
by Ryan Crocker 07 Dec '12

07 Dec '12

I haven't tried that specific example but i don't see the hang when i the use intel compiler sets. I wrote a quick "hello world" and that runs every time, compiled with gfortran. I was thinking it was something to do with running past the node memory but when i check to see how much each core is allocating that's not possible from my code. The other thing i thought to try to day was remove a lot of interface calls from the parallel module and make a stand alone parallel_init module that is the very first thing called, i don't know why that would work but i'm trying it anyway. On Dec 7, 2012, at 8:51 AM, Rajeev Thakur wrote: > Does the pi3f90 example in the examples/f90 directory work? I have had that hang with gfortran for unknown reasons. > > Rajeev > > On Dec 6, 2012, at 11:27 PM, Ryan Crocker wrote: > >> Hi all, >> >> I'm having a problem with hangups or some sort of stall. Basically the program will keep running, or look as it if is on the cluster i'm running on (i've noticed this issue on multiple clusters actually), But nothing is happening. When i have every processor print out they all do right before MPI_INIT and not after. I counted the files and all the processors are entering the call. What makes it even more odd is that the same exact simulation will run if i decrease the number of nodes/cores i'm using, i.e. i'll run on 96 cores (or more) and moving to 72 my program will run without issue. >> >> I'm using the latest gcc compiler set with the latest version of MPICH2 configured with: >> >> '--with-pbs=/PBS' '--with-default-comm=pmi' '--enable-pbspro-helper' 'CC=gcc' 'LDFLAGS=-lpthread' 'CPPFLAGS=-fpic' >> >> I've changed to the intel/mpich2 compiler set and have not had the same problem. I have no idea what this issue could be and have had little luck finding an answer with stackoverflow or google searches any help would be much appreciated. Also, hit me up for any more information you'd need to help. >> >> Thanks, >> >> My flow solver is written in fortran and here are the subroutines leading up to the MPI_INIT call, and the whole flow solver is compiled with '-O3 -ffree-line-length-none' : >> >> ! ====================================== ! >> program main >> >> call main_init >> call simulation_run >> call main_stop >> >> end program main >> >> ! ====================================== ! >> >> subroutine main_init >> use string >> implicit none >> character(len=str_medium) :: input_name >> >> call parallel_init >> >> ! Initialize the random number generator >> call random_init >> >> ! Parse the input file >> call parser_init >> >> input_name='input' >> call parser_parsefile(input_name) >> >> ! Geometry initialization >> call geometry_init >> >> ! Data initialization >> call data_init >> >> ! Simulation initialization >> call simulation_init >> >> return >> end subroutine main_init >> >> ! ====================================== ! >> >> subroutine parallel_init >> use parallel >> use parser >> implicit none >> integer :: ierr >> integer :: size_real,size_dp >> >> ! Initialize a first basic MPI environment >> >> !##### This is where it stall out ######### >> >> call MPI_INIT(ierr) >> call MPI_COMM_RANK(MPI_COMM_WORLD,irank,ierr) >> call MPI_COMM_SIZE(MPI_COMM_WORLD,nproc,ierr) >> irank = irank+1 >> iroot = 1 >> >> ! Set MPI working precision - WP >> call MPI_TYPE_SIZE(MPI_REAL,size_real,ierr) >> call MPI_TYPE_SIZE(MPI_DOUBLE_PRECISION,size_dp,ierr) >> if (WP .eq. size_real) then >> MPI_REAL_WP = MPI_REAL >> else if (WP .eq. size_dp) then >> MPI_REAL_WP = MPI_DOUBLE_PRECISION >> else >> call parallel_kill('Error in parallel_init: no WP equivalent in MPI') >> end if >> >> ! Set MPI single precision >> call MPI_TYPE_SIZE(MPI_REAL,size_real,ierr) >> call MPI_TYPE_SIZE(MPI_DOUBLE_PRECISION,size_dp,ierr) >> if (SP .eq. size_real) then >> MPI_REAL_SP = MPI_REAL >> else if (SP .eq. size_dp) then >> MPI_REAL_SP = MPI_DOUBLE_PRECISION >> else >> call parallel_kill('Error in parallel_init: no SP equivalent in MPI') >> end if >> >> ! For now, comm should point to MPI_COMM_WORLD >> comm = MPI_COMM_WORLD >> >> return >> end subroutine parallel_init >> >> ! ============================= ! >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss Ryan Crocker University of Vermont, School of Engineering Mechanical Engineering Department rcrocker(a)uvm.edu 315-212-7331

1 0

Re: [mpich-discuss] Hangup or stall at MPI_INIT
by Rajeev Thakur 07 Dec '12

07 Dec '12

Does the pi3f90 example in the examples/f90 directory work? I have had that hang with gfortran for unknown reasons. Rajeev On Dec 6, 2012, at 11:27 PM, Ryan Crocker wrote: > Hi all, > > I'm having a problem with hangups or some sort of stall. Basically the program will keep running, or look as it if is on the cluster i'm running on (i've noticed this issue on multiple clusters actually), But nothing is happening. When i have every processor print out they all do right before MPI_INIT and not after. I counted the files and all the processors are entering the call. What makes it even more odd is that the same exact simulation will run if i decrease the number of nodes/cores i'm using, i.e. i'll run on 96 cores (or more) and moving to 72 my program will run without issue. > > I'm using the latest gcc compiler set with the latest version of MPICH2 configured with: > > '--with-pbs=/PBS' '--with-default-comm=pmi' '--enable-pbspro-helper' 'CC=gcc' 'LDFLAGS=-lpthread' 'CPPFLAGS=-fpic' > > I've changed to the intel/mpich2 compiler set and have not had the same problem. I have no idea what this issue could be and have had little luck finding an answer with stackoverflow or google searches any help would be much appreciated. Also, hit me up for any more information you'd need to help. > > Thanks, > > My flow solver is written in fortran and here are the subroutines leading up to the MPI_INIT call, and the whole flow solver is compiled with '-O3 -ffree-line-length-none' : > > ! ====================================== ! > program main > > call main_init > call simulation_run > call main_stop > > end program main > > ! ====================================== ! > > subroutine main_init > use string > implicit none > character(len=str_medium) :: input_name > > call parallel_init > > ! Initialize the random number generator > call random_init > > ! Parse the input file > call parser_init > > input_name='input' > call parser_parsefile(input_name) > > ! Geometry initialization > call geometry_init > > ! Data initialization > call data_init > > ! Simulation initialization > call simulation_init > > return > end subroutine main_init > > ! ====================================== ! > > subroutine parallel_init > use parallel > use parser > implicit none > integer :: ierr > integer :: size_real,size_dp > > ! Initialize a first basic MPI environment > > !##### This is where it stall out ######### > > call MPI_INIT(ierr) > call MPI_COMM_RANK(MPI_COMM_WORLD,irank,ierr) > call MPI_COMM_SIZE(MPI_COMM_WORLD,nproc,ierr) > irank = irank+1 > iroot = 1 > > ! Set MPI working precision - WP > call MPI_TYPE_SIZE(MPI_REAL,size_real,ierr) > call MPI_TYPE_SIZE(MPI_DOUBLE_PRECISION,size_dp,ierr) > if (WP .eq. size_real) then > MPI_REAL_WP = MPI_REAL > else if (WP .eq. size_dp) then > MPI_REAL_WP = MPI_DOUBLE_PRECISION > else > call parallel_kill('Error in parallel_init: no WP equivalent in MPI') > end if > > ! Set MPI single precision > call MPI_TYPE_SIZE(MPI_REAL,size_real,ierr) > call MPI_TYPE_SIZE(MPI_DOUBLE_PRECISION,size_dp,ierr) > if (SP .eq. size_real) then > MPI_REAL_SP = MPI_REAL > else if (SP .eq. size_dp) then > MPI_REAL_SP = MPI_DOUBLE_PRECISION > else > call parallel_kill('Error in parallel_init: no SP equivalent in MPI') > end if > > ! For now, comm should point to MPI_COMM_WORLD > comm = MPI_COMM_WORLD > > return > end subroutine parallel_init > > ! ============================= ! > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0