Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add option to export to cub5 #112

Merged
merged 13 commits into from
Jun 4, 2024
Merged

add option to export to cub5 #112

merged 13 commits into from
Jun 4, 2024

Conversation

Edgar-21
Copy link
Contributor

@Edgar-21 Edgar-21 commented Jun 1, 2024

see #111, trying again but from a branch on the upstream to hopefully pass CI

closes #93

@Edgar-21
Copy link
Contributor Author

Edgar-21 commented Jun 3, 2024

Talking with @connoramoreno, it will likely be best to separate the cubit model building functionality from stellarator.export_dagmc() to allow for the separation of cub5 and DAGMC exports

@Edgar-21 Edgar-21 marked this pull request as draft June 3, 2024 19:34
Copy link
Collaborator

@connoramoreno connoramoreno left a comment

Choose a reason for hiding this comment

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

Some minor comments about formatting, some other questions and comments about code design.

parastell/parastell.py Outdated Show resolved Hide resolved
parastell/parastell.py Outdated Show resolved Hide resolved
parastell/cubit_io.py Outdated Show resolved Hide resolved
parastell/cubit_io.py Outdated Show resolved Hide resolved
parastell/parastell.py Outdated Show resolved Hide resolved
parastell/parastell.py Outdated Show resolved Hide resolved
parastell/parastell.py Outdated Show resolved Hide resolved
parastell/parastell.py Outdated Show resolved Hide resolved
)
cub5_export = all_data['cub5_export']
if cub5_export['export_cub5']:
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why do we need a export_cub5 flag if we're including a separate cub5_export dictionary in the YAML file?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm intending this to be optional behavior, but since there are no other args to get passed having the dict doesn't really make sense, I'll change it to just be a single element

parastell/parastell.py Outdated Show resolved Hide resolved
@Edgar-21 Edgar-21 marked this pull request as ready for review June 3, 2024 21:57
):
"""Exports DAGMC neutronics H5M file of ParaStell components via
Coreform Cubit.
def build_cubit_model(self, skip_imprint=False, legacy_faceting=True):
Copy link
Member

Choose a reason for hiding this comment

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

nice separation of concerns!! 👍

Copy link
Member

@gonuke gonuke left a comment

Choose a reason for hiding this comment

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

LGTM! Thanks @Edgar-21

Copy link
Collaborator

@connoramoreno connoramoreno left a comment

Choose a reason for hiding this comment

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

Looks good now!

@connoramoreno connoramoreno merged commit 1e26b75 into main Jun 4, 2024
1 check passed
@connoramoreno connoramoreno deleted the export_cub5 branch July 8, 2024 18:21
connoramoreno added a commit that referenced this pull request Sep 10, 2024
add option to export to cub5
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.

Add an option to save a Cubit cub file
3 participants