Great, I’ll upgrade to 3.7.4. Thanks for the help. Simone On Nov 4, 2016, at 10:37, John Peterson <[email protected]<mailto:[email protected]>> wrote:
On Thu, Nov 3, 2016 at 8:53 PM, Roy Stogner <[email protected]<mailto:[email protected]>> wrote: On Thu, 3 Nov 2016, John Peterson wrote: On Thu, Nov 3, 2016 at 4:21 PM, Rossi, Simone <[email protected]<mailto:[email protected]>> wrote: I’m using PETSc 3.7.2. I’ll install a another version to check if that’s the problem. OK, it could be a bug on the libmesh side, I have not tested with 3.7.2 extensively yet... As luck would have it I just did a PETSc 3.7.2 build earlier today. Running LIBMESH_OPTIONS='-ksp_monitor' make check -C examples/transient/transient_ex1/ replicates the problem for me. I get to: Solving time step 4, time=0.1250... [0]PETSC ERROR: --------------------- Error Message -------------------------------------------------------------- [0]PETSC ERROR: Argument out of range [0]PETSC ERROR: Too many KSP monitors set Just talked to Fande Kong. This is apparently a known regression in PETSc that has been fixed as of 3.7.4. He has this version built on his machine and it runs this example with -ksp_monitor just fine. -- John ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
