On Thu, Jan 21, 2016 at 12:51 PM, Hong <[email protected]> wrote: > Paul: > It might be caused by our changes in default shift strategy. > We previously used '-pc_factor_shift_type NONZERO' for ilu, then changed > to '-pc_factor_shift_type NONE'. > For your test, I get > ./ex10 -f0 test.mat -rhs 0 -pc_type asm -pc_asm_overlap 12 -sub_pc_type > ilu -sub_pc_factor_mat_ordering_type 1wd -sub_pc_factor_levels 4 > -ksp_converged_reason -sub_pc_factor_shift_type NONZERO >
Ah! That was the change. Confirmed, adding -sub_pc_factor_shift_type nonzero gets our test passing again with those options. Mystery solved. Thank you very much. Best, Paul
