-
Notifications
You must be signed in to change notification settings - Fork 146
RF: refactor DCT-II into more visible function #417
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
base: main
Are you sure you want to change the base?
Conversation
Codecov Report@@ Coverage Diff @@
## master #417 +/- ##
==========================================
- Coverage 83.22% 83.22% -0.01%
==========================================
Files 301 301
Lines 28149 28140 -9
Branches 3279 3278 -1
==========================================
- Hits 23428 23419 -9
Misses 3719 3719
Partials 1002 1002
Continue to review full report at Codecov.
|
@bthirion - will the requirement for continuous samples in time be a problem for you? https://github.com/nipy/nipy/pull/417/files#diff-9967264e8820787d766a0f3ee1e4ae67R42 |
@jbpoline - any comments? |
Use dedicated function for _cosine basis. This refactoring will require continuous times, otherwise it will raise an error. In any case, I believe that the values returned when times are not continuous are not valid: a) The current function assumes that all differences in volume times are equal to the difference in the first two volume times, and; b) The DCT values should (I believe) reflect the number of `dt` intervals, not the index into the time vector, as currently.
eba5309
to
f3be3ee
Compare
Gentlemen - I think the current function will be incorrect when the frametimes are not all equally spaced, do you agree? |
Make DCT-II basis an API function, use this function for DCT-II drift in
design_matrix.
@jbpoline - would you mind having a look at this one?