-
Notifications
You must be signed in to change notification settings - Fork 8
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
Compare results of using mctal_merge and ZWelch's version #9
Comments
There are a few differences between mctal_merge and mctal_combine.py that I am not sure why they differ. Lines 12, 13, and 15 have an extra 0 at the end of the line in merge_mctal that isn't in any of the input files. Other than those lines they produce very similar results. I ran into a bug when testing the meshtal_combine.py, hopefully will have that fixed later today. merge_mctal
mctal_combine.py
|
Is there another one coming, or is this somehow both? |
sorry, I accidentally hit comment before I was done. It should be correct now |
I've mostly got meshtal_combine.py working, the only difference I am seeing is in the first line with the ld parameter. Im looking through the mcnp documentation but havent found anything helpful yet. The only other difference is one prints 1.0 out as 1.00000e-00 and the other prints it out as 1.00000e+00. I can't imagine that being a problem but I figured I should mention it just in case merge_mctal
mine
|
Need to define expected functionality of all operation modes of the mesh_merge script, see #12 |
Compare the results produced by mctal_merge and @zwelchWI version of this implemented using python. To ensure that we get the same results, (averages and errors) in both cases.
The text was updated successfully, but these errors were encountered: