- discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] install + config on windows
by spatiogis 02 May '13

02 May '13

Hello, in my case Mpich is normally used to run .exe programs. I guess that they are already compiled... The .exe files are integrated into a software, and accessed from menus inside it. When I run one of the programs, the answer is actually "unable to query host". At the end, the process is not realised. It seems that this 'host' question is a problem to the software... Sincerely, Ben. > Hi, > You can download MPICH2 binaries for Windows at > http://www.mpich.org/downloads/ . > You need to compile your MPI programs with MPICH2 to make it work. I > would recommend recompiling your code after you install MPICH2 (If you > have MPI program binaries pre-built with MPICH2 - instead of compiling > them on your own - make sure that you install the same version of MPICH2 > that was used to build the binaries). > The wmpiregister program has a bug and you can ignore this error > message ("...unable to query host"). Can you run your MPI program using > mpiexec from a command prompt? > > Regards, > Jayesh > > ----- Original Message ----- > From: "spatiogis" <geo(a)spatiogis.fr> > To: discuss(a)mpich.org > Sent: Tuesday, April 30, 2013 9:26:35 AM > Subject: [mpich-discuss] install + config on windows > > Hello, > > I'm not very good at computing, but I would like to install Mpich2 on > windows 7 - 64 bits. There is only one pc, with one user plus the admin, > and a simple core processor. > > I would like to know if it's mandatory to have compiling softwares with > it to make it work, whereas it is asked in this case only to make run > another software, and not for compiling (that would maybe save some disk > space and simplify the installation) ? > > My second issue is that I must be missing something about the server > configuration. I have installed Mpich from the .msi file, then configured > the wmpiregister program with the Domain/user informations. > > There is this message displayed when trying to connect in the > 'configurable settings' window : 'MPICH2 not installed or unable to query > the host'. > > What is the host actually ? > > I know I am starting from very far, I am sorry for these very simple > questions. Thanks if you can reply me, that would certainly save me some > long hours of reading and testing ;) > > sincerely, > > Ben > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Benoit Véler Adhérent au groupe JAM Ingénierie 180 Avenue du Genevois, Parc d'Activité de Croix Rousse 73000 Chambéry http://www.spatiogis.fr 06-46-13-40-94

1 0

Re: [mpich-discuss] BLCR kernel module not present
by Wesley Bland 02 May '13

02 May '13

You should be able to add the blcr modules to the list of modules loaded at boot up by editing the file /etc/modules. Just add the names of the modules to the list. Wesley On May 1, 2013, at 1:08 PM, basma a.azeem <basmaabdelazeem(a)hotmail.com> wrote: > Thank you so much for your help > > i used "insmod" to install kernel module for blcr > > "sudo insmod /usr/local/lib/blcr/3.5.0-27-generic/blcr_imports.ko" > "sudo insmod /usr/local/lib/blcr/3.5.0-27-generic/blcr.ko" > > it works but i need to run these commands every time i shut down > i think that there is a method to have them installed permanently > > i am new to Linux and parallel programming also > > i need to find long running c/mpi applications to test blcr , the applications i will use > to test blcr should have an enough long execution time , i found many applications but with a short execution time . > > thank you > > > From: wbland(a)mcs.anl.gov > Date: Fri, 26 Apr 2013 14:33:59 -0500 > To: discuss(a)mpich.org > Subject: Re: [mpich-discuss] BLCR kernel module not present > > It looks like you might have missed installing the kernel module for BLCR. What is the output of `lsmod`? > > Alternatively, if you installed BLCR by using apt-get in Ubuntu, you should be able to use dkms to manage your kernel modules automatically. Make sure you have the package 'blcr-dkms' installed (you should be able to check this by typing `dims status`. > > Do either of those solutions solve your issue? > > Wesley > > On Apr 26, 2013, at 1:55 PM, basma a.azeem <basmaabdelazeem(a)hotmail.com> wrote: > > > > Thank you for your help > > > i installed BLCR 0.8.5 on my ubuntu 12.10 to be used for MPICH -3.0.3 > this version of blcr should support to kernels through 3.7.1 > > when i run the command : > basma@basma-Satellite-A500:~$ mpiexec --info > > results: > > HYDRA build details: > Version: 3.0.3 > Release Date: Thu Mar 28 16:01:21 CDT 2013 > CC: gcc > CXX: c++ > F77: no > F90: no > Configure options: '--disable-option-checking' '--prefix=/home/basma/mpich2-install' '--disable-f77' '--disable-fc' '--enable-checkpointing' '--with-hydra-ckpointlib=blcr' '--cache-file=/dev/null' '--srcdir=.' 'CC=gcc' 'CFLAGS= -O2' 'LDFLAGS= ' 'LIBS=-lrt -lcr -lpthread ' 'CPPFLAGS= -I/home/basma/libraries/mpich-3.0.3/src/mpl/include -I/home/basma/libraries/mpich-3.0.3/src/mpl/include -I/home/basma/libraries/mpich-3.0.3/src/openpa/src -I/home/basma/libraries/mpich-3.0.3/src/openpa/src -I/home/basma/libraries/mpich-3.0.3/src/mpi/romio/include' > Process Manager: pmi > Launchers available: ssh rsh fork slurm ll lsf sge manual persist > Topology libraries available: hwloc > Resource management kernels available: user slurm ll lsf sge pbs cobalt > Checkpointing libraries available: blcr > Demux engines available: poll select > > so i thought that every thing is ok but when i try to rum mpiexec it failed: > > basma@basma-Satellite-A500:~$ mpiexec -ckpointlib blcr -ckpoint-prefix /home/business/ckpts/app.ckpoint -ckpoint-interval 3600 -n 4 /home/basma/libraries/mpich-3.0.3/examples/cpi > > results: > > Fatal error in MPI_Init: Other MPI error, error stack: > MPIR_Init_thread(433)...: > MPID_Init(151)..........: channel initialization failed > MPIDI_CH3_Init(70)......: > MPID_nem_init(379)......: > MPIDI_nem_ckpt_init(153): BLCR kernel module not present > Fatal error in MPI_Init: Other MPI error, error stack: > MPIR_Init_thread(433)...: > MPID_Init(151)..........: channel initialization failed > MPIDI_CH3_Init(70)......: > MPID_nem_init(379)......: > MPIDI_nem_ckpt_init(153): BLCR kernel module not present > Fatal error in MPI_Init: Other MPI error, error stack: > MPIR_Init_thread(433)...: > MPID_Init(151)..........: channel initialization failed > MPIDI_CH3_Init(70)......: > MPID_nem_init(379)......: > MPIDI_nem_ckpt_init(153): BLCR kernel module not present > Fatal error in MPI_Init: Other MPI error, error stack: > MPIR_Init_thread(433)...: > MPID_Init(151)..........: channel initialization failed > MPIDI_CH3_Init(70)......: > MPID_nem_init(379)......: > MPIDI_nem_ckpt_init(153): BLCR kernel module not present > > =================================================================================== > = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES > = EXIT CODE: 1 > = CLEANING UP REMAINING PROCESSES > = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES > =================================================================================== > > > > i am a Linux and parallel programming beginner > > Thank you > > > _______________________________________________ > 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 > _______________________________________________ > 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] Network drive recognition problems by mpiexec
by Jayesh Krishna 02 May '13

02 May '13

