You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 'always_replace' and the 'noreplace' options to merge_atlases do not address this.
I hesitate to try and fix because there already seems to be a complex logic regarding the 'always_replace' and the 'noreplace' options, and I am unsure how this would intersect with the issue reported here.
The text was updated successfully, but these errors were encountered:
If two atlas being merged contain an overlapping set of regions, the merged atlas contains double copies of this region.
Toy example that reproduces the bug:
The 'always_replace' and the 'noreplace' options to
merge_atlases
do not address this.I hesitate to try and fix because there already seems to be a complex logic regarding the 'always_replace' and the 'noreplace' options, and I am unsure how this would intersect with the issue reported here.
The text was updated successfully, but these errors were encountered: