On Thu, Jul 18, 2013 at 4:35 PM, Jens Lohne Eftang <[email protected]> wrote: > On 07/18/2013 05:28 PM, John Peterson wrote: >> >> On Thu, Jul 18, 2013 at 3:08 PM, Jens Lohne Eftang <[email protected]> >> wrote: >>> >>> Hi all, >>> >>> >>> So apparently I was somehow lucky when the below worked. If I use a >>> different mesh, for example as in ex6 under systems_of_equations, the >>> options below do not work. I get the error: >>> >>> [0]PETSC ERROR: Nonconforming object sizes! >>> [0]PETSC ERROR: Index set does not match blocks! >>> >>> I've tried different petsc versions (also the most recent) and there's no >>> difference. It does not seem to matter whether the mesh is >>> libmesh-generated >>> or not (the mesh for which the options below work is a cubit-generated >>> exodus mesh, but I also have cubit-generated exodus meshes for which it >>> doesn't work. I've not been able to identify what causes the error). >>> >>> Any ideas? >> >> Sounds like its related to the new block size stuff that Ben added >> recently? >> >> You can configure with --disable-blocked-storage and maybe get back to >> the way the code worked previously? > > > Thanks! That was indeed the issue. > > Does this mean I can't use eg mumps as my solver package?
No, I don't think the blocksize optimization being off has anything to do with MUMPS. -- John ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
