Help to run input file (MCNPX)

  • Thread starter Thread starter zakaria
  • Start date Start date
AI Thread Summary
An MCNPX simulation for internal radiotherapy is failing to run due to technical limitations on the user's machine. The user seeks assistance to verify the input file without requiring result analysis. Responses indicate potential errors in the input file, particularly with the "corc1" parameter, which may be incorrectly defined and could lead to fatal errors. Suggestions include correcting the "corc1" line to avoid zero volume mesh elements and ensuring proper angle definitions. The discussion emphasizes the importance of accurate input file formatting for successful simulation execution.
zakaria
Messages
2
Reaction score
0
Hello,

I'm working on an MCNPX simulation related to internal radiotherapy. Unfortunately, I'm currently unable to run the code on my machine due to technical limitations.

If possible, could someone kindly run the input file and share the output or let me know whether the simulation runs successfully?

I'm not asking for result analysis just a quick check to see if my input file is correct and executable.

Thank you very much in advance
 

Attachments

Last edited:
Engineering news on Phys.org
Welcome to PF.

zakaria said:
Unfortunately, I'm currently unable to run the code on my machine due to technical limitations.
What kind of limitations? We don't usually do folks' work for them.
 
berkeman said:
Welcome to PF.


What kind of limitations? We don't usually do folks' work for them.
Thank you very much for your reply.
I am not asking anyone to do my work for me, but I have tried many times to run the simulation myself without success. MCNPX stops immediately when the simulation starts.
 
Does it give any error message? What version of MCNP are you using?
 
There seems to be at least one mistake in the input file.
Code:
  cora1 0.0 0.023 2.3
  corb1 0 0.25 2.5
  corc1 0 1 90
Is this intended to produce a mesh containing 8 or 90'000 elements (voxels)?

For cylindrical geometry corc is the angle, it has to start with a 0, so this is implied. In MCNP this is really common, energy bins, histogram distributions etc. Putting an extra 0 on this line is asking for mesh elements (voxels) between angle 0 and angle 0, which have zero volume. This triggers a fatal error. That may be a cause of this input file not working. I also don't know if corc is supposed to end with a 360, some implementations of mesh need this.

So "corc1 1 90" would fix that error, but if the intention is 1 division per degree up to 90 degrees, then "corc1 89i 90" would do it and the other lines might also need fixing. i{n} interpolates n values and saves having long lists in the input file, it would be the same as corc1 [0] 1 2 3 4 5 .... 87 88 89 90.
 
Hello everyone, I am currently working on a burnup calculation for a fuel assembly with repeated geometric structures using MCNP6. I have defined two materials (Material 1 and Material 2) which are actually the same material but located in different positions. However, after running the calculation with the BURN card, I am encountering an issue where all burnup information(power fraction(Initial input is 1,but output file is 0), burnup, mass, etc.) for Material 2 is zero, while Material 1...
Hi everyone, I'm a complete beginner with MCNP and trying to learn how to perform burnup calculations. Right now, I'm feeling a bit lost and not sure where to start. I found the OECD-NEA Burnup Credit Calculational Criticality Benchmark (Phase I-B) and was wondering if anyone has worked through this specific benchmark using MCNP6? If so, would you be willing to share your MCNP input file for it? Seeing an actual working example would be incredibly helpful for my learning. I'd be really...
Back
Top