-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
B0FieldIdentifier: some characters should be replaced to set workflow name to avoid crashes in graph creation #295
Comments
Replaced offending characters in my B0Field* tags and it works now, if that can help anyone encountering that issue. |
Ah, thanks for that. I think we assumed it would be a camel case string. |
We use the B0FieldIdentifier as an entity at the output (estimated fieldmaps). But the B0FieldIdentifier can definitely have hyphens, so we probably want to revise the workflow names and the datasinks. |
This is turning out not to be resolvable purely in sdcflows. fMRIPrep at least (and thus probably nibabies and maybe dMRIPrep) use I think the fix, as @mgxd says in #434 (comment) is to make the sanitized ID available through the object API. We will then use that internally, and downstream tools need to transition. If the sanitized ID replaces non-alphanumeric characters with OTOH we would be introducing a new API feature, so it might make sense to call it 2.9.0, regardless. WDYT? And do we care about getting this in for fMRIPrep 24.0, or should we leave it to the next round of releases? |
FMRIPrep version 20.1.0
Not sure if that is in fMRIPrep or SDCFlows that the workflow name is set, but I get the following error if B0FieldIdentifier contains a
-
, and this will likely occur for other characters (I have no knowledge on dot files syntax though).dot file contains something like
fmriprep_wf_single_subject_01_wf_fmap_preproc_wf_in_b0id-test
on the offending line.The text was updated successfully, but these errors were encountered: