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
Here is the new error we run into while running the new 1.5.0 container. I think we can workaround this by simply not using the session directory as part of file name.
+ singularity run --cleanenv docker://poldracklab/fmriprep:1.5.0 --notrack --resource-monitor --skip_bids_validation --stop-on-first-crash --use-plugin=multi_proc.yml --output-spaces fsaverage5:res-2mm fsnative:res-2mm T1w:res-2mm template:res-2mm --force-bbr --force-syn --fs-license-file=.license.txt --skull-strip-template=NKI --work-dir=fmripworkdir --participant_label=sub-TTTEMPSUB fmripinput fmripout participant
�[91mERROR : Could not write to /N/soft/rhel7/singularity/2.6.1/var/singularity/mnt/final/etc/localtime: Too many levels of symbolic links
�[0mProcess Process-2:
Traceback (most recent call last):
File "/usr/local/miniconda/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
self.run()
File "/usr/local/miniconda/lib/python3.7/multiprocessing/process.py", line 99, in run
self._target(*self._args, **self._kwargs)
File "/usr/local/miniconda/lib/python3.7/site-packages/fmriprep/cli/run.py", line 547, in build_workflow
layout = BIDSLayout(str(bids_dir), validate=False)
File "/usr/local/miniconda/lib/python3.7/site-packages/bids/layout/layout.py", line 212, in __init__
indexer.index_metadata()
File "/usr/local/miniconda/lib/python3.7/site-packages/bids/layout/index.py", line 349, in index_metadata
md_val))
ValueError: Conflicting values found for entity 'session' in filename /N/dc2/scratch/brlife/carbonate-workflows/5d9b87504ff6d3df3337f364/5d9b87504ff6d3736c37f367/fmripinput/sub-TTTEMPSUB/ses-SSSES/anat/sub-TTTEMPSUB_ses-SSSES_run-1_T1w.nii.gz (value='SSSES') versus its JSON sidecar (value='1'). Please reconcile this discrepancy.
The text was updated successfully, but these errors were encountered:
Here is the new error we run into while running the new 1.5.0 container. I think we can workaround this by simply not using the session directory as part of file name.
The text was updated successfully, but these errors were encountered: