Mark : > > I call ParMetis from the app code and not from within a solver. Perhaps > -info should say "called ParMetis, edgecuts = %d\n", or something like that. >
Info like this needs to be put in petsc/ParMetis interface. We do not have it, do we? I use mumps/parmetis, thus have to get parmetis info via mumps. Hong > Mark > > On Mon, Nov 17, 2014 at 10:46 AM, Hong <[email protected]> wrote: > >> Mark, >> I use ParMetis with mumps direct solver. I can test their installation >> with >> petsc/src/ksp/ksp/examples/tutorials >> mpiexec -n 2 ./ex2 -pc_type lu -pc_factor_mat_solver_package mumps >> -mat_mumps_icntl_28 2 -mat_mumps_icntl_29 2 -ksp_view >> ... >> ICNTL(28) (use parallel or sequential ordering): 2 >> ICNTL(29) (parallel ordering): 2 >> >> To know what these parameters are, do >> mpiexec -n 2 ./ex2 -pc_type lu -pc_factor_mat_solver_package mumps -help >> |grep mumps >> ... >> -mat_mumps_icntl_28 <1>: ICNTL(28): use 1 for sequential analysis and >> ictnl(7) ordering, or 2 for parallel analysis and ictnl(29) ordering (None) >> -mat_mumps_icntl_29 <0>: ICNTL(29): parallel ordering 1 = ptscotch 2 = >> parmetis (None) >> >> Hong >> >> On Mon, Nov 17, 2014 at 9:12 AM, Mark Adams <[email protected]> wrote: >> >>> I have a code that repartitions the grid using PETSc. I would like to >>> know the simplest instructions that I can give my users (Pat Worley in this >>> case) to verify that ParMetis is actually called. I had difficulty with >>> this my self in that -info did not seem to say ParMetis was being used. I >>> did verify by printing vizing the partitions that partitioning was taking >>> place. I am thinking I can say use -log_summary and search for >>> download-parmetis -- is there a better way? >>> >>> Mark >>> >> >> >
