Re: [petsc-users] DMGlobalToLocal acting weird

2018-07-02 Thread Manuel Valera
Yes, LocTemperature is the one with the problem, right after calling GlobalToLocalBegin/End() that array is different from the gTemperature it comes from, I cannot tell exactly where right now, i would need to create a much smaller experiment to print all of the entries, i'll try doing that tomorr

Re: [petsc-users] DMGlobalToLocal acting weird

2018-07-02 Thread Smith, Barry F.
> On Jul 2, 2018, at 6:48 PM, Manuel Valera wrote: > > > > On Mon, Jul 2, 2018 at 4:23 PM, Smith, Barry F. wrote: > > > > On Jul 2, 2018, at 6:13 PM, Manuel Valera wrote: > > > > Ok so i fixed the '99 business' by making sure the whole DMDA array was > > filled, there was row at the en

Re: [petsc-users] DMGlobalToLocal acting weird

2018-07-02 Thread Smith, Barry F.
> On Jul 2, 2018, at 6:13 PM, Manuel Valera wrote: > > Ok so i fixed the '99 business' by making sure the whole DMDA array was > filled, there was row at the end that wasn't and hence that problem, > > The local vector problem persists, though, Exactly what error? When you print the entir

Re: [petsc-users] DMGlobalToLocal acting weird

2018-07-02 Thread Smith, Barry F.
> On Jul 2, 2018, at 5:42 PM, Manuel Valera wrote: > > > > On Mon, Jul 2, 2018 at 3:04 PM, Smith, Barry F. wrote: > >First make sure that getCenterInfo(daScalars, xstart, ystart, zstart, > xend, yend, zend) returns what it should. > > It does, i am also working in one processor onl

Re: [petsc-users] DMGlobalToLocal acting weird

2018-07-02 Thread Manuel Valera
Ok so i fixed the '99 business' by making sure the whole DMDA array was filled, there was row at the end that wasn't and hence that problem, The local vector problem persists, though, i solved it for now using a global vector instead of a local one, is this because of the warning on globaltolocalb

Re: [petsc-users] DMGlobalToLocal acting weird

2018-07-02 Thread Manuel Valera
On Mon, Jul 2, 2018 at 3:04 PM, Smith, Barry F. wrote: > >First make sure that getCenterInfo(daScalars, xstart, ystart, zstart, > xend, yend, zend) returns what it should. > It does, i am also working in one processor only for now. >remove the 99 business and print out the arrtemp()

Re: [petsc-users] DMGlobalToLocal acting weird

2018-07-02 Thread Smith, Barry F.
First make sure that getCenterInfo(daScalars, xstart, ystart, zstart, xend, yend, zend) returns what it should. remove the 99 business and print out the arrtemp() and TO() values. Are they correct? What is DimTemperature? Shouldn't it be LocTempature? Print out the values in td

[petsc-users] DMGlobalToLocal acting weird

2018-07-02 Thread Manuel Valera
Hi guys, I've noticed a bug in my code that seems to happen right after a call to DMGlobalToLocalBegin/End and i can't seem to find a reason, it goes like this: I create the DMDA (daScalars) with the following: bx = DM_BOUNDARY_GHOSTED > by = DM_BOUNDARY_PERIODIC > bz = DM_BOUNDARY_GHOSTED >

Re: [petsc-users] "snes_type test" is gone?

2018-07-02 Thread Alexander Lindsay
Thank you Lisandro, that seems to work perfectly for what we want! On Sat, Jun 30, 2018 at 4:28 AM, Lisandro Dalcin wrote: > ./example.exe -snes_test_jacobian -snes_type ksponly -ksp_type preonly > -pc_type none -snes_convergence_test skip > On Sat, 30 Jun 2018 at 01:06, Alexander Lindsay > wro

Re: [petsc-users] Linesearch type cp change from 3.7.6 to 3.9.1

2018-07-02 Thread Matthew Knepley
On Mon, Jul 2, 2018 at 4:54 AM Carles Bona-Casas wrote: > Dear all, > > I have been running a code with the option -snes_linesearch_type cp using > petsc 3.7.6. > > I have updated my code to use petsc 3.9.1. If I run a simulation with the > updated code and the option -snes_linesearch_type cp inc