Allow custom node set and blocks IDs #103
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also, fix a bug bith exo output
isteinbrecher
temporarily deployed
to
cubit_secrets_trusted
GitHub Actions
Inactive
danielwolff1
approved these changes
Aug 14, 2025
Contributor
danielwolff1
left a comment
danielwolff1
left a comment
There was a problem hiding this comment.
Thanks for the addition, looks good to me!
Feel free to proceed with merging and then I will rebase #102 accordingly 🚀
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow the user to set custom IDs for node sets and blocks in the exo file.
@maxfirmbach this should now really resolve #76
This PR also fixes a hidden issue that occurred if node sets of multiple geometry types were exported to yaml/exo.