> On Aug 22, 2016, at 1:10 PM, Matthew Overholt <[email protected]> wrote: > >>> On Aug 22, 2016, at 10:49 AM, Matthew Overholt <[email protected]> wrote: >>> >>> I am using the Intel MKL CPardiso library as a PC direct solver, and I am >>> trying to >>> figure out how to properly set options (the Pardiso and CPardiso “iparm” >>> parameter >>> values in the Intel docs). > >> On Aug 22, 2016, at 12:32 PM, Barry Smith wrote: >> The easy way to set these is via the options database so from the command >> line you >> can use -mat_mkl_cpardiso_<icntl> <ival> for example -mat_mkl_cpardiso_10 13 >> or in >> the code you can write >> PetscOptionsSetValue(NULL,"-mat_mkl_cpardiso_10","13"); make >> sure that you call the PetscOptionsSetValue() BEFORE you call >> KSPSetFromOptions(). > > Thanks, Barry, that is very helpful. I can successfully set some of the > CPardiso parameters now from the command line (or otherwise, using the > options database), but according to "-help" the only MKL_CPARDISO Options > available are -mat_mkl_cpardiso_1 and _65 through _69. If I specify option > 10 as you suggested I get a warning that the option was not used.
Hmm, looks like you need to run with -mat_mkl_cpardiso_1 1 in order to get the other options like 10 to work. So for example -mat_mkl_cpardiso_1 1 -mat_mkl_cpardiso_10 13 > I would like to get access to several other parameters to try and fix my > zero pivot problem. How should I do that? Does the MKL interface make use > of some -pc_factor* options (such as -pc_factor_zeropivot) when it calls > CPardiso? No it does not use these options. > > Thanks again, > Matt Overholt > > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus >
