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
Hi,
I was reading the way temporal filtering is implemented using the cosine model and except I was a bit confused from the fact that is written as a low-pass filter while it is a high-pass filter as also stated in #295 (An error that is actually propagated in nistats too https://github.com/nistats/nistats/blob/master/nistats/design_matrix.py#L87) I also think I noticed something else.
Thx for the comments.
Note that here, ou plan is to stray away from SPm conventions and provide the frequency in Herz.
Note thate the cosine drift provides a basis for a low-pass filter of the data; the fact that it is treated as a nuisance parameters makes the whole thing a high-pass filtering. We should probably coroect the wording (PR welcome ---in nistats: the orriginal nipy code is dead).
Regarding whether we should consider the last regressor or not, it depends whether you consider the noud as incluisve or exclusive ;-) We took the conservative option, but I have no strong opinion on that.
Best,
B
Thanks for replying,
the documentation Create a cosine drift matrix with periods greater or equals to period_cut gave me the idea its should be inclusive.
Except from that though in the case when the calculated order is exact to the one matching the cutt-of, skipping it is the conservative option.
On the other hand at the cases where the order is not exact (where using the floor func makes the difference) using that order would be already conservative. Skipping it is not necessary and makes it too conservative.
For example, using the same data as in the example above but using a cutoff of 100s
order = floor(2120(1/100)*2) = floor(4,8)= 4
in that case using 4 would be the conservative choice but using 3 (this is the default now) is too conservative.
If skipping is kept maybe using round instead of floor would be more even.
Also stop skipping and using the inclusive option would be fine. Are there any disadvantages to that?
Will some frequencies a bit less than the cut-off also be regressed out? I believe so but again not many
Ok! I will make the changes proposed both here and in nistats and open PRs . Do you think they have not chance of being merged here? I see some commits up to October. I would like to go straight to nistats but I am waiting for it to stabilize.
On Thu, 20 Dec 2018, 12:51 pm Takis Panagopoulos ***@***.*** wrote:
Ok! I will make the changes proposed both here and in nistats and open PRs
. Do you think they have not chance of being merged here? I see some
commits up to October. I would like to go straight to nistats but I am
waiting for it to stabilize.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#448 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAEIHBgcoybrEtRX_mHlxtkZxqghhxEVks5u64e2gaJpZM4ZaHT8>
.
Activity
bthirion commentedon Dec 19, 2018
takhs91 commentedon Dec 19, 2018
Thanks for replying,
the documentation
Create a cosine drift matrix with periods greater or equals to period_cutgave me the idea its should be inclusive.Except from that though in the case when the calculated order is exact to the one matching the cutt-of, skipping it is the conservative option.
On the other hand at the cases where the order is not exact (where using the floor func makes the difference) using that order would be already conservative. Skipping it is not necessary and makes it too conservative.
For example, using the same data as in the example above but using a cutoff of 100s
order = floor(2120(1/100)*2) = floor(4,8)= 4
in that case using 4 would be the conservative choice but using 3 (this is the default now) is too conservative.
If skipping is kept maybe using round instead of floor would be more even.
Also stop skipping and using the inclusive option would be fine. Are there any disadvantages to that?
Will some frequencies a bit less than the cut-off also be regressed out? I believe so but again not many
bthirion commentedon Dec 19, 2018
I'm fine with not skipping.
Best, B
takhs91 commentedon Dec 20, 2018
Ok! I will make the changes proposed both here and in nistats and open PRs . Do you think they have not chance of being merged here? I see some commits up to October. I would like to go straight to nistats but I am waiting for it to stabilize.
matthew-brett commentedon Dec 20, 2018