[ENH] Use non-parametric method for regression z-statistic estimation #461
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
** Update: Closed in favor of a better implementation of the parametric approach by @CesarCaballeroGaudes
Closes #178.
Essentially, the problem is that the approach we use in
computefeats2
to calculate voxel-wise z-values (not z-statistics) associated with our components is rather odd and wrong. See this notebook for a simple comparison of methods, looking at RMSE compared to a slow, but valid, method.The current problem is that I'm getting the following error:
I believe that the error is due to voxels with no variability.
Changes proposed in this pull request:
permuted_ols
method withincomputefeats2
to calculate valid regressor-wise z-statistics for multiple regressions even with low degrees of freedom.