[Developers] LocalReduce calculating wrong L{2, 3, 4} norms for complex variables ?
Yaakoub El-Khamra
yye00 at cct.lsu.edu
Wed Mar 26 12:48:29 CST 2008
Yes, I sent the patches around to PUGHReduce to make everything play
nice. This was about a year ago.
On Wed, 2008-03-26 at 18:47 +0100, Thomas Radke wrote:
> Erik Schnetter wrote:
> > On Mar 26, 2008, at 06:45:52, Thomas Radke wrote:
> >
> >> Yaakoub El Khamra wrote:
> >>
> >>> Actually the new reduction operators for PUGHReduce have been completed
> >>> a while ago, they just have not been moved over from AlphaThorns.
> >>
> >>
> >> Should they be moved then ? What mesh refinement parts are still missing
> >> in there ?
> >
> >
> > If it works, then yes, let's move it.
> >
> > The local reduction operators need to talk to the global reduction
> > operators, which are part of the driver. This interface isn't complete
> > for AMR, which needs masks and may have several components per
> > processor etc.
>
> Sorry, my tests were still with CactusBase/LocalReduce.
> AlphaThorns/LocalReduce does not work. While the operators seem to be
> all there, they aren't registered yet because their interface doesn't
> (quite) match the flesh reduction API.
>
More information about the Developers
mailing list