Hello,
I THINK it is a bug, but not sure, therefore before making an issue i would like some developers input (not sure what are the exact specific steps that generates the problem in the pipeline):
- use wavelet source
- connectivity on wavelet
- select some cells on top, some cells on the bottom and use extract selection
- use extract cells by region and extract only intersected extract intersected (so similar to slice+crinkle)
- use connectivity again
This up to my understanding should give two different regionsIds as they are not touching each other, nevertheless the regionsIds is ‘kept’ from the first connectivity? I think? this ONLY happens to the cell regionIDs and not to the point regionIds which looks like it works (at least from my understanding) correctly.
image of the original wavelet (transparent) and the extracted cells from the selection after second connectivity filter (ie., final result) and it can be seen the two clearly separated regions shows like only one region. (i imagine that it comes from the original connetivity? as if i change the input of the extract selection to the wavelet instead of the connectivity filter this gets as expected, two regions)