Praveen, the assembly/integration loop is executed in parallel by several threads (regardless of debug/optimized mode). You shouldn't use the sequence of printed outputs as an indication of the true order of execution.
From the documentation, it looks like cells_first is not what you want. Could you elaborate on your problem more? Why would you need the jump terms in the cell integration? Is this required by your integration scheme? This requirement sounds a bit odd to me. What equation are you trying to solve? Perhaps there is a way to get around this problem by re-engineering the implementation a bit. Regards, Mihai ________________________________ Von: Praveen C <[email protected]> An: Bärbel Janssen <[email protected]>; deal.ii <[email protected]> Gesendet: Mittwoch, den 13. April 2011, 17:33:08 Uhr Betreff: Re: [deal.II] MeshWorker integration_loop: Do faces first On Wed, Apr 13, 2011 at 8:07 PM, Praveen C <[email protected]> wrote: Thanks. I went back and looked at the documentation. It says > > >cells_first determines, whether, on a given cell, face or cell integrals are >to >be dealt with first. Note that independent of the value of this flag, cell and >face integrals of a given cell are all taken care of before moving to the next >cell. > > >So the order is maintained only on each cell. That explains my problem. I want >all face integration in the entire triangulation to be done first. > > I probably jumped to wrong conclusions here. Does meshworker automatically use threads if deal.ii is compiled with threads enabled ? praveen
_______________________________________________ dealii mailing list http://poisson.dealii.org/mailman/listinfo/dealii
