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.
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
Implementation of Triply Periodic Minimal Surfaces (TPMS) in OpenMC #3292
base: develop
Are you sure you want to change the base?
Implementation of Triply Periodic Minimal Surfaces (TPMS) in OpenMC #3292
Changes from 20 commits
194c53a
cad5288
34dfcbc
aba087b
4b64056
d135cc9
ff3c463
c01af03
5456834
d737e1a
1baeb79
0e89a7a
e3a9932
887929a
5e110f2
d68db81
c7c1d02
dd4d98f
fe2018b
c730d3a
23f626b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally, the base class shouldn't have to have any methods like this. I believe this is not in line with the "dependency inversion principle" which, if followed, means you'll have cleaner object oriented code. do you know of any other way to accomplish this without letting the base class know we're dealing with a TPMS surface?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, I tried to do a dynamic casting first, like the following:
But it felt even more dirty, and it might hurt cases where there are a lot of surfaces. Moreover, we can probably generalize that feature to allow ray-tracing optimization to other surfaces.
Let me know which solution would be best.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah yeah, you shouldn't need to use a dynamic case. ideally, you would just put virtual methods on the surface class that make it behave correctly. dynamic casting means you have done your abstractions poorly. do you have any ideas about what the general logic at hand here might be?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Basically, I do the following in the cell.cpp:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably leave this as =0. That prevents programmer mistakes and ensures that base classes implement this method, which will surely be unique for each surface type.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had to edit that part because of the special treatment of tpms :
cell.cpp l833
I am open to another solution but I always failed to create an object surface which is specifically is a
SurfaceTPMS
orSurfaceFunctionTPMS
.