-
Notifications
You must be signed in to change notification settings - Fork 5
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
$SB_EXECFILE error message #12
Comments
I figured in previous versions, I was using "-patch 1 1" to prevent patch processing. But this generated this error in the newest versions where "-patch 0 0" is required instead. |
Actually, this error is still in the latest version we use on SBgrid and only seems to happen when -OutImod is set to "2" (AreTomo format). Everything runs well up to the last steps it seems. |
Hi @ncoudray, is there any way to solve it? |
I haven't found a way to solve it. I used -OutImod option 1 instead and try to work with this outputt |
OK, I have tried with other number for -OutImod. But sometimes it worked, sometimes not. |
Hi,
I tried to run AreTomo2 (from SBgrid installation), and I get the following error message:
/data/apps/extern/sbgrid/share/capsules/lib/job.sh: line 126: 2156235 Segmentation fault (core dumped) "$SB_EXECFILE" "$@"
I tried different versions (AreTomo2_1.0.0_Cuda118, AreTomo2_c7_Cuda122) which gave the same error. I noticed the v1.3.4 lead to the the same message (AreTomo_1.3.4_Cuda112_Feb22_2023, AreTomo_1.3.4_Cuda116_Feb22_2023).
However, older versions do work on the same images (and comparable cuda version) - (AreTomo_1.3.3_Cuda112_11212022, AreTomo_1.3.3_Cuda116_11212022, AreTomo_1.3.0_Cuda116_09292022).
Any idea why the newer version would fail with such a message on our cluster?
Thanks,
Best,
Nicolas
The text was updated successfully, but these errors were encountered: