<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 27/06/16 13:44, Barry Smith wrote:<br>
</div>
<blockquote
cite="mid:165B0002-DF4F-47D8-8BAF-7C829A20887E@mcs.anl.gov"
type="cite"> Yes, you are correct, there is no MatFDSetType() and
in the SetFromOptions we totally cheat
<a class="moz-txt-link-freetext" href="http://www.mcs.anl.gov/petsc/petsc-current/src/mat/matfd/fdmatrix.c.html#MatFDColoringSetFromOptions">http://www.mcs.anl.gov/petsc/petsc-current/src/mat/matfd/fdmatrix.c.html#MatFDColoringSetFromOptions</a>
and just stick the value directly into the data structure. For now
you can call
<pre wrap="">
PetscOptionsSetValue(NULL,"-mat_fd_type","ds") in your code (before you start using the MatFD stuff) and we'll add the routine to the master branch.</pre>
</blockquote>
<br>
Thanks, that workaround does the trick for now.<br>
<blockquote
cite="mid:165B0002-DF4F-47D8-8BAF-7C829A20887E@mcs.anl.gov"
type="cite">
<pre wrap="">I didn't think anyone would care about the difference between ds and wp with MatFD.</pre>
</blockquote>
It makes a noticeable difference for the problem I'm solving right
now. That may be because the problem is not non-dimensionalized (as
yet anyway) and so some of the solution elements are of different
magnitudes than others. If I non-dimensionalize them it may possibly
not matter any more about wp or ds.<br>
<br>
- Adrian<br>
<pre class="moz-signature" cols="72">--
Dr Adrian Croucher
Senior Research Fellow
Department of Engineering Science
University of Auckland, New Zealand
email: <a class="moz-txt-link-abbreviated" href="mailto:a.croucher@auckland.ac.nz">a.croucher@auckland.ac.nz</a>
tel: +64 (0)9 923 84611
</pre>
</body>
</html>