PennLINC / xcp_d

Post-processing of fMRIPrep, NiBabies, and HCP outputs
https://xcp-d.readthedocs.io
BSD 3-Clause "New" or "Revised" License
75 stars 26 forks source link

FD Thresh arg error #1302

Open juansanchezpena opened 4 days ago

juansanchezpena commented 4 days ago

Summary

xcp_d: error: unrecognized arguments: --fd-thresh 0.3 xcp_d: error: ambiguous option: --f could match --file-format, --fd-thresh, --fd_thresh, --fs-license-file

fd_thresh 0.3 WORKED!

Additional details

What were you trying to do?

fun xcp-d on fmriprep 24.0.1 output:

What did you expect to happen?

conainer launch

What actually happened?

errors above until I used fd_thresh

Reproducing the bug

a " --mode none --participant-label patensasc0085 --input-type fmriprep --file-format cifti --despike  fd_thresh 0.3 -p 36P -m y --motion-filter-type notch --band-stop-min 12 --band-stop-max 18 --output-type interpolated --min-coverage 0"

tsalo commented 4 days ago

Can you share the full command you used that failed, as well as the full command that succeeded?

juansanchezpena commented 4 days ago

Thanks for the prompt reply, I was a bit green in saying it worked. I had an error with the syntax for spike denoise, it seems to be running fine with -f now. Will report if anything changes

From: Taylor Salo @.> Date: Tuesday, October 22, 2024 at 11:26 AM To: PennLINC/xcp_d @.> Cc: Sanchez, Juan (NYSPI) @.>, Author @.> Subject: Re: [PennLINC/xcp_d] xcp_d: error: FD Thresh arg error (Issue #1302)

ATTENTION: This email came from an external source. Do not open attachments or click on links from unknown senders or unexpected emails.

Can you share the full command you used that failed, as well as the full command that succeeded?

— Reply to this email directly, view it on GitHubhttps://github.com/PennLINC/xcp_d/issues/1302#issuecomment-2429592366, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARKALFBZIGVYF2LABKLSX63Z4ZVBFAVCNFSM6AAAAABQMXPUWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRZGU4TEMZWGY. You are receiving this because you authored the thread.Message ID: @.***>