Hi, Are the network drives accessible by the user launching the job (registered with mpiexec)? Try manually mapping the network drive, as the user registered with mpiexec, to make sure it works. Regards, Jayesh ----- Original Message ----- From: "Robert Bauer" <Robert.Bauer(a)iconplc.com> To: discuss(a)mpich.org Sent: Wednesday, May 1, 2013 6:19:19 PM Subject: [mpich-discuss] Network drive recognition problems by mpiexec The mpiexec program on a windows environment does not recognize networked drives despite my attempts at using –map and –mapall. Can anyone provide suggestions? Robert J. Bauer, Ph.D. Vice President, Pharmacometrics, R&D ICON Development Solutions 7740 Milestone Parkway Suite 150 Hanover, MD 21076 Tel: (215) 616-6428 Mob: (925) 286-0769 Email: Robert.Bauer(a)iconplc.com Web: www.iconplc.com ICON plc made the following annotations. ------------------------------------------------------------------------------ This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that ICON plc can arrange for proper delivery, and then please delete the message. Thank You, ICON plc South County Business Park Leopardstown Dublin 18 Ireland Registered number: 145835 ICON plc made the following annotations. ------------------------------------------------------------------------------ This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that ICON plc can arrange for proper delivery, and then please delete the message. Thank You, ICON plc South County Business Park Leopardstown Dublin 18 Ireland Registered number: 145835 _______________________________________________ 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] Error while connecting to the host
by Pavan Balaji 02 May '13

02 May '13

Hello, SMPD and windows are not supported any more within mpich. Please use Microsoft's MS-MPI, which is freely available. -- Pavan On 05/02/2013 01:48 AM US Central Time, Zana Karimi wrote: > Hi, > > I have a problem running my parallel program using MPICH2. I was > wondering if you could help me! > When I run mpiexec I get this error: > > ERROR:Connect on sock (host=ZANA-PC 192.168.1.13 , port=1472) > failed, exhaused all end points > SMPDU_Sock_post_connect failed. > > I will appreciate any help, > > Thanks in advance, > > Zana, > > > -- > ------------------------------------------------------------------------------------------- > ------------------------------------------------------------------------------------------- > *Zana Karimi* > Graduate Research Student, University of Colorado at Boulder > Email: karimi.zana(a)gmail.com <mailto:[email protected]>, > Zana.Karimi(a)colorado.edu <mailto:[email protected]> > > > > > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > -- Pavan Balaji http://www.mcs.anl.gov/~balaji

1 0

Error while connecting to the host
by Zana Karimi 02 May '13

02 May '13

Hi, I have a problem running my parallel program using MPICH2. I was wondering if you could help me! When I run mpiexec I get this error: ERROR:Connect on sock (host=ZANA-PC 192.168.1.13 , port=1472) failed, exhaused all end points SMPDU_Sock_post_connect failed. I will appreciate any help, Thanks in advance, Zana, -- ------------------------------------------------------------------------------------------- ------------------------------------------------------------------------------------------- *Zana Karimi* Graduate Research Student, University of Colorado at Boulder Email: karimi.zana(a)gmail.com, Zana.Karimi(a)colorado.edu

1 0

Re: [mpich-discuss] gather, send
by Ryan Crocker 01 May '13

01 May '13

I dropped down to two processes to debug: the quick check: print*,'send_buffer',irank,maxval(send_buffer),minval(send_buffer) print*,'gsend_buffer',irank,maxval(gsend_buffer),minval(gsend_buffer) send_buffer 1 1.0000000000000000 0.0000000000000000 send_buffer 2 1.0000000000000000 0.0000000000000000 gsend_buffer 2 0.0000000000000000 0.0000000000000000 gsend_buffer 1 0.0000000000000000 0.0000000000000000 long print check: do k=kmin_,kmax_ do j=gy_wmin-1,gy_wmax+1 do i=imin_,imax_ print*,irank,i,j,k,send_buffer(nodes_n(i,j,k)),gsend_buffer(nodes_n(i,j,k)) end do end do end do 1 6 50 6 0.0000000000000000 0.0000000000000000 1 7 50 6 0.0000000000000000 0.0000000000000000 1 8 50 6 0.0000000000000000 0.0000000000000000 1 9 50 6 0.0000000000000000 0.0000000000000000 2 26 50 6 0.0000000000000000 0.0000000000000000 2 27 50 6 0.0000000000000000 0.0000000000000000 2 28 50 6 0.0000000000000000 0.0000000000000000 2 29 50 6 0.0000000000000000 0.0000000000000000 2 30 50 6 0.0000000000000000 0.0000000000000000 2 31 50 6 0.0000000000000000 0.0000000000000000 2 32 50 6 0.0000000000000000 0.0000000000000000 2 33 50 6 0.0000000000000000 0.0000000000000000 2 34 50 6 0.0000000000000000 0.0000000000000000 1 10 50 6 0.0000000000000000 0.0000000000000000 2 35 50 6 0.0000000000000000 0.0000000000000000 2 36 50 6 0.0000000000000000 0.0000000000000000 2 37 50 6 0.0000000000000000 0.0000000000000000 2 38 50 6 0.0000000000000000 0.0000000000000000 2 39 50 6 0.0000000000000000 0.0000000000000000 2 40 50 6 0.0000000000000000 0.0000000000000000 2 41 50 6 0.0000000000000000 0.0000000000000000 2 42 50 6 0.0000000000000000 0.0000000000000000 2 43 50 6 0.0000000000000000 0.0000000000000000 2 44 50 6 0.0000000000000000 0.0000000000000000 2 45 50 6 0.0000000000000000 0.0000000000000000 2 26 51 6 1.0000000000000000 0.0000000000000000 2 27 51 6 1.0000000000000000 0.0000000000000000 2 28 51 6 1.0000000000000000 0.0000000000000000 2 29 51 6 1.0000000000000000 0.0000000000000000 2 30 51 6 1.0000000000000000 0.0000000000000000 2 31 51 6 1.0000000000000000 0.0000000000000000 2 32 51 6 1.0000000000000000 0.0000000000000000 2 33 51 6 1.0000000000000000 0.0000000000000000 2 34 51 6 1.0000000000000000 0.0000000000000000 2 35 51 6 1.0000000000000000 0.0000000000000000 2 36 51 6 1.0000000000000000 0.0000000000000000 2 37 51 6 1.0000000000000000 0.0000000000000000 2 38 51 6 1.0000000000000000 0.0000000000000000 2 39 51 6 1.0000000000000000 0.0000000000000000 2 40 51 6 1.0000000000000000 0.0000000000000000 2 41 51 6 1.0000000000000000 0.0000000000000000 2 42 51 6 1.0000000000000000 0.0000000000000000 2 43 51 6 1.0000000000000000 0.0000000000000000 2 44 51 6 1.0000000000000000 0.0000000000000000 2 45 51 6 1.0000000000000000 0.0000000000000000 2 26 52 6 0.0000000000000000 0.0000000000000000 1 11 50 6 0.0000000000000000 0.0000000000000000 1 12 50 6 0.0000000000000000 0.0000000000000000 1 13 50 6 0.0000000000000000 0.0000000000000000 1 14 50 6 0.0000000000000000 0.0000000000000000 1 15 50 6 0.0000000000000000 0.0000000000000000 1 16 50 6 0.0000000000000000 0.0000000000000000 1 17 50 6 0.0000000000000000 0.0000000000000000 1 18 50 6 0.0000000000000000 0.0000000000000000 1 19 50 6 0.0000000000000000 0.0000000000000000 1 20 50 6 0.0000000000000000 0.0000000000000000 1 21 50 6 0.0000000000000000 0.0000000000000000 1 22 50 6 0.0000000000000000 0.0000000000000000 1 23 50 6 0.0000000000000000 0.0000000000000000 1 24 50 6 0.0000000000000000 0.0000000000000000 1 25 50 6 0.0000000000000000 0.0000000000000000 1 6 51 6 1.0000000000000000 0.0000000000000000 1 7 51 6 1.0000000000000000 0.0000000000000000 1 8 51 6 1.0000000000000000 0.0000000000000000 1 9 51 6 1.0000000000000000 0.0000000000000000 1 10 51 6 1.0000000000000000 0.0000000000000000 1 11 51 6 1.0000000000000000 0.0000000000000000 1 12 51 6 1.0000000000000000 0.0000000000000000 1 13 51 6 1.0000000000000000 0.0000000000000000 1 14 51 6 1.0000000000000000 0.0000000000000000 1 15 51 6 1.0000000000000000 0.0000000000000000 1 16 51 6 1.0000000000000000 0.0000000000000000 1 17 51 6 1.0000000000000000 0.0000000000000000 1 18 51 6 1.0000000000000000 0.0000000000000000 1 19 51 6 1.0000000000000000 0.0000000000000000 1 20 51 6 1.0000000000000000 0.0000000000000000 1 21 51 6 1.0000000000000000 0.0000000000000000 1 22 51 6 1.0000000000000000 0.0000000000000000 1 23 51 6 1.0000000000000000 0.0000000000000000 1 24 51 6 1.0000000000000000 0.0000000000000000 1 25 51 6 1.0000000000000000 0.0000000000000000 1 6 52 6 0.0000000000000000 0.0000000000000000 1 7 52 6 0.0000000000000000 0.0000000000000000 1 8 52 6 0.0000000000000000 0.0000000000000000 1 9 52 6 0.0000000000000000 0.0000000000000000 1 10 52 6 0.0000000000000000 0.0000000000000000 1 11 52 6 0.0000000000000000 0.0000000000000000 1 12 52 6 0.0000000000000000 0.0000000000000000 1 13 52 6 0.0000000000000000 0.0000000000000000 1 14 52 6 0.0000000000000000 0.0000000000000000 1 15 52 6 0.0000000000000000 0.0000000000000000 1 16 52 6 0.0000000000000000 0.0000000000000000 1 17 52 6 0.0000000000000000 0.0000000000000000 1 18 52 6 0.0000000000000000 0.0000000000000000 1 19 52 6 0.0000000000000000 0.0000000000000000 1 20 52 6 0.0000000000000000 0.0000000000000000 1 21 52 6 0.0000000000000000 0.0000000000000000 1 22 52 6 0.0000000000000000 0.0000000000000000 1 23 52 6 0.0000000000000000 0.0000000000000000 1 24 52 6 0.0000000000000000 0.0000000000000000 1 25 52 6 0.0000000000000000 0.0000000000000000 2 27 52 6 0.0000000000000000 0.0000000000000000 2 28 52 6 0.0000000000000000 0.0000000000000000 2 29 52 6 0.0000000000000000 0.0000000000000000 2 30 52 6 0.0000000000000000 0.0000000000000000 2 31 52 6 0.0000000000000000 0.0000000000000000 2 32 52 6 0.0000000000000000 0.0000000000000000 2 33 52 6 0.0000000000000000 0.0000000000000000 2 34 52 6 0.0000000000000000 0.0000000000000000 2 35 52 6 0.0000000000000000 0.0000000000000000 2 36 52 6 0.0000000000000000 0.0000000000000000 2 37 52 6 0.0000000000000000 0.0000000000000000 2 38 52 6 0.0000000000000000 0.0000000000000000 2 39 52 6 0.0000000000000000 0.0000000000000000 2 40 52 6 0.0000000000000000 0.0000000000000000 2 41 52 6 0.0000000000000000 0.0000000000000000 2 42 52 6 0.0000000000000000 0.0000000000000000 2 43 52 6 0.0000000000000000 0.0000000000000000 2 44 52 6 0.0000000000000000 0.0000000000000000 2 45 52 6 0.0000000000000000 0.0000000000000000 On May 1, 2013, at 5:34 PM, Rajeev Thakur wrote: > The gather is sending everything to real rank 1. Since you have incremented irank, you need to print the values at irank=2. > > On May 1, 2013, at 7:31 PM, Ryan Crocker wrote: > >> my call for the memory allocation for the buffers: >> >> call parallel_min_int_0d(imaxo_*jmaxo_*kmaxo_,max_buff) >> allocate(send_buffer(max_buff)) >> max_global_buff = max_buff*nproc >> allocate(gsend_buffer (max_global_buff)) >> >> in my mpi init subroutine: >> >> >> 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 >> >> >> On May 1, 2013, at 5:21 PM, Rajeev Thakur wrote: >> >>> Is the send_buffer allocated to be large enough to hold max_buff on all ranks? >>> >>> Is gsend_buffer large enough to hold max_buff * nprocs? >>> >>> Is the rank 1, not rank 0, the root? >>> >>> On May 1, 2013, at 7:16 PM, Ryan Crocker wrote: >>> >>>> i'm just checking just the gather call, and the gsend_buffer from the gather call is still empty: >>>> >>>> max_buff is now the largest core domain. >>>> >>>> print*,max_buff -> 24750 >>>> >>>> call MPI_GATHER(send_buffer, max_buff, MPI_REAL, gsend_buffer, max_buff, MPI_REAL, iroot, comm, ierr) >>>> >>>> a print out of the send_buffer and the gsend_buffer where it should have non-zero terms. >>>> >>>> print*,irank,i,j,k,send_buffer(i,j,k),gsent_buffer(i,j,k) -> >>>> >>>> 1 6 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 7 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 8 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 9 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 10 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 11 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 12 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 13 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 14 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 15 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 16 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 17 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 18 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 19 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 20 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 21 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 22 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 23 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 24 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 25 50 6 0.0000000000000000 0.0000000000000000 >>>> 1 6 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 7 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 8 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 9 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 10 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 11 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 12 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 13 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 14 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 15 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 16 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 17 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 18 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 19 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 20 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 21 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 22 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 23 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 24 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 25 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 6 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 7 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 8 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 9 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 10 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 11 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 12 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 13 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 14 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 15 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 16 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 17 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 18 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 19 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 20 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 21 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 22 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 23 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 24 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 25 51 6 1.0000000000000000 0.0000000000000000 >>>> 1 6 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 7 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 8 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 9 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 10 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 11 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 12 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 13 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 14 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 15 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 16 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 17 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 18 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 19 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 20 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 21 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 22 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 23 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 24 52 6 0.0000000000000000 0.0000000000000000 >>>> 1 25 52 6 0.0000000000000000 0.0000000000000000 >>>> >>>> >>>> On May 1, 2013, at 5:06 PM, Rajeev Thakur wrote: >>>> >>>>> Just before the call to gather, check the value of send_count and check that send_buffer is not all zeros. >>>>> >>>>> send_count has to be the same on all ranks. Otherwise you have to use Gatherv. >>>>> >>>>> On May 1, 2013, at 7:03 PM, Ryan Crocker wrote: >>>>> >>>>>> that's where i checked it with and it's min and max are still zero. I just amended it so that each send buffer from the different cores are the same size and when i check it on the root gsend_buffer is still incorrect. >>>>>> >>>>>> On May 1, 2013, at 5:00 PM, Rajeev Thakur wrote: >>>>>> >>>>>>> gsend_buffer will be valid only on the root. >>>>>>> >>>>>>> On May 1, 2013, at 6:55 PM, Ryan Crocker wrote: >>>>>>> >>>>>>>> I just looked at the gsend_buffer, that's actually all zeros as well, and each send_buffer is not. So i think my problem is there. >>>>>>>> >>>>>>>> On May 1, 2013, at 4:47 PM, Rajeev Thakur wrote: >>>>>>>> >>>>>>>>> The count passed to MPI_Scatter should be the local size, i.e., the amount that gets sent to each process. Looks like what is being passed is the global size. >>>>>>>>> >>>>>>>>> On May 1, 2013, at 6:21 PM, Ryan Crocker wrote: >>>>>>>>> >>>>>>>>>> Hi all, >>>>>>>>>> >>>>>>>>>> So i don't know what the issue with this code snippet is but i cannot get the scatter call to work. When i print out the recieve_buffer it comes out as all zeros. The counters without the underscore are the core domains, with the o, the global domains. >>>>>>>>>> >>>>>>>>>> rec_count = (imaxo-imino+1)*(jmaxo-jmino+1)*(kmaxo-kmino+1) >>>>>>>>>> send_count = (imax_-imin_+1)*(jmax_-jmin_+1)*(kmax_-kmin_+1) >>>>>>>>>> >>>>>>>>>> call MPI_GATHER (send_buffer, send_count, MPI_REAL, gsend_buffer, send_count, MPI_REAL, iroot, comm, ierr) >>>>>>>>>> >>>>>>>>>> rec_count = (imaxo-imino+1)*(jmaxo-jmino+1)*(kmaxo-kmino+1) >>>>>>>>>> send_count = (imaxo-imino+1)*(jmaxo-jmino+1)*(kmaxo-kmino+1) >>>>>>>>>> >>>>>>>>>> call MPI_SCATTER (gsend_buffer, send_count, MPI_REAL, recieve_buffer, rec_count, MPI_REAL, iroot, comm, ierr) >>>>>>>>>> >>>>>>>>>> thanks for the help. >>>>>>>>>> >>>>>>>>>> Ryan Crocker >>>>>>>>>> University of Vermont, School of Engineering >>>>>>>>>> Mechanical Engineering Department >>>>>>>>>> rcrocker(a)uvm.edu >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >>> _______________________________________________ >>> 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 > > _______________________________________________ > 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] gather, send
by Rajeev Thakur 01 May '13

