Hi Jed,
Im not getting any error! There just no file comming. I tried it on serveral machienes. UsingPetscViewerASCIIOpen it works fine. My Petsc source is from Dezember 2014.
Thanks
Gesendet:Dienstag, 03. Mrz 2015 um 23:49 Uhr
Von:Jed Brown j...@jedbrown.org
An:Grischa Jacobs
Hi,
I am using DMDAVecGetArrayF90 with a pointer in petsc 3.4.3. Is there anyway of
finding out what the start and finish indices of the pointer coming back from
this routine are per processor?
I have declared:
DM :: da
Vec :: X
On Wed, Mar 4, 2015 at 12:26 PM, carol.brick...@awe.co.uk wrote:
Hi,
I am using DMDAVecGetArrayF90 with a pointer in petsc 3.4.3. Is there
anyway of finding out what the start and finish indices of the pointer
coming back from this routine are per processor?
I have declared:
DM
Thank you Barry. I think this is what I want.
Hui
From: Barry Smith [bsm...@mcs.anl.gov]
Sent: Wednesday, March 04, 2015 10:53 AM
To: Sun, Hui
Cc: petsc-users@mcs.anl.gov
Subject: Re: [petsc-users] DMDA with dof=4, multigrid solver
On Mar 4, 2015, at
DMDAGetCorners() for global vectors and DMDAGetGhostCorners() for local
(ghosted) vectors.
Barry
On Mar 4, 2015, at 12:26 PM, carol.brick...@awe.co.uk
carol.brick...@awe.co.uk wrote:
Hi,
I am using DMDAVecGetArrayF90 with a pointer in petsc 3.4.3. Is there anyway
of finding out
Excellent - just remembered that. I'll see if it works. Had taken it out to do
my own thing.
Carol
Dr Carol Brickley
BSc,PhD,ARCS,DIC,MBCS
Senior Software Engineer
Applied Computer Science
DS+T,
AWE
Aldermaston
Reading
Berkshire
RG7 4PR
Direct: 0118 9855035
-Original Message-
On Mar 4, 2015, at 8:53 AM, Sun, Hui hus...@ucsd.edu wrote:
I thought DMDAcreateMatrix would already specify the size of the matrix to be
N by N, where N is the number of unknowns in the grid. And each processor
takes care of a submatrix of size N_i by N_i.
Not really. Each process
On Mar 4, 2015, at 7:45 PM, Randall Mackie rlmackie...@gmail.com wrote:
In my application, I am repeatedly calling KSPSolve with the following
options:
-ksp_type gmres \
-pc_type gamg \
-pc_gamg_type agg \
-pc_gamg_agg_nsmooths 1\
each call is after the matrix and right hand side
In my application, I am repeatedly calling KSPSolve with the following options:
-ksp_type gmres \
-pc_type gamg \
-pc_gamg_type agg \
-pc_gamg_agg_nsmooths 1\
each call is after the matrix and right hand side have been updated.
This works well in the sense that it solves the system in a
Hi Barry,
Thank you for this advice, it solved my problem.
I was able to see that VecVeiw() wrote all the time and narrowed down my
problem to reading back the binary files.
Sorry, I should have done that before posting.
Mohammad
On 4/03/2015 4:00 pm, Barry Smith bsm...@mcs.anl.gov wrote:
I thought DMDAcreateMatrix would already specify the size of the matrix to be N
by N, where N is the number of unknowns in the grid. And each processor takes
care of a submatrix of size N_i by N_i.
However, I wish to form a matrix of size M by N, where N is the number of
unknowns in the grid,
11 matches
Mail list logo
