Skip to content

Conversation

@Joeycho
Copy link

@Joeycho Joeycho commented Nov 17, 2025

Current:
direction missing.
#3355

PR:
Input image has indexToWorld function. Reuse it.

@Joeycho
Copy link
Author

Joeycho commented Nov 17, 2025

@finetjul

Copy link
Member

@finetjul finetjul left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please reformat your commit message to match semantic release.

xyz[kernelX] = x0[0] + t * (x1[0] - x0[0]);
xyz[kernelY] = x0[1] + t * (x1[1] - x0[1]);
xyz[model.slicingMode] = z;
const xyz = indexToWorld(ijk);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not think it is a drop-in remplacement.
Previous code was not trying to find the location of ijk in the world coordinate space, but more something the location of cVal on the edgeVerts edge.
Maybe it is getPixelPoints that could use indexToWorld

@Joeycho Joeycho changed the title use indexToWorld function, rather than separate calculation Fix (ImageMarchingSquares): use indexToWorld function, rather than separate calculation Nov 18, 2025
@Joeycho Joeycho changed the title Fix (ImageMarchingSquares): use indexToWorld function, rather than separate calculation fix (ImageMarchingSquares): use indexToWorld function, rather than separate calculation Nov 18, 2025
@Joeycho Joeycho changed the title fix (ImageMarchingSquares): use indexToWorld function, rather than separate calculation fix(ImageMarchingSquares): use indexToWorld function, rather than separate calculation Nov 18, 2025
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 this pull request may close these issues.

2 participants