Hi Patrick, You are spot on, I was copying in a vector and not taking care to pad with 1s to length 3.
Thanks Phil On 01/10/2018 15:57, Patrick Sanan wrote: > Whoops, sent that patch too fast (forgot to update SETERRQ3 to > SETERRQ4). Updated patch for maint attached. > > Am Mo., 1. Okt. 2018 um 16:55 Uhr schrieb Patrick Sanan > <[email protected] <mailto:[email protected]>>: > > Meshes of size 1 should work. > > Looks like there is a bug in the code to produce this error > message (patch for maint attached). It's not outputting the "P" > (size in the 3rd dimension) component. > > This is just speculation without a full error message or code to > reproduce, but perhaps the size in the third dimension is an > uninitialized value which is triggering this warning with a 10 x > 10 x (huge garbage) x 1 (dof) mesh. > > Am Mo., 1. Okt. 2018 um 15:59 Uhr schrieb Phil Tooley > <[email protected] <mailto:[email protected]>>: > > Hi all, > > Is it valid to have a DMDA with one of the dimensions of size > 1. I was > hoping to avoid having to write explicit logic to handle the > case that I > am working on a 2D rather than a 3D image for my current > application. > Unfortunately when I try to construct such a DMDA I get an error: > > [0]PETSC ERROR: --------------------- Error Message > -------------------------------------------------------------- > [0]PETSC ERROR: Overflow in integer operation: > [0]PETSC ERROR: Mesh of 10 by 10 by 1 (dof) is too large for > 32 bit indices > > Is there a workaround other than "write everything twice"? > > Thanks > > Phil > > -- > Phil Tooley > Research Software Engineering > University of Sheffield > -- Phil Tooley Research Software Engineering University of Sheffield
