Fix inconsistencies in merge code #488
Merged
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.
This PR introduces some inconsistencies in the merge code introduced by the ROI merge feature.
The wrong connectivity object was being used as a reference when comparing end state connectivities to determine whether rings have been broken or have undergone a size change.
In certain cases, comments within the code referred to the old merge implementation, so were inconsistent with the actual logic of the code.
Several loops used in the reconstruction of the intrascale matrix were incorrectly indented.
I confirm that I have merged the latest version of
develinto this branch before issuing this pull request (e.g. by runninggit pull origin devel): [y]I confirm that I have permission to release this code under the GPL3 license: [y]