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

Basic implementation and test for connection threshold #128

Merged
merged 3 commits into from
Aug 1, 2020

Conversation

jefferis
Copy link
Contributor

  • note that checkmate was already an indirect dependency
  • @romainFr any comments? Also what do you think should happen when we have specified an ROI? Should the threshold apply to the total connectivity or to the ROI connectivity alone? Right now it is the former but I suspect it should be the latter ...

@romainFr
Copy link
Collaborator

Useful addition, thanks! I do agree that the filter should be on ROI weight -- we've been thresholding mostly on ROI weight in our analysis. Alternatively, one could have one threshold for the ROI and one threshold for the neuron?

@jefferis
Copy link
Contributor Author

Useful addition, thanks! I do agree that the filter should be on ROI weight -- we've been thresholding mostly on ROI weight in our analysis.

OK.

Alternatively, one could have one threshold for the ROI and one threshold for the neuron?

I think I would probably keep it simple. Part of my motivation was just to avoid transferring a lot of n=1 or 2 connections. I think people can add secondary threshold criteria themselves if they want.

jefferis added 2 commits July 31, 2020 19:32
* note that checkmate was already an indirect dependency
* the cypher got a bit hairy so I actually only apply the ROI weight threshold to downloaded data.
* I'm sure there must be a way to apply it on the server in a multi-level query.
@jefferis jefferis force-pushed the feature/connection-table-threshold branch from c08da3e to 2b4592e Compare July 31, 2020 18:33
* this is just to ensure consistency after various changes in dplyr/tibble that more aggressively return tibbles
  (which are nice but ...)
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