-
Notifications
You must be signed in to change notification settings - Fork 10
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 named Cells #76
Comments
In GitLab by @tjlaboss on May 25, 2022, 13:23 Syntactically, there's no way to tell if a comment is a name. I think that is a one-way street. Nevertheless, the |
So you think it should only be user set and valid while in memory? Should it be added to the comments? What's the OpenMC way of doing this? |
In GitLab by @tjlaboss on May 25, 2022, 14:30 OpenMC objects have a IMO if an object doesn't have a natural name, like the SCn or FCn cards, then the name should be written as a comment. No preference as to whether it's prepended as a comment card or added as an inline |
In GitLab by @tjlaboss on May 25, 2022, 15:00 Another thought: if a name is written as a comment, MCNPy could potentially check if it just wrote that string, to avoid doubling and tripling up on identical comments through multiple passes. |
Yeah so |
Are you going to do this or should I boot it to the next release? |
Coming back to this: it sounds a lot like a custom embedded syntax: #344. |
This idea came from @tjlaboss.
The idea is that rather than just referring to a cell by its number, which is mutable, could we refer to it and request it by a string?
Something like
cell.name
possibly?This is already somewhat clunkily possible through comments, however it is clunky.
My main concern with this is: how do you preserve those names through saving to and reading from a file? My thought would be to add them as a preceding comment. However, how do you know it's a name and not just a general comment? We might need to introduce a special comment syntax. This is starting to sound like Mo.py and that concerns me.
The text was updated successfully, but these errors were encountered: