Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Meshes not right size, location, or value. #79

Closed
bzenger opened this issue May 17, 2019 · 1 comment
Closed

Meshes not right size, location, or value. #79

bzenger opened this issue May 17, 2019 · 1 comment
Assignees

Comments

@bzenger
Copy link

bzenger commented May 17, 2019

Please follow these instructions for your issue to be worked on:

Description

The new version of cleaver is scaling and creating meshes not like the old version, and that do not match the original segmentation. This is not a simple "translation" problem but something much more significant. I am unaware of how to fix this or why it would be.

See in the screen shots attached below. Red is the old version of cleaver, blue is the new version of cleaver.

Also, the "foreground" mesh number is now set to 0 and the background is set to 1, which is annoying for our programs that use the old format.
Archive.zip

image

Steps to Reproduce

I created a simple segmentation of a cylinder and meshed them with identical (default) settings of both cleaver versions.

Important notes:

  1. The cleaver loading of the file took much longer in the newer version than the older version. I am not sure why that would be. Cleaver also took significantly longer to mesh in the newer version than the older version. By significant I mean a difference of several minutes to create the mesh.
  2. Loaded these identical files in as .nrrd files of a segmentation
  3. Cleaved, meshed, and saved them out as .mat files for matlab (according to the viewer)
    ** This was all done in the GUI, not command line **

Versions

Mac OS: 10.13.6
Cleaver Versions: 2.3.1 and 2.4 (latest master)
ITK 4.13
QT5.9

@allywarner allywarner self-assigned this Jun 3, 2019
@allywarner
Copy link
Contributor

Should be fixed with with latest PR. Although, Cleaver is still running slower on OSX. Release to follow.

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

No branches or pull requests

2 participants