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
I have in my event file for example condition_1 and condition_2 and contrast conditions and cond_1_gt_cond_2.
When running the results workflow, it fails since the code is set to:
line 387 of bidsResults.m
% skip contrast with name ending in _[0-9]* as they are run level
% contrasts
So, I might suggest adding somewhere (FAQ? A warning within bidspm?) that naming a contrast *_a-number is not a good idea.
The behavior now is either
in case it is asked to print only 1 contrast, the process does not start cause matlabbatch is empty, or
in case of multiple contrasts where one is named "correctly" and the other is not it just thrown an error that field dir does not exist (if you want to know more about this error LMK cause it is a bit long to write here and not sure it is relevant)
ps: I lied, I did not check if an issue exists already OR if it is already written somewhere 😇
The text was updated successfully, but these errors were encountered:
On seconds thought I think your suggestion may be better: especially that you can easily rename the conditions in your TSV using variable transformation in the BIDS stats model
Is there an existing issue for this?
New feature
No response
Unclear documentation
I have in my event file for example
condition_1
andcondition_2
and contrastconditions
andcond_1_gt_cond_2
.When running the results workflow, it fails since the code is set to:
line 387 of
bidsResults.m
So, I might suggest adding somewhere (FAQ? A warning within bidspm?) that naming a contrast
*_a-number
is not a good idea.The behavior now is either
in case it is asked to print only 1 contrast, the process does not start cause matlabbatch is empty, or
in case of multiple contrasts where one is named "correctly" and the other is not it just thrown an error that
field dir does not exist
(if you want to know more about this error LMK cause it is a bit long to write here and not sure it is relevant)ps: I lied, I did not check if an issue exists already OR if it is already written somewhere 😇
The text was updated successfully, but these errors were encountered: