Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Feature/graph analysis identification #28
Feature/graph analysis identification #28
Changes from 23 commits
449c44f
0e51cd6
2f4f78c
1b757ea
03429a4
b4a7f4b
a376541
29d0340
ec51cc8
37a5f9a
cdf5e10
d905ebd
8f40d9e
75081b5
8d585b1
4cda25c
d9586e7
776d67c
878e3c0
d223923
79bd345
acc7874
2d8b943
6803470
a8af146
52e5378
636bce4
b1197bf
308a7e9
359c710
7a99470
1d54eaa
29beff4
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Large diffs are not rendered by default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feature:
Just noticed this now. It'd be useful to also allow identifying nodes with other (custom) classes where we determine the class-to-class mapping. I will add this as an extra small feature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Intuitively it should be slightly faster to combine these two filters into one, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I also think that if numpy does short-circuit evaluation on these things this should be faster. @herbiebradley I don't know if it does, do you?
Concretely: Do you know how numpy handles these type of cases?
Case
select_from_array[np.logical_or(condition_array1, condition_array2)]
Does it first evaluate both
condition_array1
andcondition_array2
in the slice[ ... ]
and thenor
the conditions (in which case it'd probably be slower bc we would calculate the geometry overlaps for shapes which won't agree in class label).Or does it calculate the first element of
condition_array1
and then short-circuit decide if that element ofcondition_array2
even needs to be calculated? (in which case I think it should be slightly faster)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure about
np.logical_or
but if you use base pythonor
and a generator to select then it should short-circuit and may be faster - there are some interesting timing results here on selecting from boolean arrays: https://stackoverflow.com/questions/58422690/filtering-a-numpy-array-what-is-the-best-approachThis file was deleted.