[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Using MAT_NO_NEW_NONZERO_LOCATIONS and MAT_SYMMETRIC give error
- To: petsc-users@xxxxxxxxxxx
- Subject: Re: Using MAT_NO_NEW_NONZERO_LOCATIONS and MAT_SYMMETRIC give error
- From: "Matthew Knepley" <knepley@xxxxxxxxx>
- Date: Tue, 27 May 2008 11:13:12 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=48SsLif+0IkTqWrUgh8Dbn3Xp6W9/AADyO+IpOPFoLg=; b=cfheOgbBWP5fF3cWKgU2M+cgpSotlF1TAoE6h/acuTYL5Nb6zE7+LdieOXnf5Op8V8EeTufXwIo+6uDNEVEC94xTvq3dNTJVDvO70w8obAMmLpcfctyveOls5PTC6FbdtUpyGOAC/kYj//9c9PnOWDAzerhDSSTLCHkETi0sCAo=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Uz9SkjorvsaOZ7T0p7nvCzp0KpgnLJvIrmwFTMfRia+6hl/OR2CRrGkzC1mRdRaeXxVOI54DS/xJIgiPCY7LjUhRn722dNQw2QgOejduo2ZTAEQCDBoHoDyTAFWH9v7iBJWVIiNrUuNGSoxt5EJ6icSd1uxpqPXj/daYrZ1wF64=
- In-reply-to: <483C2FBF.90509@gmail.com>
- References: <483C2FBF.90509@gmail.com>
- Reply-to: petsc-users@xxxxxxxxxxx
- Sender: owner-petsc-users@xxxxxxxxxxx
On Tue, May 27, 2008 at 10:58 AM, Ben Tay <zonexo@xxxxxxxxx> wrote:
> Hi,
>
> I read in the manual that I can use either call
> MatSetOption(A_mat_uv,MAT_NO_NEW_NONZERO_LOCATIONS,PETSC_TRUE,ierr) or call
> MatSetOption(A_mat,MAT_SYMMETRIC,PETSC_TRUE,ierr).
>
> When I use MAT_NO_NEW_NONZERO_LOCATIONS for the matrix formed by my momentum
> eqn, I get the error on my home computer udring compiling:
>
> :\Myprojects2\imb_airfoil_x2_parallel\mom_disz.f90(356) : Error: This name
> does not have a type, and must have an explicit type.
> [MAT_NO_NEW_NONZERO_LOCATIONS]
> call MatSetOption(A_mat_uv,MAT_NO_NEW_NONZERO_LOCATIONS,PETSC_TRUE,ierr)
1) It appears this symbol was not defined for Fortran. This is fixed
in petsc-dev.
> Although this error does not happen when I compile in linux, I can this
> error during run:
>
> [0]PETSC ERROR:
> ------------------------------------------------------------------------
> [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation,
> probably memory access out of range
> [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
> [0]PETSC ERROR: or see
> http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSC
> ERROR: or try http://valgrind.org on linux or man libgmalloc on Apple to
> find memory corruption errors
> [0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and
> run
> [0]PETSC ERROR: to get more information on the crash.
> [0]PETSC ERROR: --------------------- Error Message
> ------------------------------------
> [0]PETSC ERROR: Signal received!
> [0]PETSC ERROR:
> ------------------------------------------------------------------------
>
> I use KSPRICHARDSON and PCILU for my momentum eqn matrix.
>
> When I use MatSetOption(A_mat,MAT_SYMMETRIC,PETSC_TRUE,ierr) for my poisson
> eqn which is symmetric, I get the same error as above during run. Btw, I'm
> using hypre as the preconditioner and default solver.
This option does not actually do anything. The SEGV must come from
another error.
Matt
> May I know why using these options give the error?
>
> Thank you very much.
>
> Regards.
>
>
>
--
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which
their experiments lead.
-- Norbert Wiener