Skip to content
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

Automatic error handling of missing/incomplete mcnp output file #12

Open
jamesbevins opened this issue Feb 23, 2018 · 2 comments
Open
Assignees
Labels
Milestone

Comments

@jamesbevins
Copy link
Collaborator

This can happen a couple of ways:
a) Geometry error and particles got lost
b) Filesystem error and the file wasn't saved
c) Run time timeout

For b and c, it would be best to keep running instead of failing. The same is probably also true of a), but there should definitely be a prominent warning added to the logfile (maybe a separate one? or slurm.out?)

@jamesbevins
Copy link
Collaborator Author

I implemented a version of this in Gnowee Utilities. All it does is prevent the whole program from crashing by using try/except, but it is a start.

@jamesbevins jamesbevins added this to the v2.0 milestone Mar 18, 2019
@SandraBogetic
Copy link

Hi James, regarding this bug especially point a). So while working on the mcnp geometry input file reading I was thinking about such error. So I thought have error alert in a slurm.out file that alerts that the mcnp output has a "lost particle" info error which usually means geometry error, would that work? Without stopping the run correct? Would we want still to have that MCNP input file printed out ?

For point b) do you mean an MCNP input file?

For point c) do you mean for the single run?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants