The error message is indeed confusing. Perhaps a better error message would be 'Cannot use -pc_type ilu with mumps'.
----- Original Message ----- > Hmm, then the error message is not complete enough. It printed seqaij > but nothing about mumps hence confused everyone who read your email > message. So how come mumps doesn't come up somewhere in the error > message? > > Barry > > > On Jun 21, 2011, at 11:14 AM, Shri wrote: > > > Sorry, my mistake..since 3 other people are working on this project > > someone added pc_factor_package mumps in the options file and hence > > ilu was giving that error. > > > > Thanks, > > Shri > > > > ----- Original Message ----- > >> Shri, > >> I notice this is on Karlin. > >> Does the same code work on other machines? > >> Does petsc examples work on this machine? > >> > >> Hong > >> > >> On Tue, Jun 21, 2011 at 4:12 AM, Jed Brown <jed at 59a2.org> wrote: > >>> On Tue, Jun 21, 2011 at 08:15, Shri <abhyshr at mcs.anl.gov> wrote: > >>>> > >>>> I am getting this error for ilu. Did anything get changed for > >>>> ilu? > >>>> I get > >>>> the same error for debug mode as well. > >>>> > >>>> ./TS -pc_type ilu > >>> > >>> Can you reproduce with an example? I haven't noticed any problems. > >>> Maybe you > >>> have memory corruption or something else unexpected causing > >>> MatGetFactor to > >>> not be called. Maybe try setting a breakpoint at ilu.c:213.
