-
Notifications
You must be signed in to change notification settings - Fork 95
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
Add component selection documentation #84
Comments
@jwe080, it'd be great to have your expertise here, too ! |
Since the reorganization happening in #247 I think this issue should be paused. |
With #262 merged I am unpausing this issue. |
In line with many of the other issues I've commented on, I think that we should come up with a discrete set of tasks to close this issue. From the above, I could envision something like the following:
|
Given the interest in rewriting the decision tree, it seems that this issue is likely going to be solved as new code is written and documented. I think this issue is on probation. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions to tedana:tada: ! |
It would be great to have more documentation on what component selection entails. This is only covered in a very general way at this point and could be enormously expanded.
As @jbpoline had suggested, it would be great at some point to have automatically generated jupyter notebooks (using sphinx-gallery), but to start with I'd love to have a break down of the kappa, rho calculations and how various points in the decision tree impact those metrics.
One other piece: I know @handwerkerd has some examples from his
meica-reports
-- this section could be a great place to include those, until we generate some of our own !The text was updated successfully, but these errors were encountered: