-
Notifications
You must be signed in to change notification settings - Fork 484
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
DAGMC Test via Python Interface #1119
Conversation
…on't expect a geometry.xml file.
Oops, one more is in here too. The |
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.
Looks good! We don't really need a separate dagmc_xml
test though, so I'd suggest just having this test be the sole dagmc test in regression_tests/dagmc/
Can you remove the extra |
@paulromano for sure. Error in the directory move. Thanks! |
tests/regression_tests/dagmc/test.py
Outdated
mats = openmc.Materials([u235, water]) | ||
model.materials = mats | ||
|
||
harness = HashedPyAPITestHarness('statepoint.5.h5', model=model) |
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.
Let's stick with PyAPITestHarness
so the results don't get hashed (we generally only use that if the results file would be huge). Sorry, last request, I promise!
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.
Haha no worries! That makes sense. Updating...
This adds a test for DAGMC with a model setup using the Python interface.
The only external change needed was a check during model export to determine if it uses a DAGMC geometry - in which case no geometry.xml file is created.
This was to avoid having to spoof a universe for the OpenMC geometry like this.