JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for FSL Archives


FSL Archives

FSL Archives


FSL@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

FSL Home

FSL Home

FSL  November 2018

FSL November 2018

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: eddy_cuda on centos7

From:

Bennet Fauber <[log in to unmask]>

Reply-To:

FSL - FMRIB's Software Library <[log in to unmask]>

Date:

Fri, 16 Nov 2018 08:34:46 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (149 lines)

The segfaulting by eddy_cuda appears to have been due to several
combinations of problems in with one or both the input .nii file or
the file used for --slspec.  Clearly one should be doubly certain that
the number of slices reported by the nifti file and the number of
lines in the slspec file agree.  In case is is of any use to anyone
else, we have now got

#!/bin/bash snippet, not for csh

# run fslinfo on the input file, get the number part of the output
# for dimension 3, which is the number of slices
slices=$(fslinfo $nifti_file | grep ^dim3 | awk '{ print $2 }')

# count the number of lines in the fslspec file and save just the number
slspec_lines=$(wc -l $slspec_file | awk '{ print $1 }')

echo "fslinfo says the image file has $slices slices"
echo "the slspec file has $slspec_lines lines in it"

# check to make sure the two numbers agree; if they do, move on
# if they don't, stop right there and exit with an error number 9
if [ $slices -eq $slspec_lines ] ; then
    echo "Those agree.  Continuing to process data..."
else
    echo "Disagreement about the number of slices.  I quit."
    exit 9
fi

We are running this on a compute cluster, and eddy_cuda is being
called from mrtrix3, so this checks prior to running the dwidenoise,
which takes a long time, and will reduce the time spent waiting for
the error to be evident.

Sorry for the noise on the list.  I hope someone finds the snippet above useful.


