-
Notifications
You must be signed in to change notification settings - Fork 588
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
[MRG] ReNA_mrg #1983
[MRG] ReNA_mrg #1983
Conversation
Hello, @GaelVaroquaux or @bthirion Thanks |
Can you add ReNA to the end of examples/03_connectivity/plot_rest_parcellations.py as use this as the sole example for ReNA. |
I left a bunch of comments, but this is all I have. Thanks! |
What do you suggest please, I am not sure to understand... To me, the threshold
is simply a precision parameter,
You mean a tolerance? In which case it should be called "tol".
|
Let's call it `tolerance`.
…On Thu, May 2, 2019, 19:12 Gael Varoquaux ***@***.***> wrote:
> What do you suggest please, I am not sure to understand... To me, the
threshold
> is simply a precision parameter,
You mean a tolerance? In which case it should be called "tol".
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1983 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB6SXRG2GFOOSGEOGIKY4HTPTMOHFANCNFSM4HF5YASQ>
.
|
No to me, "tolerance" is the good nomenclature when optimizing something, here it is a precision parameter:
and
|
Then why not call it `precision` .
…On Thu, May 2, 2019, 19:24 Jerome-Alexis Chevalier ***@***.***> wrote:
No to me, "tolerance" is the good nomenclature when optimizing something,
here it is a precision parameter:
# Dealing with eccentricities, there are probably many neares neighbors
edge_mask = connectivity_.data > 1 - threshold
and
weights_ = np.maximum(threshold, weights_)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1983 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB6SXRFFUA4EGHXVQIFUO7DPTMPTPANCNFSM4HF5YASQ>
.
|
There's a typo in neares of nearest neighbour .
…On Thu, May 2, 2019, 19:25 Kshitij Chawla ***@***.***> wrote:
Then why not call it `precision` .
On Thu, May 2, 2019, 19:24 Jerome-Alexis Chevalier <
***@***.***> wrote:
> No to me, "tolerance" is the good nomenclature when optimizing something,
> here it is a precision parameter:
>
> # Dealing with eccentricities, there are probably many neares neighbors
> edge_mask = connectivity_.data > 1 - threshold
>
> and
>
> weights_ = np.maximum(threshold, weights_)
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#1983 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AB6SXRFFUA4EGHXVQIFUO7DPTMPTPANCNFSM4HF5YASQ>
> .
>
|
OK, I want this parameter removed from the parcellation object. It's an
algorithmic detail. We make a choice as a good default, and remove it.
|
Cool.
It's easy to add it back in if necessary.
Removing it once we have added it is... well, I'll have to write another
decorator. 😉
…On Thu, May 2, 2019, 19:27 Gael Varoquaux ***@***.***> wrote:
OK, I want this parameter removed from the parcellation object. It's an
algorithmic detail. We make a choice as a good default, and remove it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1983 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB6SXREUUK475HT2OHHUQZDPTMP6PANCNFSM4HF5YASQ>
.
|
Removing it once we have added it is... well, I'll have to write another decorator. 😉
How's your code?
Decorated!
|
@kchawla-pi
|
@kchawla-pi |
I don't have a system at hand. Will look at it once I return, if it is still a problem. |
@GaelVaroquaux @bthirion @kchawla-pi |
@GaelVaroquaux I will give this one more glance but at this point it should be good to go. You have anything more to say? |
Great! Congratulations!! |
Continue #1336