You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for RotamerConvolveMD the program is very helpful to our research.
I have problems with segmentation faults for some distance pairs of a MD simulation. The program runs for a while and then crashes at a certain frame.
Step 1057/4442 [ 23.8%]Segmentation fault<
Increasing the clashDistance changes the frame the segmentation fault occurs. If I start the program a few frames before the frame where the segmentation fault occurred (e.g. by setting --discard=1055), I cannot reproduce the segmentation fault (i.e. I cannot really narrow it down to a specific frame). The test scripts work without any problem. I tried this on Debian buster and bullseye both using native python (2.7 and 3.7) and anaconda as well as anaconda on an OSX system and got the same error.
Any suggestions what I could do to solve or narrow down the problem?
The text was updated successfully, but these errors were encountered:
Thank you for RotamerConvolveMD the program is very helpful to our research.
I have problems with segmentation faults for some distance pairs of a MD simulation. The program runs for a while and then crashes at a certain frame.
Increasing the clashDistance changes the frame the segmentation fault occurs. If I start the program a few frames before the frame where the segmentation fault occurred (e.g. by setting --discard=1055), I cannot reproduce the segmentation fault (i.e. I cannot really narrow it down to a specific frame). The test scripts work without any problem. I tried this on Debian buster and bullseye both using native python (2.7 and 3.7) and anaconda as well as anaconda on an OSX system and got the same error.
Any suggestions what I could do to solve or narrow down the problem?
The text was updated successfully, but these errors were encountered: