Skip to content

[PL] Add multicomponent boundary conditions.#1343

Merged
endJunction merged 3 commits intoufz:masterfrom
endJunction:MulticomponentBcs
Aug 12, 2016
Merged

[PL] Add multicomponent boundary conditions.#1343
endJunction merged 3 commits intoufz:masterfrom
endJunction:MulticomponentBcs

Conversation

@endJunction
Copy link
Copy Markdown
Member

@endJunction endJunction commented Aug 9, 2016

The main work was done before, but the parser was missing.

The default value for the component is 0 such that there is no need to add for single component variables.

TODO:

  • Documentation of the config param.
  • Changelog

@chleh
Copy link
Copy Markdown
Collaborator

chleh commented Aug 10, 2016

Regarding the default of zero: Then for multi-component-BCs one implicitly always sets BCs to component no. 0 if one forgets to explicitly specify it.
Could there be a check that for multi-component variables specifying the component is always mandatory, and for single-component variables it's not?

@endJunction
Copy link
Copy Markdown
Member Author

I'm adding an extra check, which in case of missing for multi-component variables will issue the following message:

error: ConfigTree: In file `../Tests/Data/Mechanics/Linear/square_1e0.prj' at path <process_variables/process_variable/boundary_conditions/boundary_condition>: Key <component> has not been found at ConfigTree.cpp, line 229

Comment thread ProcessLib/ProcessVariable.cpp Outdated
//! \ogs_file_param{boundary_condition__component}
bc_config.getConfigParameter<int>("component", 0);
if (_n_components > 1) {
bc_config.peekConfigParameter<int>("component");
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought peek after get doesn't work. At least I didn't want it to work in that order. ^^

@norihiro-w
Copy link
Copy Markdown
Collaborator

👍

@endJunction endJunction merged commit b574fa4 into ufz:master Aug 12, 2016
@endJunction endJunction deleted the MulticomponentBcs branch August 12, 2016 00:07
@ogsbot
Copy link
Copy Markdown
Member

ogsbot commented Jun 19, 2020

OpenGeoSys development has been moved to GitLab.

See this pull request on GitLab.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants