FCP-INDI / C-PAC

Configurable Pipeline for the Analysis of Connectomes
https://fcp-indi.github.io/
GNU Lesser General Public License v3.0
62 stars 40 forks source link

TypeError: must be encoded string without NULL bytes, not str #371

Closed LouiseP closed 9 years ago

LouiseP commented 9 years ago

Hi,

I’ve installed the new version of CPAC and the new versions of ANTs , NiPype, and CPAC image resources. When running the individual level analysis, I get the following error:

Process Process-1: Traceback (most recent call last): File "/usr/lib/python2.7/multiprocessing/process.py", line 258, in _bootstrap self.run() File "/usr/lib/python2.7/multiprocessing/process.py", line 114, in run self._target(_self._args, *_self._kwargs) File "/usr/local/lib/python2.7/dist-packages/CPAC/pipeline/cpac_pipeline.py", line 2467, in prep_workflow template_dataflow = create_mask_dataflow(c.templateSpecificationFile, 'templatedataflow%d' % num_strat) File "/usr/local/lib/python2.7/dist-packages/CPAC/utils/datasource.py", line 80, in create_mask_dataflow if not os.path.exists(mask_file): File "/usr/lib/python2.7/genericpath.py", line 18, in exists os.stat(path) TypeError: must be encoded string without NULL bytes, not str

Do you have any idea what this might be? I've never seen this error before.

Thanks a lot, Louise

sgiavasis commented 9 years ago

Hello,

This sounds like it is coming from the path you supplied for the "ROI Specification File" (either one) under the tab "ROI Voxelwise TSE" in the Time Series Extraction section of the pipeline configuration editor.

Double-check the paths you supplied; these should be text files that include paths to mask .nii.gz files.

Let me know and I can help further.

LouiseP commented 9 years ago

Thanks. This was coming from the paths I specified for the Network Centrality mask. I had a specified a .nii.gz file where I should have had a .txt file. My mistake, sorry. Louise

sgiavasis commented 9 years ago

Glad that fixed it!

No need to apologize, this is actually helpful for us because it highlights where we can introduce more informative error messages or where we can make things more intuitive, so it's still an issue.

Let us know if you need any more help.