File: EPSPowerSetNonlinear.html

package info (click to toggle)
slepc 3.14.2%2Bdfsg1-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 31,976 kB
  • sloc: ansic: 102,426; python: 3,151; makefile: 2,969; f90: 1,607; fortran: 1,525; sh: 250; cpp: 189
file content (56 lines) | stat: -rw-r--r-- 3,297 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML3.2 EN">
<HTML>
<HEAD> <link rel="canonical" href="https://slepc.upv.es/documentation/current/docs/manualpages/EPS/EPSPowerSetNonlinear.html" />
<META NAME="GENERATOR" CONTENT="DOCTEXT">
<link rel="stylesheet" href="/slepc.css" type="text/css">
<TITLE>EPSPowerSetNonlinear</TITLE>
</HEAD>
<BODY BGCOLOR="FFFFFF">
   <div id="version" align=right><b>slepc-3.14.2 2021-02-01</b></div>
   <div id="bugreport" align=right><a href="mailto:slepc-maint@upv.es?subject=Typo or Error in Documentation &body=Please describe the typo or error in the documentation: slepc-3.14.2 v3.14.2 docs/manualpages/EPS/EPSPowerSetNonlinear.html "><small>Report Typos and Errors</small></a></div>
<H1>EPSPowerSetNonlinear</H1>
Sets a flag to indicate that the problem is nonlinear. 
<H3><FONT COLOR="#883300">Synopsis</FONT></H3>
<PRE>
#include "slepceps.h" 
PetscErrorCode <A HREF="../EPS/EPSPowerSetNonlinear.html#EPSPowerSetNonlinear">EPSPowerSetNonlinear</A>(<A HREF="../EPS/EPS.html#EPS">EPS</A> eps,PetscBool nonlinear)
</PRE>
Logically Collective on eps
<P>
<H3><FONT COLOR="#883300">Input Parameters</FONT></H3>
<TABLE border="0" cellpadding="0" cellspacing="0">
<TR><TD WIDTH=40></TD><TD ALIGN=LEFT VALIGN=TOP><B>eps </B></TD><TD>&nbsp;- the eigenproblem solver context
</TD></TR>
<TR><TD WIDTH=40></TD><TD ALIGN=LEFT VALIGN=TOP><B>nonlinear </B></TD><TD>&nbsp;- whether the problem is nonlinear or not
</TD></TR></TABLE>
<P>
<H3><FONT COLOR="#883300">Options Database Key</FONT></H3>
<TABLE border="0" cellpadding="0" cellspacing="0">
<TR><TD WIDTH=40></TD><TD ALIGN=LEFT VALIGN=TOP><B>-eps_power_nonlinear </B></TD><TD>&nbsp;- Sets the nonlinear flag
</TD></TR></TABLE>
<P>
<H3><FONT COLOR="#883300">Notes</FONT></H3>
If this flag is set, the solver assumes that the problem is nonlinear,
that is, the operators that define the eigenproblem are not constant
matrices, but depend on the eigenvector: A(x)*x=lambda*B(x)*x. This is
different from the case of nonlinearity with respect to the eigenvalue
(use the <A HREF="../NEP/NEP.html#NEP">NEP</A> solver class for this kind of problems).
<P>
The way in which nonlinear operators are specified is very similar to
the case of PETSc's SNES solver. The difference is that the callback
functions are provided via composed functions "formFunction" and
"formJacobian" in each of the matrix objects passed as arguments of
<A HREF="../EPS/EPSSetOperators.html#EPSSetOperators">EPSSetOperators</A>(). The application context required for these functions
can be attached via a composed PetscContainer.
<P>

<P>
<H3><FONT COLOR="#883300">See Also</FONT></H3>
 <A HREF="../EPS/EPSPowerGetNonlinear.html#EPSPowerGetNonlinear">EPSPowerGetNonlinear</A>(), <A HREF="../EPS/EPSSetOperators.html#EPSSetOperators">EPSSetOperators</A>()
<BR><P><B><FONT COLOR="#883300">Location: </FONT></B><A HREF="../../../src/eps/impls/power/power.c.html#EPSPowerSetNonlinear">src/eps/impls/power/power.c</A>
<P><H3><FONT COLOR="#883300">Examples</FONT></H3>
<A HREF="../../../src/eps/tutorials/ex34.c.html">src/eps/tutorials/ex34.c.html</A><BR>
<BR><A HREF="./index.html">Index of all EPS routines</A>
<BR><A HREF="../../index.html">Table of Contents for all manual pages</A>
<BR><A HREF="../singleindex.html">Index of all manual pages</A>
</BODY></HTML>