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

Improve irregular boundaries #7

Closed
8 tasks done
balazsdukai opened this issue Mar 13, 2020 · 0 comments · Fixed by #16
Closed
8 tasks done

Improve irregular boundaries #7

balazsdukai opened this issue Mar 13, 2020 · 0 comments · Fixed by #16
Assignees

Comments

@balazsdukai
Copy link
Member

balazsdukai commented Mar 13, 2020

Goals:

  • Reduce irregular boundaries in final roof partition
  • Reduce complexity of initial roof partition

Todo:

  • Line regularisation: cluster on distance in general between line segments, not just perpendicular distance

  • Line regularisation: cluster with moving average for each cluster/implement proper hierarchical clustering

  • compute more accurate extend for intersection lines

  • In initial line roof partition (the arrangement prior to graph cut optimisation): insert only the line segments, not full lines

  • do not merge clusters if both contain an intersection line (or split again after clustering?)

Screenshot 2020-05-07 at 10 13 15

  • test on large area

  • remove complexity limit in graph cut optimisation node. Maybe put it in the regularisation node...

  • Make new clustering algorithm faster. 1) Use a binary min heap for the distance table/finding minimum distances, 2) keep for each cluster a std::list with heap handles to the distances involving the cluster (for faster distance update after a merge).

@Ylannl Ylannl self-assigned this Apr 2, 2020
@Ylannl Ylannl mentioned this issue May 17, 2020
Ylannl added a commit that referenced this issue May 17, 2020
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 a pull request may close this issue.

2 participants