Hi all, this could be a starting point. It’s similar to mbpart but based on METIS. The Makefile is very rudimental, the correct paths should be set manually!
On 27 Mar 2015, at 18:29, Vijay S. Mahadevan <[email protected]> wrote:
Gerd,
I use MOAB with PETSc (and DMMoab) and build it as PETSc external package (via '--download-moab=1'). This works fine, however, not all MOAB tools are built in the process. Unfortunately, the Zoltan external package is broken and as a result mbpart is not being built.
The PETSc configuration with --download-moab currently only uses HDF5 and NetCDF is PETSc has been configured with these packages also through either --download-PACKAGE or --with-PACKAGE-DIR semantics. I don't believe there is currently a configuration setting that accomodates the Zoltan linkage through this workflow.
You could however configure/compile MOAB with HDF5/NetCDF/Zoltan separately, install that somewhere and specify --with-moab-dir=/PATH/TO/MOAB. This is what I usually do since our development efforts use feature branches in both MOAB and PETSc simultaneously.
Could someone clarify the Zoltan dependence of mbpart and if there's a way to build it with just Parmetis?
Currently, mbpart depends on Zoltan interfaces to link against Metis/Parmetis and it is one of our top priority items to directly create an interface to at least Metis in the coming month so that building Zoltan for mbpart is not a requirement. Unfortunately until then, there isn't an elegant way to make this happen.
Vijay
On Fri, Mar 27, 2015 at 11:33 AM, Gerd Heber <[email protected]> wrote:
I use MOAB with PETSc (and DMMoab) and build it as PETSc external package (via '--download-moab=1'). This works fine, however, not all MOAB tools are built in the process. Unfortunately, the Zoltan external package is broken and as a result mbpart is not being built. Could someone clarify the Zoltan dependence of mbpart and if there's a way to build it with just Parmetis?
Thanks for your help. G.