01 May '13

The gather is sending everything to real rank 1. Since you have incremented irank, you need to print the values at irank=2. On May 1, 2013, at 7:31 PM, Ryan Crocker wrote: > my call for the memory allocation for the buffers: > > call parallel_min_int_0d(imaxo_*jmaxo_*kmaxo_,max_buff) > allocate(send_buffer(max_buff)) > max_global_buff = max_buff*nproc > allocate(gsend_buffer (max_global_buff)) > > in my mpi init subroutine: > > > 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 > > > On May 1, 2013, at 5:21 PM, Rajeev Thakur wrote: > >> Is the send_buffer allocated to be large enough to hold max_buff on all ranks? >> >> Is gsend_buffer large enough to hold max_buff * nprocs? >> >> Is the rank 1, not rank 0, the root? >> >> On May 1, 2013, at 7:16 PM, Ryan Crocker wrote: >> >>> i'm just checking just the gather call, and the gsend_buffer from the gather call is still empty: >>> >>> max_buff is now the largest core domain. >>> >>> print*,max_buff -> 24750 >>> >>> call MPI_GATHER(send_buffer, max_buff, MPI_REAL, gsend_buffer, max_buff, MPI_REAL, iroot, comm, ierr) >>> >>> a print out of the send_buffer and the gsend_buffer where it should have non-zero terms. >>> >>> print*,irank,i,j,k,send_buffer(i,j,k),gsent_buffer(i,j,k) -> >>> >>> 1 6 50 6 0.0000000000000000 0.0000000000000000 >>> 1 7 50 6 0.0000000000000000 0.0000000000000000 >>> 1 8 50 6 0.0000000000000000 0.0000000000000000 >>> 1 9 50 6 0.0000000000000000 0.0000000000000000 >>> 1 10 50 6 0.0000000000000000 0.0000000000000000 >>> 1 11 50 6 0.0000000000000000 0.0000000000000000 >>> 1 12 50 6 0.0000000000000000 0.0000000000000000 >>> 1 13 50 6 0.0000000000000000 0.0000000000000000 >>> 1 14 50 6 0.0000000000000000 0.0000000000000000 >>> 1 15 50 6 0.0000000000000000 0.0000000000000000 >>> 1 16 50 6 0.0000000000000000 0.0000000000000000 >>> 1 17 50 6 0.0000000000000000 0.0000000000000000 >>> 1 18 50 6 0.0000000000000000 0.0000000000000000 >>> 1 19 50 6 0.0000000000000000 0.0000000000000000 >>> 1 20 50 6 0.0000000000000000 0.0000000000000000 >>> 1 21 50 6 0.0000000000000000 0.0000000000000000 >>> 1 22 50 6 0.0000000000000000 0.0000000000000000 >>> 1 23 50 6 0.0000000000000000 0.0000000000000000 >>> 1 24 50 6 0.0000000000000000 0.0000000000000000 >>> 1 25 50 6 0.0000000000000000 0.0000000000000000 >>> 1 6 51 6 1.0000000000000000 0.0000000000000000 >>> 1 7 51 6 1.0000000000000000 0.0000000000000000 >>> 1 8 51 6 1.0000000000000000 0.0000000000000000 >>> 1 9 51 6 1.0000000000000000 0.0000000000000000 >>> 1 10 51 6 1.0000000000000000 0.0000000000000000 >>> 1 11 51 6 1.0000000000000000 0.0000000000000000 >>> 1 12 51 6 1.0000000000000000 0.0000000000000000 >>> 1 13 51 6 1.0000000000000000 0.0000000000000000 >>> 1 14 51 6 1.0000000000000000 0.0000000000000000 >>> 1 15 51 6 1.0000000000000000 0.0000000000000000 >>> 1 16 51 6 1.0000000000000000 0.0000000000000000 >>> 1 17 51 6 1.0000000000000000 0.0000000000000000 >>> 1 18 51 6 1.0000000000000000 0.0000000000000000 >>> 1 19 51 6 1.0000000000000000 0.0000000000000000 >>> 1 20 51 6 1.0000000000000000 0.0000000000000000 >>> 1 21 51 6 1.0000000000000000 0.0000000000000000 >>> 1 22 51 6 1.0000000000000000 0.0000000000000000 >>> 1 23 51 6 1.0000000000000000 0.0000000000000000 >>> 1 24 51 6 1.0000000000000000 0.0000000000000000 >>> 1 25 51 6 1.0000000000000000 0.0000000000000000 >>> 1 6 52 6 0.0000000000000000 0.0000000000000000 >>> 1 7 52 6 0.0000000000000000 0.0000000000000000 >>> 1 8 52 6 0.0000000000000000 0.0000000000000000 >>> 1 9 52 6 0.0000000000000000 0.0000000000000000 >>> 1 10 52 6 0.0000000000000000 0.0000000000000000 >>> 1 11 52 6 0.0000000000000000 0.0000000000000000 >>> 1 12 52 6 0.0000000000000000 0.0000000000000000 >>> 1 13 52 6 0.0000000000000000 0.0000000000000000 >>> 1 14 52 6 0.0000000000000000 0.0000000000000000 >>> 1 15 52 6 0.0000000000000000 0.0000000000000000 >>> 1 16 52 6 0.0000000000000000 0.0000000000000000 >>> 1 17 52 6 0.0000000000000000 0.0000000000000000 >>> 1 18 52 6 0.0000000000000000 0.0000000000000000 >>> 1 19 52 6 0.0000000000000000 0.0000000000000000 >>> 1 20 52 6 0.0000000000000000 0.0000000000000000 >>> 1 21 52 6 0.0000000000000000 0.0000000000000000 >>> 1 22 51 6 1.0000000000000000 0.0000000000000000 >>> 1 23 51 6 1.0000000000000000 0.0000000000000000 >>> 1 24 51 6 1.0000000000000000 0.0000000000000000 >>> 1 25 51 6 1.0000000000000000 0.0000000000000000 >>> 1 6 52 6 0.0000000000000000 0.0000000000000000 >>> 1 7 52 6 0.0000000000000000 0.0000000000000000 >>> 1 8 52 6 0.0000000000000000 0.0000000000000000 >>> 1 9 52 6 0.0000000000000000 0.0000000000000000 >>> 1 10 52 6 0.0000000000000000 0.0000000000000000 >>> 1 11 52 6 0.0000000000000000 0.0000000000000000 >>> 1 12 52 6 0.0000000000000000 0.0000000000000000 >>> 1 13 52 6 0.0000000000000000 0.0000000000000000 >>> 1 14 52 6 0.0000000000000000 0.0000000000000000 >>> 1 15 52 6 0.0000000000000000 0.0000000000000000 >>> 1 16 52 6 0.0000000000000000 0.0000000000000000 >>> 1 17 52 6 0.0000000000000000 0.0000000000000000 >>> 1 18 52 6 0.0000000000000000 0.0000000000000000 >>> 1 19 52 6 0.0000000000000000 0.0000000000000000 >>> 1 20 52 6 0.0000000000000000 0.0000000000000000 >>> 1 21 52 6 0.0000000000000000 0.0000000000000000 >>> 1 22 52 6 0.0000000000000000 0.0000000000000000 >>> 1 23 52 6 0.0000000000000000 0.0000000000000000 >>> 1 24 52 6 0.0000000000000000 0.0000000000000000 >>> 1 25 52 6 0.0000000000000000 0.0000000000000000 >>> >>> >>> On May 1, 2013, at 5:06 PM, Rajeev Thakur wrote: >>> >>>> Just before the call to gather, check the value of send_count and check that send_buffer is not all zeros. >>>> >>>> send_count has to be the same on all ranks. Otherwise you have to use Gatherv. >>>> >>>> On May 1, 2013, at 7:03 PM, Ryan Crocker wrote: >>>> >>>>> that's where i checked it with and it's min and max are still zero. I just amended it so that each send buffer from the different cores are the same size and when i check it on the root gsend_buffer is still incorrect. >>>>> >>>>> On May 1, 2013, at 5:00 PM, Rajeev Thakur wrote: >>>>> >>>>>> gsend_buffer will be valid only on the root. >>>>>> >>>>>> On May 1, 2013, at 6:55 PM, Ryan Crocker wrote: >>>>>> >>>>>>> I just looked at the gsend_buffer, that's actually all zeros as well, and each send_buffer is not. So i think my problem is there. >>>>>>> >>>>>>> On May 1, 2013, at 4:47 PM, Rajeev Thakur wrote: >>>>>>> >>>>>>>> The count passed to MPI_Scatter should be the local size, i.e., the amount that gets sent to each process. Looks like what is being passed is the global size. >>>>>>>> >>>>>>>> On May 1, 2013, at 6:21 PM, Ryan Crocker wrote: >>>>>>>> >>>>>>>>> Hi all, >>>>>>>>> >>>>>>>>> So i don't know what the issue with this code snippet is but i cannot get the scatter call to work. When i print out the recieve_buffer it comes out as all zeros. The counters without the underscore are the core domains, with the o, the global domains. >>>>>>>>> >>>>>>>>> rec_count = (imaxo-imino+1)*(jmaxo-jmino+1)*(kmaxo-kmino+1) >>>>>>>>> send_count = (imax_-imin_+1)*(jmax_-jmin_+1)*(kmax_-kmin_+1) >>>>>>>>> >>>>>>>>> call MPI_GATHER (send_buffer, send_count, MPI_REAL, gsend_buffer, send_count, MPI_REAL, iroot, comm, ierr) >>>>>>>>> >>>>>>>>> rec_count = (imaxo-imino+1)*(jmaxo-jmino+1)*(kmaxo-kmino+1) >>>>>>>>> send_count = (imaxo-imino+1)*(jmaxo-jmino+1)*(kmaxo-kmino+1) >>>>>>>>> >>>>>>>>> call MPI_SCATTER (gsend_buffer, send_count, MPI_REAL, recieve_buffer, rec_count, MPI_REAL, iroot, comm, ierr) >>>>>>>>> >>>>>>>>> thanks for the help. >>>>>>>>> >>>>>>>>> Ryan Crocker >>>>>>>>> University of Vermont, School of Engineering >>>>>>>>> Mechanical Engineering Department >>>>>>>>> rcrocker(a)uvm.edu >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>> >>>> _______________________________________________ >>>> 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 >> >> _______________________________________________ >> 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] gather, send
by Ryan Crocker 01 May '13

