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
Out of memory 99 #106
Out of memory 99 #106
Conversation
… memory issues we should only compute for a fraction of the target pointcloud. To compute all neighbors we use a generator.
…lygon's boundaries are not considered within the polygon.
… not overlap. The right and upper boundaries of the tiles should not overlap.
…not have the same order as the base Target pointcloud. For that reason we sequentially partition the target pointcloud.
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.
Looks great! Just some formatting things through.
To fix it could you run prospector (see contributing file in root) and have a look at the issues? Fix the whitespace issues with 'autopep8 -i <filename.py>' (don't use -aggressive as it could actually break your code when you do). After that have a look at the now much shorter prospector complaint list and only fix stuff that make sense to you. Not everything is important but unused imports and unused variables should at least be fixed.
I have checked the issues with prospector and solved them. |
To cover issue #99.
From now on compute_neighborhoods is a generator to be memory efficient. This means the user gets an iterator instead of a result. The user needs to call next(compute_neighborhoods) to iterate over the results.