ReactionMechanismGenerator / ReactionMechanismGenerator/RMG-database
Termination due to "uncaught exception"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 127
- Forks
- 160
- Avg merge
- 6d 2h
- Merged PRs (30d)
- 2
Description
Run was proceeding fine, adding reactions, when suddenly during reaction generation:
For reaction generation 7 processes are used.
libc++abi.dylib: terminating with uncaught exception of type std::runtime_error: Couldn't close file
Yesterday I got the same error in a different calculation, but the message repeated for 1000++ times before I killed the job. What is the cause, and can the problem be avoided?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported reaction-generation run using seven processes and the repeated "Couldn't close file" runtime error. Look for the relevant execution logs or traceback and establish a reproducible case; done means identifying the cause and documenting a verified way to avoid or resolve the termination.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100