Closed tiborauer closed 3 years ago
if you have just a single sample, why on earth would you want to do a tfce for multiple comparison correction ?
A single sample (per channel) still means multiple samples (in case you have more than one channel), therefore, correction for multiple comparisons is still required. It is, in fact, the most common case for MRI.
oh, but then the data are '1-dimensional', right?
Right. Then what is the solution for the issue?
you tell me
If I could, then it would be a PR and not an issue. :)
I tried a few things, but then I broke the case for multi-dimensional (as originally framed in test_clusterstat.m) data.
'cluster', interestingly, works for 0D (per channel) data.
One difference, I have noticed that the input to findcluster
is usually logical for 'cluster' but always double for 'tfce'. I can see how it can cause an issue in findcluster (line 119)
(see the error above); however, when spacereshapeable
, the input becomes double for 'cluster', too.
Thank you for the quick response!
Describe the bug TFCEstat fails for zero-dimensional (i.e. single value) data
To Reproduce Steps to reproduce the behavior (modified version of test_clusterstat):
Expected behavior Error:
Environment and versions (please complete the following information):
Additional context Add any other context about the problem here. The issue seems to be specific to zero-dimensional data, and does not occur when testing with 1-, 2-, or 3-dimensional data (per channel). However, I have noticed that TFCE seems to be less sensitive than 'cluster' in the current implementation (tested with test_clusterstat after changing line 75 to
cfg.correctm = 'tfce';
); but I cannot tell whether it is related to the issue or due to the inherent nature of the TFCE and 'cluster'.