https://www.mpich.org/static/docs/v3.1/www3/MPI_Comm_size.html
int MPI_Comm_size( MPI_Comm comm, int *size ) i.e there is no PetscInt here. [MPI does not know about PETSc datatypes] For convinence we provide PetscMPIInt to keep track of such variables [similarly PetscBLASInt]. For eg: Check src/vec/vec/examples/tests/ex2f.F Satish On Tue, 18 Sep 2018, TAY wee-beng wrote: > Hi, > > I managed to find the error appearing after using PETSc 64bit in linux - > > call MPI_COMM_SIZE(MPI_COMM_WORLD, num_procs, ierr) > > I have assigned num_procs as PetscInt and I got 0 instead of 1 (for 1 procs) > > Assigning num_procs as integer as the problem. > > Is this supposed to be the case? Or is it a bug? > > Thank you very much. > > Yours sincerely, > > ================================================ > TAY Wee-Beng (Zheng Weiming) 郑伟明 > Personal research webpage: http://tayweebeng.wixsite.com/website > Youtube research showcase: > https://www.youtube.com/channel/UC72ZHtvQNMpNs2uRTSToiLA > linkedin: www.linkedin.com/in/tay-weebeng > ================================================ > > On 8/9/2018 1:14 AM, Smith, Barry F. wrote: > > You can try valgrind > > http://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind > > > > Barry > > > > > >> On Sep 7, 2018, at 1:44 AM, TAY wee-beng <[email protected]> wrote: > >> > >> Hi, > >> > >> I found that I am unable to read in values thru namelist in Fortran after > >> using PETSc 64bit in linux. > >> > >> I have a parameter txt file which is read in using namelist in Fortran： > >> > >> namelist /body_input/ no_body, convex_body, motion_type, hover, wing_config > >> ... > >> > >> open (unit = 44 , FILE = "ibm3d_input.txt" , status = "old", iostat = > >> openstatus(4)) > >> > >> if (openstatus(4) > 0) then > >> > >> print *, "ibm3d_input file not present or wrong filename." > >> > >> stop > >> > >> end if > >> > >> read (44,nml = solver_input) > >> > >> read (44,nml = grid_input) > >> > >> read (44,nml = body_input)... > >> > >> > >> After using PETSc 64bit, my code aborts and I realise that it is because > >> the values have became NaN. Strangely, it does not occur in windows with > >> VS2008. > >> > >> I wonder if it's a bug with the Intel Fortran compiler 2018. > >> > >> Anyone has similar experience? > >> > >> -- > >> Thank you very much. > >> > >> Yours sincerely, > >> > >> ================================================ > >> TAY Wee-Beng (Zheng Weiming) 郑伟明 > >> Personal research webpage: http://tayweebeng.wixsite.com/website > >> Youtube research showcase: > >> https://www.youtube.com/channel/UC72ZHtvQNMpNs2uRTSToiLA > >> linkedin: www.linkedin.com/in/tay-weebeng > >> ================================================ > >> > >
