Skip to content

Create OGS-5 direct Neumann boundary conditions (in OGS-5: source terms)#1346

Merged
TomFischer merged 1 commit intoufz:masterfrom
TomFischer:createNeumannTool
Aug 18, 2016
Merged

Create OGS-5 direct Neumann boundary conditions (in OGS-5: source terms)#1346
TomFischer merged 1 commit intoufz:masterfrom
TomFischer:createNeumannTool

Conversation

@TomFischer
Copy link
Copy Markdown
Member

createNeumannBc --result-out <output file name> --property-name <string (property name)> --in-mesh <filename for mesh input>

The tool integrates the given element property (given via switch property-name) and writes the computed data as a PropertyVector with the name node_aggregated_gwn into the mesh. The tool also outputs an OGS-5 direct source term (Neumann boundary condition) data file, i.e., first column is the id of the mesh node and second column contains the integrated value.

@chleh
Copy link
Copy Markdown
Collaborator

chleh commented Aug 12, 2016

Only curious: What means "gwn" in node_aggregated_gwn?

"boundary condition",
true,
"",
"filename for mesh input");
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.

Should it maybe be stressed, that the mesh is the surface mesh?

@chleh
Copy link
Copy Markdown
Collaborator

chleh commented Aug 12, 2016

My comments basically address documentation. Afterwards 👍

@chleh
Copy link
Copy Markdown
Collaborator

chleh commented Aug 16, 2016

👍

Comment thread MeshLib/MeshSurfaceExtraction.h Outdated
/// to cells
/// @param prop_name name of the cell based property within the \c mesh
/// @return vector of integration value associated to the surface mesh nodes
static std::vector<double> getSurfaceIntegratedValueForNodes(
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 suggest moving these integration functions to somewhere else. The functions are nothing to do with surface extraction.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

@norihiro-w You are right. I'm unsure where the correct place is. Should it go to NumLib/Fem/Integration or do you have a better suggestion?

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'm also unsure. it could be placed under

  • MeshLib/MeshEditing or new dir Utils (?)
  • new dir NumLib/Integration
  • ProcessLib/Utils

NumLib/Fem/Integration isn't a good place for this because it focuses on element-level integration.

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.

Or move the code into the cmdline tool until we have a second use for it?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

MeshLib/MeshEditing or MeshLib/Utils or into the cmdline tool sounds good.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

It does not fit into MeshEditing since the mesh is not edited. So I moved the piece of code to the command line tool.

@endJunction
Copy link
Copy Markdown
Member

⏩ after suggested changes...

@TomFischer TomFischer merged commit 583c542 into ufz:master Aug 18, 2016
@TomFischer TomFischer deleted the createNeumannTool branch August 18, 2016 04:42
@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.

5 participants