Thanks, i was able to find the bug and correct it, it is working now,
I was calling a wrong DM for some DA,
Regards,
On Tue, Aug 14, 2018 at 2:13 PM, Jed Brown wrote:
> Manuel Valera writes:
>
> > Thanks Jed,
> >
> > I got the attached, it looks is coming from one of my routines
> > CorrectU4
Manuel Valera writes:
> Thanks Jed,
>
> I got the attached, it looks is coming from one of my routines
> CorrectU4Pressure.F90, what other information can i get from this log?
If you compile with debug info (COPTFLAGS=-g FOPTFLAGS=-g) you'll be
able to see the source line that's causing this err
Thanks Jed,
I got the attached, it looks is coming from one of my routines
CorrectU4Pressure.F90, what other information can i get from this log?
Thanks,
On Tue, Aug 14, 2018 at 12:57 PM, Jed Brown wrote:
> Manuel Valera writes:
>
> > Hello everyone,
> >
> > I am working on running part of my
Manuel Valera writes:
> Hello everyone,
>
> I am working on running part of my code in a GPU, recently i was able to
> run the whole model using one P100 GPU and one processor with good timing
> but using --with-debugging=1 as configure argument,
>
> With this in mind i compiled PETSc in a separ
Hello everyone,
I am working on running part of my code in a GPU, recently i was able to
run the whole model using one P100 GPU and one processor with good timing
but using --with-debugging=1 as configure argument,
With this in mind i compiled PETSc in a separate folder with the same exact
flags
