On Wednesday 16 August 2006 22:14, Satish Balay wrote: > On Wed, 16 Aug 2006, Thomas Geenen wrote: > > in matcreate i tell petsc that cpu0 owns 10 rows > > yes > > > in matsetvalue i tell him which rows (maybe 1,9,23,46 etc) but petsc > > automatically assumes that cpu0 owns the first 10 rows matsetsizes > > also just tells petsc the number of rows. 0-9 for cpu0 > > MatSetValues() provides no such functionality [of specifying rows > owned by local proc] . You are misinterpreting arguments to > MatSetValues(). i know but i hoped there would be some way of doing this i like to be in charge of these kind of things :) > > In this new model [which PETSc doesn't provide] - what hapens if you > call MatSetValues(row=0) on both proc 0 & proc1? Does this row get > owned by both procesors? why would you do that??? maybe if you have a very slow network? > > And from what numbering scheme do you get these numbers 1,9,23,46 etc? my nice little FEM app that i build an interface to petsc for :) > > Satish > > > so if i want to keep row 23 on cpu0 i have to do some sort of renumbering > > making row23 <10
thanks for all the help Thomas
