-
Notifications
You must be signed in to change notification settings - Fork 25
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
LN_NOISE_KERNEL: How to estimate anisotropic smoothness from its output? #97
Comments
Hi @samtorrisi, |
hi Renzo- that definitely sounds like a lot of work and from a developer stand-point i totally get why you'd not want to add extra dependencies. i'll give rolling-my-own a shot with either matlab or python, no prob and thanks for considering! -Sam |
I will look into this in summer after OHBM. I think I might be able to implement the Gaussian fitting from scratch. Thanks @samtorrisi for bringing this this program and the blog post section back to our attention. |
oh wow, well thank you @ofgulban, if you think it'll have wider interest at least give it a shot. note that i wouldn't be using Gaussian estimates for cluster correction (which Eklund et al 2016 and Cox et al 2017 demonstrated were problematic) but rather need relative but quantitative differences between different pulse sequences, for example. yes it can wait until after OHBM and have fun there! |
Hi Renzo and Faruk-
I have data that I know is smoother in one dimension than the others. It seems
LN_NOISE_KERNEL
can theoretically provide anisotropic smoothing estimates but according to Figure 10 herehttps://layerfmri.com/2020/04/06/qa/
I'll still have to do steps 6 and 7 on my own, right?
So I'm curious if you have some ready-made code to do that so I don't have to build from scratch.
I simply need the FWHM in units of voxels or mm for the x, y and z dimensions separately.
this would be for both low res and high res functional data (although i don't think that matters for this tool?)
let me know what you think and thanks!
-Sam
The text was updated successfully, but these errors were encountered: