[MOAB-dev] mbchaco default arguments

Roman Putanowicz putanowr at l5.pk.edu.pl
Sun Dec 13 21:51:10 CST 2009


Hi,

I have tried to use mbchaco (more exactly ComputePartition class).

The method 
MBErrorCode compute_partition(const int nprocs, const char *filename = NULL, 
                              const bool write_file = false, const char
                              *out_file = NULL);

when used with default parameters fails immediately because of the
check in the code:

// check input
if (NULL == filename && NULL == out_file) return MB_FAILURE;

It seems that this method is written having in mind only the input from
file. It is easy to fix it however I got puzzling output from chaco
when trying to use mbchaco standalne:

putanowr at tomi:~/work/MOABUtils/tests$ mbchaco data/lshape.vtk y ala 4
                    Chaco 2.0
                      (MOAB-based version)
          Sandia National Laboratories
Parameter file `User_Params' not found; using default parameters.
Parameter file `User_Params' not found; using default parameters.
No graph input.  Only allowed for inertial or simple methods without KL.
goal[0] is -0.25, but should be nonnegative.
goal[1] is -0.25, but should be nonnegative.
goal[2] is -0.25, but should be nonnegative.
goal[3] is -0.25, but should be nonnegative.
Sum of values in goal (-1) not equal to sum of vertex weights (-1).
ERROR IN INPUT.

Could someone please comment what is going on?
If I need need a special User_Params setting for mbchaco
could somebody provide a sample one? (ComputePartition class
takes arbitrary decision to make the global_method=1,
but even if I change the code and take for instance global_method=4
then there is this business of "Sum of values in goal (-1) not equal to sum of
vertex weights (-1)."

The sample mesh file I tried to partition is in attachment.

Regards,

Roman
-- 
Roman Putanowicz  < putanowr at l5.pk.edu.pl  >
Institute for Computational Civil Engng (L-5)
Dept. of Civil Engng, Cracow Univ. of Technology
www.l5.pk.edu.pl, tel. +48 12 628 2569, fax 2034


More information about the moab-dev mailing list