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
Hello,
We are currently conducting a revised audit outputs of our abcd-hcp-pipeline for the HBN site (RU). However, we have encountered a limitation wherein we only receive structural outputs and a single rest run output, unlike the other two sites that do not experience this issue. When using the original audit script, the following error occurs:
Traceback (most recent call last):
File "/panfs/jay/groups/6/faird/shared/projects/new_rae_testing/abcd-hcp-pipeline_audit/run.py", line 128, in <module>
sessions_to_analyze = [item['Prefix'].split('/')[2] for item in get_data if 'ses' in item['Prefix'].split('/')[2]]
File "/panfs/jay/groups/6/faird/shared/projects/new_rae_testing/abcd-hcp-pipeline_audit/run.py", line 128, in <listcomp>
sessions_to_analyze = [item['Prefix'].split('/')[2] for item in get_data if 'ses' in item['Prefix'].split('/')[2]]
TypeError: string indices must be integers
We appreciate your help and consideration
Additional details
CuBIDS version:
Datalad version:
What were you trying to do?
What did you expect to happen?
What actually happened?
Reproducing the bug
The text was updated successfully, but these errors were encountered:
@BaranMary sorry, but your traceback doesn't seem to be related to CuBIDS code. Could you provide a bit more detail? I also don't know what you mean by "audit script".
Summary
Hello,
We are currently conducting a revised audit outputs of our abcd-hcp-pipeline for the HBN site (RU). However, we have encountered a limitation wherein we only receive structural outputs and a single rest run output, unlike the other two sites that do not experience this issue. When using the original audit script, the following error occurs:
We appreciate your help and consideration
Additional details
What were you trying to do?
What did you expect to happen?
What actually happened?
Reproducing the bug
The text was updated successfully, but these errors were encountered: