Mixed file parse + API set of options

bri...@sandia.gov

unread,

Apr 7, 2017, 11:25:49 AM4/7/17

to QUESO-users mailing list

The new GPMSAOptions class appears to have the flexibility to default construct and then overlay options through the C++ API or an input file, in whichever order I choose, e.g., C++, input file, then potentially more C++ overrides (or just input file then C++ overrides).

It appears other options classes such as EnvOptionsValues (MH, SIP) are a bit more limited. It seems I could construct from file, then override through C++, but not the reverse. Is that correct?

Related, it seems when constructing a FullEnvironment, if EnvOptionsValues* alternativeOptionsValues is passed, then the input file isn't parsed. I think this means that if EnvOptionsValues allowed me to construct, set through C++, then parse, I could pass this object to the Environment and get the behavior I seek...

Brian

Roy Stogner

unread,

Apr 21, 2017, 6:00:14 PM4/21/17

to Adams, Brian M, Damon McDougall (damon@ices.utexas.edu), queso...@googlegroups.com

On Fri, 21 Apr 2017, Adams, Brian M wrote:

> Damon/Roy – Not sure if this crossed your desk.

Nope! Turns out I was subscribed to queso-dev, but not queso-users.

> The new GPMSAOptions class appears to have the flexibility to
> default construct and then overlay options through the C++ API or an
> input file, in whichever order I choose, e.g., C++, input file, then
> potentially more C++ overrides (or just input file then C++
> overrides).

Right.

> It appears other options classes such as EnvOptionsValues (MH, SIP)
> are a bit more limited. It seems I could construct from file, then
> override through C++, but not the reverse. Is that correct?

I believe so. When I got a hold of GPMSAOptions there was just
parsing in the constructor, no method to do a delayed parse, and I
*only* upgraded GPMSAOptions, not any of the other options classes.

> Related, it seems when constructing a FullEnvironment, if
> EnvOptionsValues* alternativeOptionsValues is passed, then the input
> file isn't parsed. I think this means that if EnvOptionsValues
> allowed me to construct, set through C++, then parse, I could pass
> this object to the Environment and get the behavior I seek...

It would. Start a ticket for it? Too late to get this into the
release tomorrow but it should be quick to do shortly after.
---
Roy

bma...@gmail.com

unread,

Apr 21, 2017, 6:23:20 PM4/21/17

to QUESO-users mailing list, bri...@sandia.gov, da...@ices.utexas.edu

Surely: https://github.com/libqueso/queso/issues/569

Reply all

Reply to author

Forward