Consistent python wrapper function names by pcarruscag · Pull Request #1978 · su2code/SU2

Skip to content

Navigation Menu

Sign in

Appearance settings

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Conversation

@pcarruscag

Copy link

Member

I've tried to follow some convention for naming the functions. We were using "SetMarkerCustomXX" for CHT-type boundary conditions, so I extended that to other applications.
"Custom" means that the values set this way act as boundary conditions. Whereas the other accessors allow manipulating the state (e.g. for initialization) but do not change the final solution.
I also tried to disambiguate the terms for Flow loads of the flow solver vs FEA solver and mesh deformation.

Copy link

Contributor

@jtneedels jtneedels left a comment

Choose a reason for hiding this comment

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

This LGTM.

@pcarruscag pcarruscag merged commit 77fa207 into develop

Mar 23, 2023

@pcarruscag pcarruscag deleted the consistent_py_wrapper_func_names branch

March 23, 2023 23:06

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

Reviewers

@WallyMaier WallyMaier WallyMaier approved these changes

@jtneedels jtneedels jtneedels approved these changes

Assignees

No one assigned

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@pcarruscag @WallyMaier @jtneedels