01 May '13

my call for the memory allocation for the buffers: call parallel_min_int_0d(imaxo_*jmaxo_*kmaxo_,max_buff) allocate(send_buffer(max_buff)) max_global_buff = max_buff*nproc allocate(gsend_buffer (max_global_buff)) in my mpi init subroutine: 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 On May 1, 2013, at 5:21 PM, Rajeev Thakur wrote: > Is the send_buffer allocated to be large enough to hold max_buff on all ranks? > > Is gsend_buffer large enough to hold max_buff * nprocs? > > Is the rank 1, not rank 0, the root? > > On May 1, 2013, at 7:16 PM, Ryan Crocker wrote: > >> i'm just checking just the gather call, and the gsend_buffer from the gather call is still empty: >> >> max_buff is now the largest core domain. >> >> print*,max_buff -> 24750 >> >> call MPI_GATHER(send_buffer, max_buff, MPI_REAL, gsend_buffer, max_buff, MPI_REAL, iroot, comm, ierr) >> >> a print out of the send_buffer and the gsend_buffer where it should have non-zero terms. >> >> print*,irank,i,j,k,send_buffer(i,j,k),gsent_buffer(i,j,k) -> >> >> 1 6 50 6 0.0000000000000000 0.0000000000000000 >> 1 7 50 6 0.0000000000000000 0.0000000000000000 >> 1 8 50 6 0.0000000000000000 0.0000000000000000 >> 1 9 50 6 0.0000000000000000 0.0000000000000000 >> 1 10 50 6 0.0000000000000000 0.0000000000000000 >> 1 11 50 6 0.0000000000000000 0.0000000000000000 >> 1 12 50 6 0.0000000000000000 0.0000000000000000 >> 1 13 50 6 0.0000000000000000 0.0000000000000000 >> 1 14 50 6 0.0000000000000000 0.0000000000000000 >> 1 15 50 6 0.0000000000000000 0.0000000000000000 >> 1 16 50 6 0.0000000000000000 0.0000000000000000 >> 1 17 50 6 0.0000000000000000 0.0000000000000000 >> 1 18 50 6 0.0000000000000000 0.0000000000000000 >> 1 19 50 6 0.0000000000000000 0.0000000000000000 >> 1 20 50 6 0.0000000000000000 0.0000000000000000 >> 1 21 50 6 0.0000000000000000 0.0000000000000000 >> 1 22 50 6 0.0000000000000000 0.0000000000000000 >> 1 23 50 6 0.0000000000000000 0.0000000000000000 >> 1 24 50 6 0.0000000000000000 0.0000000000000000 >> 1 25 50 6 0.0000000000000000 0.0000000000000000 >> 1 6 51 6 1.0000000000000000 0.0000000000000000 >> 1 7 51 6 1.0000000000000000 0.0000000000000000 >> 1 8 51 6 1.0000000000000000 0.0000000000000000 >> 1 9 51 6 1.0000000000000000 0.0000000000000000 >> 1 10 51 6 1.0000000000000000 0.0000000000000000 >> 1 11 51 6 1.0000000000000000 0.0000000000000000 >> 1 12 51 6 1.0000000000000000 0.0000000000000000 >> 1 13 51 6 1.0000000000000000 0.0000000000000000 >> 1 14 51 6 1.0000000000000000 0.0000000000000000 >> 1 15 51 6 1.0000000000000000 0.0000000000000000 >> 1 16 51 6 1.0000000000000000 0.0000000000000000 >> 1 17 51 6 1.0000000000000000 0.0000000000000000 >> 1 18 51 6 1.0000000000000000 0.0000000000000000 >> 1 19 51 6 1.0000000000000000 0.0000000000000000 >> 1 20 51 6 1.0000000000000000 0.0000000000000000 >> 1 21 51 6 1.0000000000000000 0.0000000000000000 >> 1 22 51 6 1.0000000000000000 0.0000000000000000 >> 1 23 51 6 1.0000000000000000 0.0000000000000000 >> 1 24 51 6 1.0000000000000000 0.0000000000000000 >> 1 25 51 6 1.0000000000000000 0.0000000000000000 >> 1 6 52 6 0.0000000000000000 0.0000000000000000 >> 1 7 52 6 0.0000000000000000 0.0000000000000000 >> 1 8 52 6 0.0000000000000000 0.0000000000000000 >> 1 9 52 6 0.0000000000000000 0.0000000000000000 >> 1 10 52 6 0.0000000000000000 0.0000000000000000 >> 1 11 52 6 0.0000000000000000 0.0000000000000000 >> 1 12 52 6 0.0000000000000000 0.0000000000000000 >> 1 13 52 6 0.0000000000000000 0.0000000000000000 >> 1 14 52 6 0.0000000000000000 0.0000000000000000 >> 1 15 52 6 0.0000000000000000 0.0000000000000000 >> 1 16 52 6 0.0000000000000000 0.0000000000000000 >> 1 17 52 6 0.0000000000000000 0.0000000000000000 >> 1 18 52 6 0.0000000000000000 0.0000000000000000 >> 1 19 52 6 0.0000000000000000 0.0000000000000000 >> 1 20 52 6 0.0000000000000000 0.0000000000000000 >> 1 21 52 6 0.0000000000000000 0.0000000000000000 >> 1 22 51 6 1.0000000000000000 0.0000000000000000 >> 1 23 51 6 1.0000000000000000 0.0000000000000000 >> 1 24 51 6 1.0000000000000000 0.0000000000000000 >> 1 25 51 6 1.0000000000000000 0.0000000000000000 >> 1 6 52 6 0.0000000000000000 0.0000000000000000 >> 1 7 52 6 0.0000000000000000 0.0000000000000000 >> 1 8 52 6 0.0000000000000000 0.0000000000000000 >> 1 9 52 6 0.0000000000000000 0.0000000000000000 >> 1 10 52 6 0.0000000000000000 0.0000000000000000 >> 1 11 52 6 0.0000000000000000 0.0000000000000000 >> 1 12 52 6 0.0000000000000000 0.0000000000000000 >> 1 13 52 6 0.0000000000000000 0.0000000000000000 >> 1 14 52 6 0.0000000000000000 0.0000000000000000 >> 1 15 52 6 0.0000000000000000 0.0000000000000000 >> 1 16 52 6 0.0000000000000000 0.0000000000000000 >> 1 17 52 6 0.0000000000000000 0.0000000000000000 >> 1 18 52 6 0.0000000000000000 0.0000000000000000 >> 1 19 52 6 0.0000000000000000 0.0000000000000000 >> 1 20 52 6 0.0000000000000000 0.0000000000000000 >> 1 21 52 6 0.0000000000000000 0.0000000000000000 >> 1 22 52 6 0.0000000000000000 0.0000000000000000 >> 1 23 52 6 0.0000000000000000 0.0000000000000000 >> 1 24 52 6 0.0000000000000000 0.0000000000000000 >> 1 25 52 6 0.0000000000000000 0.0000000000000000 >> >> >> On May 1, 2013, at 5:06 PM, Rajeev Thakur wrote: >> >>> Just before the call to gather, check the value of send_count and check that send_buffer is not all zeros. >>> >>> send_count has to be the same on all ranks. Otherwise you have to use Gatherv. >>> >>> On May 1, 2013, at 7:03 PM, Ryan Crocker wrote: >>> >>>> that's where i checked it with and it's min and max are still zero. I just amended it so that each send buffer from the different cores are the same size and when i check it on the root gsend_buffer is still incorrect. >>>> >>>> On May 1, 2013, at 5:00 PM, Rajeev Thakur wrote: >>>> >>>>> gsend_buffer will be valid only on the root. >>>>> >>>>> On May 1, 2013, at 6:55 PM, Ryan Crocker wrote: >>>>> >>>>>> I just looked at the gsend_buffer, that's actually all zeros as well, and each send_buffer is not. So i think my problem is there. >>>>>> >>>>>> On May 1, 2013, at 4:47 PM, Rajeev Thakur wrote: >>>>>> >>>>>>> The count passed to MPI_Scatter should be the local size, i.e., the amount that gets sent to each process. Looks like what is being passed is the global size. >>>>>>> >>>>>>> On May 1, 2013, at 6:21 PM, Ryan Crocker wrote: >>>>>>> >>>>>>>> Hi all, >>>>>>>> >>>>>>>> So i don't know what the issue with this code snippet is but i cannot get the scatter call to work. When i print out the recieve_buffer it comes out as all zeros. The counters without the underscore are the core domains, with the o, the global domains. >>>>>>>> >>>>>>>> rec_count = (imaxo-imino+1)*(jmaxo-jmino+1)*(kmaxo-kmino+1) >>>>>>>> send_count = (imax_-imin_+1)*(jmax_-jmin_+1)*(kmax_-kmin_+1) >>>>>>>> >>>>>>>> call MPI_GATHER (send_buffer, send_count, MPI_REAL, gsend_buffer, send_count, MPI_REAL, iroot, comm, ierr) >>>>>>>> >>>>>>>> rec_count = (imaxo-imino+1)*(jmaxo-jmino+1)*(kmaxo-kmino+1) >>>>>>>> send_count = (imaxo-imino+1)*(jmaxo-jmino+1)*(kmaxo-kmino+1) >>>>>>>> >>>>>>>> call MPI_SCATTER (gsend_buffer, send_count, MPI_REAL, recieve_buffer, rec_count, MPI_REAL, iroot, comm, ierr) >>>>>>>> >>>>>>>> thanks for the help. >>>>>>>> >>>>>>>> Ryan Crocker >>>>>>>> University of Vermont, School of Engineering >>>>>>>> Mechanical Engineering Department >>>>>>>> rcrocker(a)uvm.edu >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >>> _______________________________________________ >>> 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 > > _______________________________________________ > 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] gather, send
by Ryan Crocker 01 May '13

01 May '13

oh, a quck fix to that last email, send_buffer, and gsend_buffer are actually vectors so the print before the long list is: print*,irank,i,j,k,send_buffer(n),gsend_buffer(n) Where n is my mapping variable to node designation and it's (i,j,k) placement, i.e. do k=kmino,kmaxo do j=jmino,jmaxo do i=imino,imaxo counter = counter + 1 nodes_n(i,j,k) = counter node_index(counter)%node_i = i node_index(counter)%node_j = j node_index(counter)%node_k = k end do end do end do with do k=kmino,kmaxo do j=jmino,jmaxo do i=imino,imaxo print*,irank,i,j,k,send_buffer(nodes_n(i,j,k) ),gsend_buffer(nodes_n(i,j,k) ) end do end do end do On May 1, 2013, at 5:16 PM, Ryan Crocker wrote: > i'm just checking just the gather call, and the gsend_buffer from the gather call is still empty: > > max_buff is now the largest core domain. > > print*,max_buff -> 24750 > > call MPI_GATHER(send_buffer, max_buff, MPI_REAL, gsend_buffer, max_buff, MPI_REAL, iroot, comm, ierr) > > a print out of the send_buffer and the gsend_buffer where it should have non-zero terms. > > print*,irank,i,j,k,send_buffer(i,j,k),gsent_buffer(i,j,k) -> > > 1 6 50 6 0.0000000000000000 0.0000000000000000 > 1 7 50 6 0.0000000000000000 0.0000000000000000 > 1 8 50 6 0.0000000000000000 0.0000000000000000 > 1 9 50 6 0.0000000000000000 0.0000000000000000 > 1 10 50 6 0.0000000000000000 0.0000000000000000 > 1 11 50 6 0.0000000000000000 0.0000000000000000 > 1 12 50 6 0.0000000000000000 0.0000000000000000 > 1 13 50 6 0.0000000000000000 0.0000000000000000 > 1 14 50 6 0.0000000000000000 0.0000000000000000 > 1 15 50 6 0.0000000000000000 0.0000000000000000 > 1 16 50 6 0.0000000000000000 0.0000000000000000 > 1 17 50 6 0.0000000000000000 0.0000000000000000 > 1 18 50 6 0.0000000000000000 0.0000000000000000 > 1 19 50 6 0.0000000000000000 0.0000000000000000 > 1 20 50 6 0.0000000000000000 0.0000000000000000 > 1 21 50 6 0.0000000000000000 0.0000000000000000 > 1 22 50 6 0.0000000000000000 0.0000000000000000 > 1 23 50 6 0.0000000000000000 0.0000000000000000 > 1 24 50 6 0.0000000000000000 0.0000000000000000 > 1 25 50 6 0.0000000000000000 0.0000000000000000 > 1 6 51 6 1.0000000000000000 0.0000000000000000 > 1 7 51 6 1.0000000000000000 0.0000000000000000 > 1 8 51 6 1.0000000000000000 0.0000000000000000 > 1 9 51 6 1.0000000000000000 0.0000000000000000 > 1 10 51 6 1.0000000000000000 0.0000000000000000 > 1 11 51 6 1.0000000000000000 0.0000000000000000 > 1 12 51 6 1.0000000000000000 0.0000000000000000 > 1 13 51 6 1.0000000000000000 0.0000000000000000 > 1 14 51 6 1.0000000000000000 0.0000000000000000 > 1 15 51 6 1.0000000000000000 0.0000000000000000 > 1 16 51 6 1.0000000000000000 0.0000000000000000 > 1 17 51 6 1.0000000000000000 0.0000000000000000 > 1 18 51 6 1.0000000000000000 0.0000000000000000 > 1 19 51 6 1.0000000000000000 0.0000000000000000 > 1 20 51 6 1.0000000000000000 0.0000000000000000 > 1 21 51 6 1.0000000000000000 0.0000000000000000 > 1 22 51 6 1.0000000000000000 0.0000000000000000 > 1 23 51 6 1.0000000000000000 0.0000000000000000 > 1 24 51 6 1.0000000000000000 0.0000000000000000 > 1 25 51 6 1.0000000000000000 0.0000000000000000 > 1 6 52 6 0.0000000000000000 0.0000000000000000 > 1 7 52 6 0.0000000000000000 0.0000000000000000 > 1 8 52 6 0.0000000000000000 0.0000000000000000 > 1 9 52 6 0.0000000000000000 0.0000000000000000 > 1 10 52 6 0.0000000000000000 0.0000000000000000 > 1 11 52 6 0.0000000000000000 0.0000000000000000 > 1 12 52 6 0.0000000000000000 0.0000000000000000 > 1 13 52 6 0.0000000000000000 0.0000000000000000 > 1 14 52 6 0.0000000000000000 0.0000000000000000 > 1 15 52 6 0.0000000000000000 0.0000000000000000 > 1 16 52 6 0.0000000000000000 0.0000000000000000 > 1 17 52 6 0.0000000000000000 0.0000000000000000 > 1 18 52 6 0.0000000000000000 0.0000000000000000 > 1 19 52 6 0.0000000000000000 0.0000000000000000 > 1 20 52 6 0.0000000000000000 0.0000000000000000 > 1 21 52 6 0.0000000000000000 0.0000000000000000 > 1 22 51 6 1.0000000000000000 0.0000000000000000 > 1 23 51 6 1.0000000000000000 0.0000000000000000 > 1 24 51 6 1.0000000000000000 0.0000000000000000 > 1 25 51 6 1.0000000000000000 0.0000000000000000 > 1 6 52 6 0.0000000000000000 0.0000000000000000 > 1 7 52 6 0.0000000000000000 0.0000000000000000 > 1 8 52 6 0.0000000000000000 0.0000000000000000 > 1 9 52 6 0.0000000000000000 0.0000000000000000 > 1 10 52 6 0.0000000000000000 0.0000000000000000 > 1 11 52 6 0.0000000000000000 0.0000000000000000 > 1 12 52 6 0.0000000000000000 0.0000000000000000 > 1 13 52 6 0.0000000000000000 0.0000000000000000 > 1 14 52 6 0.0000000000000000 0.0000000000000000 > 1 15 52 6 0.0000000000000000 0.0000000000000000 > 1 16 52 6 0.0000000000000000 0.0000000000000000 > 1 17 52 6 0.0000000000000000 0.0000000000000000 > 1 18 52 6 0.0000000000000000 0.0000000000000000 > 1 19 52 6 0.0000000000000000 0.0000000000000000 > 1 20 52 6 0.0000000000000000 0.0000000000000000 > 1 21 52 6 0.0000000000000000 0.0000000000000000 > 1 22 52 6 0.0000000000000000 0.0000000000000000 > 1 23 52 6 0.0000000000000000 0.0000000000000000 > 1 24 52 6 0.0000000000000000 0.0000000000000000 > 1 25 52 6 0.0000000000000000 0.0000000000000000 > > > On May 1, 2013, at 5:06 PM, Rajeev Thakur wrote: > >> Just before the call to gather, check the value of send_count and check that send_buffer is not all zeros. >> >> send_count has to be the same on all ranks. Otherwise you have to use Gatherv. >> >> On May 1, 2013, at 7:03 PM, Ryan Crocker wrote: >> >>> that's where i checked it with and it's min and max are still zero. I just amended it so that each send buffer from the different cores are the same size and when i check it on the root gsend_buffer is still incorrect. >>> >>> On May 1, 2013, at 5:00 PM, Rajeev Thakur wrote: >>> >>>> gsend_buffer will be valid only on the root. >>>> >>>> On May 1, 2013, at 6:55 PM, Ryan Crocker wrote: >>>> >>>>> I just looked at the gsend_buffer, that's actually all zeros as well, and each send_buffer is not. So i think my problem is there. >>>>> >>>>> On May 1, 2013, at 4:47 PM, Rajeev Thakur wrote: >>>>> >>>>>> The count passed to MPI_Scatter should be the local size, i.e., the amount that gets sent to each process. Looks like what is being passed is the global size. >>>>>> >>>>>> On May 1, 2013, at 6:21 PM, Ryan Crocker wrote: >>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> So i don't know what the issue with this code snippet is but i cannot get the scatter call to work. When i print out the recieve_buffer it comes out as all zeros. The counters without the underscore are the core domains, with the o, the global domains. >>>>>>> >>>>>>> rec_count = (imaxo-imino+1)*(jmaxo-jmino+1)*(kmaxo-kmino+1) >>>>>>> send_count = (imax_-imin_+1)*(jmax_-jmin_+1)*(kmax_-kmin_+1) >>>>>>> >>>>>>> call MPI_GATHER (send_buffer, send_count, MPI_REAL, gsend_buffer, send_count, MPI_REAL, iroot, comm, ierr) >>>>>>> >>>>>>> rec_count = (imaxo-imino+1)*(jmaxo-jmino+1)*(kmaxo-kmino+1) >>>>>>> send_count = (imaxo-imino+1)*(jmaxo-jmino+1)*(kmaxo-kmino+1) >>>>>>> >>>>>>> call MPI_SCATTER (gsend_buffer, send_count, MPI_REAL, recieve_buffer, rec_count, MPI_REAL, iroot, comm, ierr) >>>>>>> >>>>>>> thanks for the help. >>>>>>> >>>>>>> Ryan Crocker >>>>>>> University of Vermont, School of Engineering >>>>>>> Mechanical Engineering Department >>>>>>> rcrocker(a)uvm.edu >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>> >>>> _______________________________________________ >>>> 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 >> >> _______________________________________________ >> 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 Ryan Crocker University of Vermont, School of Engineering Mechanical Engineering Department rcrocker(a)uvm.edu 315-212-7331

