Dag Kjetsa

I'm trying to make use of the Copernicus node called "statisticsbyid", but am unsure how to interpret the output.
The resolution of my image plane is 1024x1024. I have an image with some separated islands and I have run that through a "segmentbyconnectivity" node to get the id output I need. If I read the area output of the statistics node I find that the smalles island I have has a value of 0.0002. But, if I count the pixels there are 53 pixels in that island. So, how do these numbers correlate? What is the node actually calculating? What does the value 0.0002 on a 1024*1024 pixels image actually mean?

Thanks,

Dag

After doing another post for something else I discovered something that looks like a bug to me.

I have a height field with a size of 1024x1024, and a resolution of 1 (1024x1024 voxels). When I import this into Copernicus (Houdini 21 btw.) I seem to only really get 1023x1023 pixels out of it. See attached image. Around the very edge of the image plane I can see a one pixel sized dark line that has no values (the picker disappears over this line), where there should be information. Or is there something I need to address in sops?

Has someone else had this issue? Could it be a bug?

Thanks,
Dag

Ah. I did not think about that. I can use a uvtomono node. By default the operation is set to Magnitude/Length, so that should do it. Seems like I have to do some serious remapping after this though. First remap to get the result to a normalized 0-1 range and then a second one to get the range into something more useful since I seem to be getting a one pixel dark line on the imported height field (see attached image). But, yes, seems to work. If for some reason this is not how I should do it, do shout out.

@jsmack: thanks!

Dag