[deal.II] Nested reverse and forward-mode Sacado memory leak

Hello everyone, I found that Sacado's nested reverse and forward mode AD leads to a memory leak when use multiple times. I have opened an issue on their end: https://github.com/trilinos/Trilinos/issues/7741 and the steps to reproduce are pretty simple. However, I've found that the community

[deal.II] deal.II Newsletter #129

Hello everyone! This is deal.II newsletter #129. It automatically reports recently merged features and discussions about the deal.II finite element library. ## Below you find a list of recently proposed or merged features: #10811: Merge implementation of gather_evaluate and integrate_scatter

Re: [deal.II] Hanging nodes of a read-in mesh

I see. I will try if I can find something. For now, the slowdown happens in the FGMRES solver by the way. Thanks! Feimi On Mon, Aug 10, 2020 at 10:41 AM Wolfgang Bangerth wrote: > On 8/9/20 10:10 PM, Feimi Yu wrote: > > I'm solving for a SUPG stabilized slightly compressible Navier-Stokes > >

Re: [deal.II] Hanging nodes of a read-in mesh

On 8/9/20 10:10 PM, Feimi Yu wrote: I'm solving for a SUPG stabilized slightly compressible Navier-Stokes equation, with a Schur complement type preconditioner. I don't see why hanging nodes would make any kind of difference for this combination (in fact, for any equation). If I were you, I'd