Thank you Satish! It works perfect.
Hui
From: Satish Balay [ba...@mcs.anl.gov]
Sent: Friday, April 17, 2015 3:29 PM
To: Sun, Hui
Cc: Matthew Knepley; petsc-users@mcs.anl.gov
Subject: Re: [petsc-users] install petsc with valgrind
Well - its best if the .
Well - its best if the .o files are not deleted.. [then you don't
have to run dsymutil]. One way to do it [if using PETSc makefiles] is:
make test RM=/bin/true
To run dsymutil - I think you need the .o files anyway - and run it as
instructed below.
> --66450-- run: /usr/bin/dsymutil "./test"
On Fri, Apr 17, 2015 at 5:26 PM, Sun, Hui wrote:
> How do I run dsymutil so as to get the line numbers?
>
dsymutil ./test
Matt
> --
> *From:* Matthew Knepley [knep...@gmail.com]
> *Sent:* Friday, April 17, 2015 3:10 PM
> *To:* Sun, Hui
> *Cc:* Barry Smith; pet
How do I run dsymutil so as to get the line numbers?
From: Matthew Knepley [knep...@gmail.com]
Sent: Friday, April 17, 2015 3:10 PM
To: Sun, Hui
Cc: Barry Smith; petsc-users@mcs.anl.gov
Subject: Re: [petsc-users] install petsc with valgrind
On Fri, Apr 17, 2015 a
Thank you Matt!
Hui
From: Matthew Knepley [knep...@gmail.com]
Sent: Friday, April 17, 2015 3:10 PM
To: Sun, Hui
Cc: Barry Smith; petsc-users@mcs.anl.gov
Subject: Re: [petsc-users] install petsc with valgrind
On Fri, Apr 17, 2015 at 5:09 PM, Sun, Hui
mailto:hus..
On Fri, Apr 17, 2015 at 5:09 PM, Sun, Hui wrote:
> I'm not sure if I'm doing the right thing. But I have just
> export PATH=$PATH:dir_to_valgind_bin
>
> And I rerun the command:
> -@${PETSC_DIR}/bin/petscmpiexec -valgrind -n ${NP} ./test -mx ${ND} -my
> ${ND} -mz ${ND} -ksp_monitor_short -ksp_typ
I'm not sure if I'm doing the right thing. But I have just
export PATH=$PATH:dir_to_valgind_bin
And I rerun the command:
-@${PETSC_DIR}/bin/petscmpiexec -valgrind -n ${NP} ./test -mx ${ND} -my ${ND}
-mz ${ND} -ksp_monitor_short -ksp_type fgmres -pc_type asm
Then it seems to output something, f
Or make sure valgrind is in your path
> On Apr 17, 2015, at 4:56 PM, Matthew Knepley wrote:
>
> As I said, it cannot find valgrind in your path. Remove it or install
> valgrind.
>
>Matt
>
> On Fri, Apr 17, 2015 at 4:55 PM, Sun, Hui wrote:
> Thank you, Matt and Barry. I was trying to r
As I said, it cannot find valgrind in your path. Remove it or install
valgrind.
Matt
On Fri, Apr 17, 2015 at 4:55 PM, Sun, Hui wrote:
> Thank you, Matt and Barry. I was trying to run the following:
> -@${PETSC_DIR}/bin/petscmpiexec -valgrind -n ${NP} ./test -mx ${ND} -my
> ${ND} -mz ${ND} -k
Thank you, Matt and Barry. I was trying to run the following:
-@${PETSC_DIR}/bin/petscmpiexec -valgrind -n ${NP} ./test -mx ${ND} -my ${ND}
-mz ${ND} -ksp_monitor_short -ksp_type fgmres -pc_type asm
where NP=2, ND=32
And in the makefile I have specified the following:
include ${PETSC_DIR}/lib/pe
Please please please always show WHAT YOU RAN with the error message.
Otherwise we just must guess
> On Apr 17, 2015, at 3:58 PM, Sun, Hui wrote:
>
> Thank you Barry. I just have it installed. And I was running a code, and got
> the following error message:
>
> HYDU_create_process (utils/
Looks like a bunch of these things are missing from
lib/petsc/conf/bfort-petsc.txt it should be listed under native
Barry
> On Apr 17, 2015, at 4:43 PM, Matthew Knepley wrote:
>
> Does bfort have to be told that PCCompositeType is an enum?
>
>Matt "bfort's biggest fan"
>
> On Fri
Does bfort have to be told that PCCompositeType is an enum?
Matt "bfort's biggest fan"
On Fri, Apr 17, 2015 at 4:37 PM, Mark Adams wrote:
> It looks like fieldsplitf.c has an extra PetscToPointer. type is already
> a pointer:
>
> PETSC_EXTERN void PETSC_STDCALL pcfieldsplitgettype_(PC
> pc
It looks like fieldsplitf.c has an extra PetscToPointer. type is already a
pointer:
PETSC_EXTERN void PETSC_STDCALL pcfieldsplitgettype_(PC pc,PCCompositeType
*type, int *__ierr ){
*__ierr = PCFieldSplitGetType(
(PC)PetscToPointer((pc) ),
(PCCompositeType* )PetscToPointer((type) ));
}
O
On Fri, Apr 17, 2015 at 3:58 PM, Sun, Hui wrote:
> Thank you Barry. I just have it installed. And I was running a code, and
> got the following error message:
>
> HYDU_create_process (utils/launch/launch.c:75): execvp error on file
> valgrind: (No such file or directory)
>
>
> ===
Thank you Barry. I just have it installed. And I was running a code, and got
the following error message:
HYDU_create_process (utils/launch/launch.c:75): execvp error on file valgrind:
(No such file or directory)
==
Likely need to run in the debugger to see what generates the error. Perhaps
a missing ierr?
Barry
> On Apr 17, 2015, at 9:10 AM, Mark Adams wrote:
>
> I declare
>
> PCCompositeType::pcctype
>
> But PCFieldSplitGetType does not seem to like it?
>
> Mark
>
> [1]PETSC ERROR:
On Fri, Apr 17, 2015 at 2:11 PM, Mikael Öhman wrote:
> In OOFEM, we do a "dry assembly" from which we compute the preallocation (
> e.g. MatSeqSBAIJSetPreallocation ).
>
> Since I already compute the column index in order to compute the "nnz"
> input for preallocation, I figured I'd try to use th
The development copy of PETSc allows using --prefix with MPICH
http://www.mcs.anl.gov/petsc/developers/index.html
> On Apr 17, 2015, at 2:38 PM, Sun, Hui wrote:
>
> Hello,
>
> I want to install petsc with valgrind. And I read some documentations, which
> suggests me to do
> ./configur
Hello,
I want to install petsc with valgrind. And I read some documentations, which
suggests me to do
./configure --download-mpich --with-valgind-dir=…
However, I also want to specify --prefix, but petsc doesn't allow me, because
--download-mpich option does not work with --prefix install.
Is
In OOFEM, we do a "dry assembly" from which we compute the preallocation (
e.g. MatSeqSBAIJSetPreallocation ).
Since I already compute the column index in order to compute the "nnz"
input for preallocation, I figured I'd try to use the
"MatSeq*AIJSetColumnIndices" functions as well.
First, I'd li
I declare
PCCompositeType::pcctype
But PCFieldSplitGetType does not seem to like it?
Mark
[1]PETSC ERROR: - Error Message
--
[1]PETSC ERROR: Invalid pointer
[1]PETSC ERROR: Invalid Pointer to Int: Parameter # 2
[1
Matt,
That really makes sense to me.
Thanks,
Paul
Huaibao (Paul) Zhang
*Gas Surface Interactions Lab*
Department of Mechanical Engineering
University of Kentucky,
Lexington,
KY, 40506-0503
*Office*: 216 Ralph G. Anderson Building
*Web*:gsil.engineering.uky.edu
On Fri, Apr 17, 2015 at 9:31 AM, M
On Fri, Apr 17, 2015 at 8:28 AM, paul zhang wrote:
> I agree with you. The performance indeed depends on the type of problem.
> Anyway, back to the questions I proposed, I am afraid ILU and LU are
> not sequential only. Am I right?
>
As it says in the table, the PETSc implementations are sequent
I agree with you. The performance indeed depends on the type of problem.
Anyway, back to the questions I proposed, I am afraid ILU and LU are
not sequential only. Am I right?
Thanks,
Paul
Huaibao (Paul) Zhang
*Gas Surface Interactions Lab*
Department of Mechanical Engineering
University of Kentuc
You can find the current list of preconditioners on line 40 here:
http://www.mcs.anl.gov/petsc/petsc-current/include/petscpc.h.html
You can click on the names to be taken to man pages.
However, since preconditioners are by nature problem-dependent, it's a better
idea to try to look up what migh
26 matches
Mail list logo
