Skip to content
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

Split brain networks #125

Open
wants to merge 47 commits into
base: master
Choose a base branch
from
Open

Conversation

Islast
Copy link
Collaborator

@Islast Islast commented Jul 4, 2019

  • I'm ready to merge
    Not at all. This is just a preview of my proposed changes to seperate the BrainNetwork class into two distinct subclasses: BinaryBrainNetwork and WeightedBrainNetwork.
  • What's the context for this pull request?
    (this is a good place to reference any issues that this PR addresses)
    Ruslan discovered that when you run the threshold method on an already binarised graph it returns garbage.
    This made me think that there are potentially a lot of situations where treated a weighted network like a binary network or vice versa could be disastrous.

  • What's new?
    My thinking is that the difference between a weighted and a binarised brain network should be very explicit since it's going to determine what sort of analyses we can do on it.

It should be possible to threshold a WeightedBrainNetwork into a BinaryBrainNetwork and it should be possible to initialise a WeightedBrainNetwork from a correlation matrix.

A BinaryBrainNetwork should support all of the network analysis methods. We could run these on a weighted graph no problem, but they would tell us nothing about our data. We will record the original weightings on existent BinaryBrainNetworks in case we want to restrict our focus to fewer edges later (the specific use case being plotting).

  • What should a reviewer feedback on?
    Is this the right direction to go in to solve this problem.

  • Does anything need to be updated after merge?
    (e.g the wiki or the WhitakerLab website)

docs and tutorials would certainly need to be updated, but it's a little early for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants