Sent from my iPad On Jul 27, 2013, at 5:45 AM, "Kirk, Benjamin (JSC-EG311)" <benjamin.k...@nasa.gov> wrote:
> On Jul 27, 2013, at 1:47 AM, "Derek Gaston" <fried...@gmail.com> wrote: > >> Ben: is there anything that can be done here? We were really looking >> forward to this... > > So the petsc matrices assume a constant blocking factor for the entire > matrix, which I think is the bug fundamental driver here. If you solved > decoupled flow/temperature in 1 matrix with equal order basis functions you'd > have 4 fully coupled variables in 3D, with 1 tagalog. I don't think petsc > will optimize for that case, and in fact you *might* be better memory wise > splitting into two matrices where the flow vars could be coupled. > > Is there another use case with non-full dof coupling I could be overlooking? > I'd be happy to try to address it... > > -Ben > > ------------------------------------------------------------------------------ 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-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel