On Thu, 17 Sep 2009, Derek Gaston wrote:
> On Sep 17, 2009, at 5:30 PM, Roy Stogner wrote:
>> Done, and with a parallel coarsening bugfix thrown in for good
>> measure. I haven't tested it with --enable-complex yet (don't have a
>> PETSc build around with PetscScalar==std::complex) but it
>> co
On Sep 17, 2009, at 5:30 PM, Roy Stogner wrote:
> Done, and with a parallel coarsening bugfix thrown in for good
> measure. I haven't tested it with --enable-complex yet (don't have a
> PETSc build around with PetscScalar==std::complex) but it
> compiles that way again, at least.
PARALLEL COARSE
On Thu, 17 Sep 2009, Roy Stogner wrote:
> Still working on it. We've basically got the same problem in every
> Parallel:: method that takes a default argument. There's a comment in
> there where someone (me? Ben?) fixed one of them by adding a second
> declaration (and a comment thinking that i
On Thu, 17 Sep 2009, Roy Stogner wrote:
> Then we can get rid of all these std::complex operator
> overloadings.
Get rid of all these function overloadings, I mean. It may have taken
me too long to work out the difference between overloading and
template specialization, but I do know what oper
On Thu, 17 Sep 2009, John Peterson wrote:
On Thu, Sep 17, 2009 at 3:51 PM, Roy Stogner wrote:
On Thu, 17 Sep 2009, Roy Stogner wrote:
One of the two problems, anyway. Problem two: for some reason the
DistributedVector call to Parallel::allgather(std::vector&) with
T=std::complex isn't g
On Thu, Sep 17, 2009 at 3:51 PM, Roy Stogner wrote:
>
>
> On Thu, 17 Sep 2009, Roy Stogner wrote:
>
>> One of the two problems, anyway. Problem two: for some reason the
>> DistributedVector call to Parallel::allgather(std::vector&) with
>> T=std::complex isn't getting resolved to the
>> Parallel:
On Thu, 17 Sep 2009, Roy Stogner wrote:
> One of the two problems, anyway. Problem two: for some reason the
> DistributedVector call to Parallel::allgather(std::vector&) with
> T=std::complex isn't getting resolved to the
> Parallel::allgather(std::vector >&) specialization.
> I'm not sure how
On Thu, 17 Sep 2009, Roy Stogner wrote:
> On Thu, 17 Sep 2009, Roy Stogner wrote:
>
>> We use Parallel::datatype<> to wrap a bunch of MPI calls into a much
>> nicer interface. Unfortunately, it looks like MPI_DOUBLE_COMPLEX is a
>> Fortran-only datatype, and MPI::DOUBLE_COMPLEX requires a C++ MP
On Thu, 17 Sep 2009, Roy Stogner wrote:
> We use Parallel::datatype<> to wrap a bunch of MPI calls into a much
> nicer interface. Unfortunately, it looks like MPI_DOUBLE_COMPLEX is a
> Fortran-only datatype, and MPI::DOUBLE_COMPLEX requires a C++ MPI2
> standard whereas we've been trying to stay
On Thu, 17 Sep 2009, Jan Biermann wrote:
> I have been using an old libmesh version until now because I didn't want to
> bother changing all my application code. But now the problem size becomes
> this big that I cannot get around the latest version (because I think you
> changed the mesh clas
Dear all,
I have been using an old libmesh version until now because I didn't want
to bother changing all my application code. But now the problem size
becomes this big that I cannot get around the latest version (because I
think you changed the mesh class for parallel computing, so not storin
11 matches
Mail list logo
