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

GLM: segmentation fault #40

Open
welton0411 opened this issue Oct 6, 2017 · 2 comments
Open

GLM: segmentation fault #40

welton0411 opened this issue Oct 6, 2017 · 2 comments

Comments

@welton0411
Copy link

Hi,
I was trying to analyze high-res fMRI using 'GLM' but received the error message below:

Authored by K.A. Eklund
Data size for run 1: 256 x 256 x 256 x 147
Data size for run 2: 256 x 256 x 256 x 147
Data size for run 3: 256 x 256 x 256 x 147
Data size for run 4: 256 x 256 x 256 x 147
Data size for run 5: 256 x 256 x 256 x 147
Data size for run 6: 256 x 256 x 256 x 147
Data size for run 7: 256 x 256 x 256 x 147
Data size for run 8: 256 x 256 x 256 x 147
Total data size: 256 x 256 x 256 x 1176
Number of original regressors: 7
Number of total regressors: 15
Number of contrasts: 13
Performing 13 t-tests
GLM -runs 8 data_dir/fmri_run1.nii.gz data_dir/fmri_run2.nii.gz data_dir/fmri_run3.nii.gz data_dir/fmri_run4.nii.gz data_dir/fmri_run5.nii.gz data_dir/fmri_run6.nii.gz data_dir/fmri_run7.nii.gz data_dir/fmri_run8.nii.gz -designfiles regress_run1.txt regress_run2.txt regress_run3.txt regress_run4.txt regress_run5.txt regress_run6.txt regress_run7.txt regress_run8.txt -mask data_dir/brainmask_crop.nii -contrasts contrast.txt -firstlevel -detrendingregressors 1 -output brc_: Segmentation fault

The size of each input file is ~850MB. Someone recommended me to put all the input & output files in the directory. I don't know why though. Any help will be highly appreciated.

@wanderine
Copy link
Owner

wanderine commented Oct 7, 2017 via email

@welton0411
Copy link
Author

Sure. Please see below:


Device info


Platform number: 0

Platform vendor: Intel(R) Corporation
Platform name: Intel(R) OpenCL
Platform extentions: cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_depth_images cl_khr_3d_image_writes cl_intel_exec_by_local_thread cl_khr_spir cl_khr_fp64
Platform profile: FULL_PROFILE


Device number: 0

Device vendor: Intel(R) Corporation
Device name: Intel(R) Xeon(R) CPU E5-2643 v3 @ 3.40GHz
Hardware version: OpenCL 1.2 (Build 25)
Software version: 1.2.0.25
OpenCL C version: OpenCL C 1.2
Device extensions: cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_depth_images cl_khr_3d_image_writes cl_intel_exec_by_local_thread cl_khr_spir cl_khr_fp64
Global memory size in MB: 257546
Size of largest memory object in MB: 64386
Global memory cache size in KB: 256
Local memory size in KB: 32
Constant memory size in KB: 128
Parallel compute units: 24
Clock frequency in MHz: 3400
Max number of threads per block: 8192
Max number of threads in each dimension: 8192 8192 8192


Any solution for the memory issue?

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

No branches or pull requests

2 participants