Hello Matt,
There was a problem with the way I was doing the tests, not with PetscOptionsGetString. PetscOptionsGetString now behaves as expected in all tests. Sorry for the confusion.

        Jared Crean

On 11/03/2015 10:37 PM, Jared Crean wrote:
    Hello Matt,
Ok, something weird is going on. Some of my test cases are behaving strangely (the output of the test in my previous message is the expected behavior, but previously the test gave different results). Let me figure out what is going on with the tests before proceeding.

    Jared Crean

On 11/03/2015 10:07 PM, Matthew Knepley wrote:
On Sat, Oct 31, 2015 at 7:52 PM, Jared Crean <[email protected] <mailto:[email protected]>> wrote:

    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


You gave the options and the program says it was found. What is the problem here?

   Matt

    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


Reply via email to