[RESOLVED] Unknown error occur--AttributeError: 'NoneType' object has no attribute 'lower'

Issues
1

Hi all,

I get the following unknown error message when executing hcp_pre_freesurfer:

Session id: FCS103C
[started on Monday, 24. March 2025 04:57:14]
Running HCP PreFreeSurfer Pipeline [LegacyStyleData] ...

ERROR: Unknown error occured:
...................................
Traceback (most recent call last):
  File "/opt/qunex/python/qx_utilities/hcp/process_hcp.py", line 806, in hcp_pre_freesurfer
    hcp = getHCPPaths(sinfo, options)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/qunex/python/qx_utilities/hcp/process_hcp.py", line 249, in getHCPPaths
    ] or options["hcp_bold_dcmethod"].lower() in [
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'lower'
...................................
...

---> Final report for command hcp_pre_freesurfer
... FCS103A ---> PreFS failed

My command is:

		qunex_container hcp_pre_freesurfer \
		    --sessionsfolder="${WORK_DIR}/${STUDY_NAME}/sessions" \
                    --sessions="${SUBJ}" \
		    --batchfile="${WORK_DIR}/${STUDY_NAME}/processing/batch.txt" \
                    --container="${QUNEX_CONTAINER}" \
                     --parsessions="${PARSES}" \
		    --hcp_processing_mode="${hcp_processing_mode}" \
		    --hcp_t2="${hcp_t2}" \
                    --hcp_avgrdcmethod="NONE" \
                    --bind="${WORK_DIR}:${WORK_DIR}" \
                    --overwrite="yes"

where,
hcp_processing_mode=LegacyStyleData|
hcp_t2=NONE
hcp_bold_dcmethod=NONE
QUNEX_CONTAINER=“gitlab.qunex.yale.edu:5002/qunex/qunexcontainer:1.1.1”

What are the possible reasons for this error? Thanks for your kindly help!

Best, Acacius

2

Seems like a bug, can you try bypassing it by setting also

--hcp_bold_dcmethod="NONE"

You are currently only setting hcp_avgrdcmethod.

Best, Jure

3

Hi, Jure

It seems to work now! Thanks for your help!

Best,
Acacius

4

Great! The bug is already fixed and will be released in the next QuNex version. For the time being, you need to use the workaround described above. Sorry for the inconvenience.

Best, Jure