onflicts.
Jed
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20090507/3eca4b1d/attachment.pgp>
tes
Desc: OpenPGP digital signature
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20090507/eed52097/attachment.pgp>
L:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20090507/f4f4b9fb/attachment.pgp>
mcs.anl.gov/pipermail/petsc-dev/attachments/20090507/005f44e8/attachment.pgp>
How about?
-snes_mf (means what it currently means)
-snes_mf operator (means what -snes_mf_operator means)
Barry
On May 7, 2009, at 6:03 PM, Lisandro Dalcin wrote:
> On Thu, May 7, 2009 at 6:14 PM, Jed Brown wrote:
>> Barry Smith wrote:
>>>
>>>I understand this. I just don
On Thu, May 7, 2009 at 6:14 PM, Jed Brown wrote:
> Barry Smith wrote:
>>
>> ? ?I understand this. I just don't view this as a big deal worth
>> changing the code over.
>
> I agree. ?My comment was that *if* the options were to be changed, as
> Lisandro was suggesting, then it would be better to el
On Thu, May 7, 2009 at 5:24 PM, Jed Brown wrote:
> Barry Smith wrote:
>>
>> On May 7, 2009, at 3:00 PM, Lisandro Dalcin wrote:
>
>>> 2) What should happen if a user pass BOTH options -snes_mf and
>>> -snes_mf_operators? Error? One of them should overrides the other?
>>
>> ? ?An error.
>
> The tric
On Thu, May 7, 2009 at 5:14 PM, Barry Smith wrote:
>>
>> 3) I would like to add a call to set matrix-free programatically...
>> something like SNESSetUseMFFD(snes,...). Any signature suggetions
>> regarding my previous discussions about the many options?
>
> ? No need to add this. One can already
On Wed, May 6, 2009 at 5:53 PM, Barry Smith wrote:
>
> ? It is ok with me if you try moving it all.
>
Ok, I've already started to work on this.
1) I would like to condensate -snes_mf_operator and -snes_mf_operator2
in a single option, were you have to pass the version, 1 or 2 (the
fist by defaul
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_m
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.
Barry
On May 7, 2009, at 3:47 PM, Jed Brown wrote:
> Bar
One could have -snes_mf override -snes_mf_operator that would make
sense.
There is no hierarchy of options (first, last, in files etc) in
order to keep the model
simple.
It is always possible someone has two options that conflict with
each other in the
options database. This is
On May 7, 2009, at 3:00 PM, Lisandro Dalcin wrote:
> On Wed, May 6, 2009 at 5:53 PM, Barry Smith
> wrote:
>>
>> It is ok with me if you try moving it all.
>>
>
> Ok, I've already started to work on this.
>
> 1) I would like to condensate -snes_mf_operator and -snes_mf_operator2
> in a single
13 matches
Mail list logo
