- #1
chang-ho
- 1
- 1
- TL;DR
- I don't know what the problem is.
I hope someone can solve this problem.
Help with error please: "dump 1 on file" on MCNP
Click For Summary
Discussion Overview
The discussion revolves around the "dump 1 on file" message encountered in MCNP, focusing on the nature of dump files, their purpose, and the implications for users. The scope includes technical explanations and diagnostic considerations related to the MCNP software.
Discussion Character
- Technical explanation, Diagnostic clarification
Main Points Raised
- Some participants explain that the dump file is a normal part of MCNP operation, occurring at the start and end of a run, and potentially at other times depending on settings.
- It is noted that the dump file can contain useful information for debugging or restarting runs, particularly regarding particle tracking.
- One participant suggests that sharing the str.run file along with the str.txt source file could provide additional diagnostic insights.
- Another participant asserts that the issue has been resolved, indicating that the dump file does not signify an error and that there are no error messages in the output file.
Areas of Agreement / Disagreement
Participants generally agree that the dump file is a normal feature of MCNP operation. However, there is no consensus on the necessity of sharing additional files for diagnostic purposes, as some participants suggest it while others do not address this point.
Contextual Notes
The discussion does not clarify specific settings or conditions under which the dump files are generated, nor does it address any potential limitations of the information contained within the dump files.
- #2
DEvens
Homework Helper
Education Advisor
Gold Member
- 1,246
- 508
The dump thing is not a problem. By default, MCNP does a dump at the start of the run, and another at the end. And, depending on the settings and options, it may do additional dumps during the run.
The dump file contains information that may be useful for other purposes. For example, it may be useful in debugging or in re-starting a run to add more particles.
It will also print out additional information at each dump. You should be aware that there may be, for example, multiple reports of tallies. So the first (and all but the last, as there can be several) report of a tally may happen before all of your particles have been run.
You can control some of the dump process using the PRDMP card. Read up in the user manual about this card. It can be very useful when you are doing debug on a model.
The dump file contains information that may be useful for other purposes. For example, it may be useful in debugging or in re-starting a run to add more particles.
It will also print out additional information at each dump. You should be aware that there may be, for example, multiple reports of tallies. So the first (and all but the last, as there can be several) report of a tally may happen before all of your particles have been run.
You can control some of the dump process using the PRDMP card. Read up in the user manual about this card. It can be very useful when you are doing debug on a model.
- #3
sysprog
- 2,617
- 1,793
The dump file, as @DEvens indicated, contains information that could be useful for diagnostic purposes, so perhaps it would be just as well to also post the str.run file, instead of just posting the str.txt source file the processing of which caused the dump to be generated.
- #4
DEvens
Homework Helper
Education Advisor
Gold Member
- 1,246
- 508
sysprog said:
The question has been sorted. The dump file is normal operation. There are no error messages in the output file produced.
Similar threads
- · Replies 3 ·
- · Replies 1 ·
- · Replies 4 ·
- · Replies 1 ·
- · Replies 10 ·
- · Replies 1 ·
- · Replies 1 ·
- · Replies 1 ·
- · Replies 6 ·
- · Replies 4 ·