-
Notifications
You must be signed in to change notification settings - Fork 44
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
Create more examples using nilearn #81
Comments
This seems like just an example right? How is this different than just showing an examples that includes lines similar to:
|
This is definitely an example not a core feature.
But it needs to handle some issues relating to dealing with multiple
subjects/networks. The expectation of the output is that sparse support
will be comparable across all of them in some sense.
Nilearn folks discourage using this base estimator for single graphs. But
as you point out. It is trivial for this naive usecase where we are
compatible.
…On Wed, Jan 18, 2017, 7:44 PM Jason Laska ***@***.***> wrote:
This seems like just an example right? How is this different than just
showing an examples that includes lines similar to:
from nilearn.connectome import ConnectivityMeasure
cm = ConnectivityMeasure(
cov_estimator=QuicGraphLassoCV, kind='precision'
)
cm.fit(...)
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#81 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAov98edkTxypKOgM5FJdvgpj1rvbf7Yks5rTtwGgaJpZM4LnozI>
.
|
@mnarayan -- this was an interesting discussion that I was hoping we could resume? My two cents on this is that the nilearn folks are correct that single precision matrices for single individuals are not comparable across individuals (i.e. where skggm is compatible). The philosophy behind PyNets, however, is that averages of global features across a distribution of precision matrices built upon multiple node definitions for single individuals are comparable across individuals, where skggm is compatible. Curious to hear your thoughts on this, and particularly whether you think this impacts how skggm's estimators should be used in such scenarios... -derek |
Hi @dpisner453. I think the issue of whether individual graphs are comparable or not depends on Last I checked nilearn's implementations prefer to assume shared model selection across all individuals and refits that model onto individual subject data. This is quite reasonable for the sorts of applications nilearn is used for like classification/clustering and so forth. I am familiar with nilearn's ConnectivityMeasure API. Does PyNets have something similar as well? If PyNets has an explicit separate subject estimation philosophy, then our current estimators will work easily for you out of the box. |
Thanks for the response @mnarayan ! Are you referring to population-based network estimators like lasso-penalized D-trace loss? I should clarify I am not suggesting the use of estimators that pool information across subjects, only those that pool information within subjects. Our initial focus has been on building better default estimators at the level of a single data matrix, not that no pooling ought to happen. We don't have anything implementing estimators for a population of networks yet. Last I checked nilearn's implementations prefer to assume shared model selection across all individuals and refits that model onto individual subject data. This is quite reasonable for the sorts of applications nilearn is used for like classification/clustering and so forth. PyNets does have the ability to access nilearn's ConnectivityMeasure API library of estimators but is also able, as you noted, to use skggm's estimators out-of-the-box. Very much looking forward to seeing what skggm comes up with next. -derek |
Since our estimators are sklearn compatible, we can enable those who use nilearn for graphical model estimation to use skggm estimators as well.
This would involve using ConnectivityMeasure from nilearn as a base estimator class (which is designed for dealing with multiple graphical models) and then creating an skggm relevant implementation under the hood. Would be useful for application examples, where a similar procedure would need to be applied in any case.
The text was updated successfully, but these errors were encountered: