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
[DOC] Mention classification type in plot_haxby_glm_decoding.py #4122
Conversation
Addresses issue: nilearn#4109
👋 @TamerGezici Thanks for creating a PR! Until this PR is ready for review, you can include the [WIP] tag in its title, or leave it as a github draft. Please make sure it is compliant with our contributing guidelines. In particular, be sure it checks the boxes listed below.
For new features:
For bug fixes:
We will review it as quick as possible, feel free to ping us with questions if needed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thx. Can you make sure that the length of the lines is no more than 80 characters ?
Best,
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4122 +/- ##
==========================================
- Coverage 91.81% 91.76% -0.05%
==========================================
Files 144 144
Lines 16241 16241
Branches 3386 3386
==========================================
- Hits 14911 14904 -7
- Misses 789 791 +2
- Partials 541 546 +5 Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@TamerGezici thanks ! We need to break the lines up as suggested for standard formatting.
Can you also add a whatsnew entry to doc/changes/latest.rst
and your name to CITATION.cff
? (see https://nilearn.github.io/dev/development.html#changelog for more detail)
@TamerGezici are you able to finish this or would you like us to take over? |
Co-authored-by: Yasmin <63292494+ymzayek@users.noreply.github.com>
Co-authored-by: Yasmin <63292494+ymzayek@users.noreply.github.com>
I think it's good now I have a question though, here, all-vs-one clasification is done for which "one"? Or is it all classified against one, and then averaged for all pairs of all-vs-one classifications? It may be worth adding that to the end of DOC if that is so. |
@TamerGezici it is rather the latter, each condition classified against all for each group so you end up with |
You also need to add your name to CITATION.cff as a first time contributor |
Done. I didn't know a simple commit like this would qualify for that. Haha! |
You help clarifying something that was unclear to you and probably others: defo a contribution. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thx !
Addresses issue: #4109