-
Notifications
You must be signed in to change notification settings - Fork 10
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 query key population_type
#229
Conversation
Actually, not quite true but we never claim that we'd support it: circuit.edges.get({"population_type": "chemical"})
# returns: {"population_type": "chemical"} (dict)
circuit.edges.get({"population_type": "chemical", properties=["afferent_section_id"]})
# returns: pd.DataFrame with what you'd expect Same happens with other queries used with |
62caac8
to
3073a67
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #229 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 33 32 -1
Lines 2743 2712 -31
=========================================
- Hits 2743 2712 -31
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
10df397
to
a137e70
Compare
I think this is good to go, yeah? Seems reasonable to me, I think. |
Added a query key
population_type
to query edge / node ids based on population type.Examples:
Closes #228