[petsc-users] PetscOptionsGetString Not Finding Option

[Matthew Knepley]

On Tue, Nov 3, 2015 at 9:01 PM, Jared Crean <jcrean01 at gmail.com> wrote:

>   Hell Hong,
>         Is there a way to directly query the options database to get the
> value of Petsc options?  This is related to the discussion here:
> http://lists.mcs.anl.gov/pipermail/petsc-dev/2015-July/017944.html .  I
> though PetscOptionsGetString and PetscOptionsSetValue would provide this
> capability, but now it seems like petsc options cannot be accessed.
>

I am not sure what you mean. This


http://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/Sys/PetscOptionsGetString.html

will get the raw input string for any option. The other functions return
processed versions. What else do you want?

   Matt

    Jared Crean
>
> On 11/01/2015 10:19 AM, Hong wrote:
>
> Jared :
> Either call KSPSetPCSide() or change
> const char name[] = "-ksp_pc_side"
> to a non-petsc option name, e.g., "-my_ksp_pc_side".
>
> Hong
>
> Hello,
>>     I am trying to use PetscOptionsGetString to retrieve the value of an
>> option in the options database, but the value returned in the last argument
>> indicates the option was not found.   In the attached code (a modified
>> version of ksp example 2), the string "-ksp_pc_side" is passed in as the
>> argument name. If I run the code as
>>
>>     ./jc2 -pc_type ilu -ksp_pc_side right
>>
>>     I get the output:
>>
>>     option -ksp_pc_side was found
>>
>>     from line 71 of the file.  Petsc does not complain of unused options
>> when the program finishes.  Am I using this function incorrectly?
>>
>>     Jared Crean
>>
>
>
>


-- 
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20151103/27321599/attachment.html>