On Wed, Nov 14, 2018 at 10:30 AM Bennet Fauber <[log in to unmask]> wrote:
>
> I am replying to this thread, as it seems like my problem might be
> related.  If not, I can resubmit as a separate issue.
>
> I have a researcher trying to replicate an analysis that was done in
> June.  They are running the same commands -- one person gave over the
> cluster setup script and I am pretty sure that only the subject ID has
> changed.
>
> Here is the command we are running with the version I got for FSL 5.0.10:
>
> [bennet@flux-build bin]$ ls -l eddy_cuda-5.0.10
> -rwxr-xr-x 1 bennet swinstaller 40525310 Apr 24  2017 eddy_cuda-5.0.10
>
> [bennet@flux-build bin]$ md5sum eddy_cuda
> afa454d92c75542924ca36313b70d36c  eddy_cuda
>
> [hajenna@nyx7500 dwipreproc-tmp-FDLY57]$ eddy_cuda \
>    --imain=eddy_in.nii --mask=eddy_mask.nii \
>    --acqp=eddy_config.txt --index=eddy_indices.txt \
>    --bvecs=bvecs --bvals=bvals --niter=8 --fwhm=10,6,4,2,0,0,0,0 \
>    --repol --ol_type=both --mporder=8 --s2v_niter=8 --dont_peas \
>    --ol_type=both --mporder=8 --s2v_niter=8 --slspec=slspec.txt \
>    --out=dwi_post_eddy
> Entering EddyGpuUtils::LoadPredictionMaker
>
> ...................Allocated GPU # 0...................
> Entering EddyGpuUtils::LoadPredictionMaker
> Entering EddyGpuUtils::LoadPredictionMaker
> Entering EddyGpuUtils::LoadPredictionMaker
> Entering EddyGpuUtils::LoadPredictionMaker
> Entering EddyGpuUtils::LoadPredictionMaker
> Entering EddyGpuUtils::LoadPredictionMaker
> Entering EddyGpuUtils::LoadPredictionMaker
> Entering EddyGpuUtils::LoadPredictionMaker
> Segmentation violation, Address not mapped, Offending address = (nil)
> eddy_cuda ) [0x47d73a] [
> eddy_cuda ) [0x4ab1b1] [
> eddy_cuda ) [0x49c517] [
> eddy_cuda ) [0x4096e3] [
> eddy_cuda ) [0x40ca08] [
> eddy_cuda ) [0x40db2c] [
> /lib64/libc.so.6 __libc_start_main [0x2b3504d84445]
> eddy_cuda ) [0x405f69] [
>
> I tried the version that I got for FSL 5.0.11 with this result.
>
> [bennet@flux-build bin]$ ls -l eddy-5.0.11_cuda7.5
> -rwxrwxr-x 1 bennet swinstaller 33505739 Sep 21  2017 eddy-5.0.11_cuda7.5
>
> [bennet@flux-build bin]$ md5sum eddy-5.0.11_cuda7.5
> 5e7edd5288d3b0b7834e9ca244bf7dee  eddy-5.0.11_cuda7.5
>
> [hajenna@nyx7500 dwipreproc-tmp-FDLY57]$ eddy-5.0.11_cuda7.5
> --imain=eddy_in.nii --mask=eddy_mask.nii --acqp=eddy_config.txt
> --index=eddy_indices.txt --bvecs=bvecs --bvals=bvals --niter=8
> --fwhm=10,6,4,2,0,0,0,0 --repol --ol_type=both --mporder=8
> --s2v_niter=8 --dont_peas --ol_type=both --mporder=8 --s2v_niter=8
> --slspec=slspec.txt --out=dwi_post_eddy
>
> ...................Allocated GPU # 0...................
> Segmentation violation, Unknown reason, Offending address = (nil)
> eddy-5.0.11_cuda7.5 ) [0x49ff01] [?
> eddy-5.0.11_cuda7.5 ) [0x4c62b1] [?
> eddy-5.0.11_cuda7.5 ) [0x4bb8c9] [?
> eddy-5.0.11_cuda7.5 ) [0x412c0d] [?
> eddy-5.0.11_cuda7.5 ) [0x413974] [?
> eddy-5.0.11_cuda7.5 ) [0x40798e] [?
> /lib64/libc.so.6 __libc_start_main [0x2b2d00589445]
> eddy-5.0.11_cuda7.5 ) [0x40ef31] [?
>
> Here is the `nvidia-smi` output for the card in the machine (there are
> more GPUs, but I thought the rest would be redundant).
>
> +-----------------------------------------------------------------------------+
> | NVIDIA-SMI 390.48                 Driver Version: 390.48                    |
> |-------------------------------+----------------------+----------------------+
> | GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
> | Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
> |===============================+======================+======================|
> |   0  Tesla K20Xm         On   | 00000000:09:00.0 Off |                    0 |
> | N/A   27C    P8    16W / 235W |      0MiB /  5700MiB |      0%   E. Process |
> +-------------------------------+----------------------+----------------------+
>
> We use modules, and the cuda/7.5 module is loaded, and produces
>
> [bennet@nyx7500 ~]$ nvcc --version
> nvcc: NVIDIA (R) Cuda compiler driver
> Copyright (c) 2005-2015 NVIDIA Corporation
> Built on Tue_Aug_11_14:27:32_CDT_2015
> Cuda compilation tools, release 7.5, V7.5.17
>
> [bennet@nyx7500 ~]$ uname -r
> 3.10.0-693.11.6.el7.x86_64
>
> If I swap with the cuda/6.5 modules, then it says it can't find libcudart.so.7.5
>
> [hajenna@nyx7500 dwipreproc-tmp-FDLY57]$ eddy_cuda --imain=eddy_in.nii
> --mask=eddy_mask.nii --acqp=eddy_config.txt --index=eddy_indices.txt
> --bvecs=bvecs --bvals=bvals --niter=8 --fwhm=10,6,4,2,0,0,0,0 --repol
> --ol_type=both --mporder=8 --s2v_niter=8 --dont_peas --ol_type=both
> --mporder=8 --s2v_niter=8 --slspec=slspec.txt --out=dwi_post_eddy
> eddy_cuda: error while loading shared libraries: libcudart.so.7.5:
> cannot open shared object file: No such file or directory
>
> So I am pretty sure we are matched with cuda libraries.

########################################################################

To unsubscribe from the FSL list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=FSL&A=1

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager