-
Notifications
You must be signed in to change notification settings - Fork 3
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 'ignore' case to create_layered_volume #5
Conversation
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5 +/- ##
=======================================
Coverage ? 76.57%
=======================================
Files ? 4
Lines ? 175
Branches ? 0
=======================================
Hits ? 134
Misses ? 41
Partials ? 0
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
I added a couple of comments here plus this. |
hold on a little bit, I'm trying to find a regex that works, so it'll be easier that this (also to use same regex in other codes) |
Ok after some further investigation with Alexis, he found a new regex that would exclude the barrels: As an example for layer one, we switch from
What do you think? Here is a little snippet we used for testing this:
|
Looks good to me. Do the placement hints produced with this new regex match the expected result? |
Can it be simplified more to: IIRC, only layers Narrowing the |
Yes that works too, I have not tested the full placement hints, but the test would just need a new |
ah yes, the [ab] is only as in the original regex of course. Yes, narrowing I wasn't sure what were the bounds |
It also removes the leading |
yes, so I can use the same regex in synthesis later, without having to add this extra ignore thingy ;) |
Add an ignore case to
create_layered_volume
based on an optional key in the metadata dictionary to allow literature-based barrel column names with queries present in the pipeline.The regex cases (
"queries": ["@.*1[ab]?$", "@.*[2-3][ab]?$", "@.*4[ab]?$", "@.*5[ab]?$", "@.*6[ab]?$"]
) struggled with the following pattern:Where the name of the barrel includes one of the layer numbers at the end (1, 2, 3, 4, 5). So for example column name ending with number 1, i.e.
SSp-bfd-C1
, would be included in the indices found for layer 1.New suggested metadata has to follow this pattern (to be added into
atlas-placement-hints
):Find a more detailed description of the issue in
atlas-placement-hints
: https://github.com/BlueBrain/atlas-placement-hints/issues/12 with visualizations.The only alternative implementation I can think of would mimic the behaviour of
assert_leaf_node
and require loading a specific hierarchy dictionary to check if a given node has children.@lecriste and @mgeplf please let me know what do you think, thanks