Skip to content

established PlumeMeshUtils.py#116

Draft
andytorrestb wants to merge 5 commits into
plume-kit:masterfrom
andytorrestb:refactor/rename_rpod-andy
Draft

established PlumeMeshUtils.py#116
andytorrestb wants to merge 5 commits into
plume-kit:masterfrom
andytorrestb:refactor/rename_rpod-andy

Conversation

@andytorrestb
Copy link
Copy Markdown
Member

established PlumeMeshUtils.py so remove repeated simulation logic.

TODO: inspect extracted methods and try to understand if they belong here or should be in another class? Please read comments for further details.

NOTE: This could end up being a temporary file. If functions are better handled by other classes/files.

Copy link
Copy Markdown
Member Author

@andytorrestb andytorrestb left a comment

Choose a reason for hiding this comment

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

These are most likely better defined at the Vehicle level. Please move to the Vehicle class and manually trace through errors to ensure no test cases are broken.

@andytorrestb
Copy link
Copy Markdown
Member Author

andytorrestb commented Oct 2, 2025

Recent commits work towards addressing this issue. One open question persists: should build_thruster_link be a method defined within Vehicle.py? or is it better handled as a utility?

Overall, how should we handle utilities?

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.

1 participant