<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Aug 30, 2020, at 7:33 AM, Mark Adams <<a href="mailto:mfadams@lbl.gov" class="">mfadams@lbl.gov</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr" class=""><div class=""><br class=""><br class=""></div><div class=""><br class=""></div><div class="">So, if ParMETIS gives different edge cut as it is expected, MatPartitioningGetUseEdgeWeights and MatPartitioningSetUseEdgeWeights works correctly. Why can't CHACO?</div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br class=""></blockquote></div></blockquote><div class=""><br class=""></div><div class="">Chaco does not support using edge weights.</div></div></div></div></blockquote><div><br class=""></div> The package interfaces that do not support edge weights should error if one requests partitioning with edge weights. Not everyone is born with the innate knowledge that the Chaco PETSc interface doesn't support edge weights.</div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_quote"><div class=""> </div></div></div>
</div></blockquote></div><a href="https://gitlab.com/petsc/petsc/-/merge_requests/3119" class="">https://gitlab.com/petsc/petsc/-/merge_requests/3119</a></div></body></html>