SNESSetUp() and matrix-free options
    Barry Smith 
    bsmith at mcs.anl.gov
       
    Thu May  7 16:07:13 CDT 2009
    
    
  
    I understand this. I just don't view this as a big deal worth  
changing the code over.
   Barry
On May 7, 2009, at 4:03 PM, Jed Brown wrote:
> Barry Smith wrote:
>>
>> I don't have a problem with (somehow) merging the two options, but I
>> don't see it as a big improvement.
>>
>>   -snes_mf -snes_mf_type both or operator
>>
>> instead of -snes_mf or -snes_mf_operator
>>
>> I don't see this as a big improvement.
>
> The difference is that
>
>  -snes_mf -snes_mf_operator
>
> is a conflict, but
>
>  -snes_mf -snes_mf_type both -snes_mf -snes_mf_type operator1
> -snes_mf_type operator2
>
> is not a conflict because it collapses to
>
>  -snes_mf -snes_mf_type operator2
>
>
> This isn't a big deal when all the options are on the command line,  
> but
> it is definitely nicer if some options are sitting in .petscrc or  
> being
> pulled in with -options_file.
>
> Jed
>
    
    
More information about the petsc-dev
mailing list