1 0

Re: [mpich-discuss] gather, send
by Rajeev Thakur 01 May '13

01 May '13

Is the send_buffer allocated to be large enough to hold max_buff on all ranks? Is gsend_buffer large enough to hold max_buff * nprocs? Is the rank 1, not rank 0, the root? On May 1, 2013, at 7:16 PM, Ryan Crocker wrote: > i'm just checking just the gather call, and the gsend_buffer from the gather call is still empty: > > max_buff is now the largest core domain. > > print*,max_buff -> 24750 > > call MPI_GATHER(send_buffer, max_buff, MPI_REAL, gsend_buffer, max_buff, MPI_REAL, iroot, comm, ierr) > > a print out of the send_buffer and the gsend_buffer where it should have non-zero terms. > > print*,irank,i,j,k,send_buffer(i,j,k),gsent_buffer(i,j,k) -> > > 1 6 50 6 0.0000000000000000 0.0000000000000000 > 1 7 50 6 0.0000000000000000 0.0000000000000000 > 1 8 50 6 0.0000000000000000 0.0000000000000000 > 1 9 50 6 0.0000000000000000 0.0000000000000000 > 1 10 50 6 0.0000000000000000 0.0000000000000000 > 1 11 50 6 0.0000000000000000 0.0000000000000000 > 1 12 50 6 0.0000000000000000 0.0000000000000000 > 1 13 50 6 0.0000000000000000 0.0000000000000000 > 1 14 50 6 0.0000000000000000 0.0000000000000000 > 1 15 50 6 0.0000000000000000 0.0000000000000000 > 1 16 50 6 0.0000000000000000 0.0000000000000000 > 1 17 50 6 0.0000000000000000 0.0000000000000000 > 1 18 50 6 0.0000000000000000 0.0000000000000000 > 1 19 50 6 0.0000000000000000 0.0000000000000000 > 1 20 50 6 0.0000000000000000 0.0000000000000000 > 1 21 50 6 0.0000000000000000 0.0000000000000000 > 1 22 50 6 0.0000000000000000 0.0000000000000000 > 1 23 50 6 0.0000000000000000 0.0000000000000000 > 1 24 50 6 0.0000000000000000 0.0000000000000000 > 1 25 50 6 0.0000000000000000 0.0000000000000000 > 1 6 51 6 1.0000000000000000 0.0000000000000000 > 1 7 51 6 1.0000000000000000 0.0000000000000000 > 1 8 51 6 1.0000000000000000 0.0000000000000000 > 1 9 51 6 1.0000000000000000 0.0000000000000000 > 1 10 51 6 1.0000000000000000 0.0000000000000000 > 1 11 51 6 1.0000000000000000 0.0000000000000000 > 1 12 51 6 1.0000000000000000 0.0000000000000000 > 1 13 51 6 1.0000000000000000 0.0000000000000000 > 1 14 51 6 1.0000000000000000 0.0000000000000000 > 1 15 51 6 1.0000000000000000 0.0000000000000000 > 1 16 51 6 1.0000000000000000 0.0000000000000000 > 1 17 51 6 1.0000000000000000 0.0000000000000000 > 1 18 51 6 1.0000000000000000 0.0000000000000000 > 1 19 51 6 1.0000000000000000 0.0000000000000000 > 1 20 51 6 1.0000000000000000 0.0000000000000000 > 1 21 51 6 1.0000000000000000 0.0000000000000000 > 1 22 51 6 1.0000000000000000 0.0000000000000000 > 1 23 51 6 1.0000000000000000 0.0000000000000000 > 1 24 51 6 1.0000000000000000 0.0000000000000000 > 1 25 51 6 1.0000000000000000 0.0000000000000000 > 1 6 52 6 0.0000000000000000 0.0000000000000000 > 1 7 52 6 0.0000000000000000 0.0000000000000000 > 1 8 52 6 0.0000000000000000 0.0000000000000000 > 1 9 52 6 0.0000000000000000 0.0000000000000000 > 1 10 52 6 0.0000000000000000 0.0000000000000000 > 1 11 52 6 0.0000000000000000 0.0000000000000000 > 1 12 52 6 0.0000000000000000 0.0000000000000000 > 1 13 52 6 0.0000000000000000 0.0000000000000000 > 1 14 52 6 0.0000000000000000 0.0000000000000000 > 1 15 52 6 0.0000000000000000 0.0000000000000000 > 1 16 52 6 0.0000000000000000 0.0000000000000000 > 1 17 52 6 0.0000000000000000 0.0000000000000000 > 1 18 52 6 0.0000000000000000 0.0000000000000000 > 1 19 52 6 0.0000000000000000 0.0000000000000000 > 1 20 52 6 0.0000000000000000 0.0000000000000000 > 1 21 52 6 0.0000000000000000 0.0000000000000000 > 1 22 51 6 1.0000000000000000 0.0000000000000000 > 1 23 51 6 1.0000000000000000 0.0000000000000000 > 1 24 51 6 1.0000000000000000 0.0000000000000000 > 1 25 51 6 1.0000000000000000 0.0000000000000000 > 1 6 52 6 0.0000000000000000 0.0000000000000000 > 1 7 52 6 0.0000000000000000 0.0000000000000000 > 1 8 52 6 0.0000000000000000 0.0000000000000000 > 1 9 52 6 0.0000000000000000 0.0000000000000000 > 1 10 52 6 0.0000000000000000 0.0000000000000000 > 1 11 52 6 0.0000000000000000 0.0000000000000000 > 1 12 52 6 0.0000000000000000 0.0000000000000000 > 1 13 52 6 0.0000000000000000 0.0000000000000000 > 1 14 52 6 0.0000000000000000 0.0000000000000000 > 1 15 52 6 0.0000000000000000 0.0000000000000000 > 1 16 52 6 0.0000000000000000 0.0000000000000000 > 1 17 52 6 0.0000000000000000 0.0000000000000000 > 1 18 52 6 0.0000000000000000 0.0000000000000000 > 1 19 52 6 0.0000000000000000 0.0000000000000000 > 1 20 52 6 0.0000000000000000 0.0000000000000000 > 1 21 52 6 0.0000000000000000 0.0000000000000000 > 1 22 52 6 0.0000000000000000 0.0000000000000000 > 1 23 52 6 0.0000000000000000 0.0000000000000000 > 1 24 52 6 0.0000000000000000 0.0000000000000000 > 1 25 52 6 0.0000000000000000 0.0000000000000000 > > > On May 1, 2013, at 5:06 PM, Rajeev Thakur wrote: > >> Just before the call to gather, check the value of send_count and check that send_buffer is not all zeros. >> >> send_count has to be the same on all ranks. Otherwise you have to use Gatherv. >> >> On May 1, 2013, at 7:03 PM, Ryan Crocker wrote: >> >>> that's where i checked it with and it's min and max are still zero. I just amended it so that each send buffer from the different cores are the same size and when i check it on the root gsend_buffer is still incorrect. >>> >>> On May 1, 2013, at 5:00 PM, Rajeev Thakur wrote: >>> >>>> gsend_buffer will be valid only on the root. >>>> >>>> On May 1, 2013, at 6:55 PM, Ryan Crocker wrote: >>>> >>>>> I just looked at the gsend_buffer, that's actually all zeros as well, and each send_buffer is not. So i think my problem is there. >>>>> >>>>> On May 1, 2013, at 4:47 PM, Rajeev Thakur wrote: >>>>> >>>>>> The count passed to MPI_Scatter should be the local size, i.e., the amount that gets sent to each process. Looks like what is being passed is the global size. >>>>>> >>>>>> On May 1, 2013, at 6:21 PM, Ryan Crocker wrote: >>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> So i don't know what the issue with this code snippet is but i cannot get the scatter call to work. When i print out the recieve_buffer it comes out as all zeros. The counters without the underscore are the core domains, with the o, the global domains. >>>>>>> >>>>>>> rec_count = (imaxo-imino+1)*(jmaxo-jmino+1)*(kmaxo-kmino+1) >>>>>>> send_count = (imax_-imin_+1)*(jmax_-jmin_+1)*(kmax_-kmin_+1) >>>>>>> >>>>>>> call MPI_GATHER (send_buffer, send_count, MPI_REAL, gsend_buffer, send_count, MPI_REAL, iroot, comm, ierr) >>>>>>> >>>>>>> rec_count = (imaxo-imino+1)*(jmaxo-jmino+1)*(kmaxo-kmino+1) >>>>>>> send_count = (imaxo-imino+1)*(jmaxo-jmino+1)*(kmaxo-kmino+1) >>>>>>> >>>>>>> call MPI_SCATTER (gsend_buffer, send_count, MPI_REAL, recieve_buffer, rec_count, MPI_REAL, iroot, comm, ierr) >>>>>>> >>>>>>> thanks for the help. >>>>>>> >>>>>>> Ryan Crocker >>>>>>> University of Vermont, School of Engineering >>>>>>> Mechanical Engineering Department >>>>>>> rcrocker(a)uvm.edu >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>> >>>> _______________________________________________ >>>> 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 >> >> _______________________________________________ >> 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