Issues with display of optimism

Hello,
I am trying to analysis the left atrial shapes, but the outcome of optimism is awkward. How to deal with it? Thank you!

The picture shows the mean shape of my data.

If you turn the isosurface off and move the PCA mode slider back and forth, are the particles going crazy, or do they look as you might expect? I’m trying to figure out if it’s a surface reconstruction problem, or if the optimization has gone wrong.

Hi, Thank you for the response. When I move the PCA mode slider, the particles are reasonable as expected. So it might be a surface reconstruction problem. I tried three reconstruction options in the software, the results are all weird.

[

xby

xbyzju@126.com

](头像签名)

---- Replied Message ----

From | Alan Morris via ShapeWorksnotifications@shapeworks.discoursemail.com |

  • | - |
    Date | 12/14/2022 08:46 |
    To | xbyzju@126.com |
    Subject | [ShapeWorks] Issues with display of optimism |

| amorris
December 14 |

  • | - |

If you turn the isosurface off and move the PCA mode slider back and forth, are the particles going crazy, or do they look as you might expect? I’m trying to figure out if it’s a surface reconstruction problem, or if the optimization has gone wrong.

Are these the left atrium shapes from the shapeworks use case? Or are they from elsewhere?

They are our own data from left atrial CT Angiography.

---- Replied Message ----

From | Alan Morris via ShapeWorksnotifications@shapeworks.discoursemail.com |

| amorris
December 20 |

  • | - |

Are these the left atrium shapes from the shapeworks use case? Or are they from elsewhere?

Can you try (after the optimization) to reduce the number of shapes to just a few (e.g. two) and see if the problem persists. I am wondering if it is a particular shape.

To do this, open the xlsx file and cut all but the first two subject lines, then re-load in Studio.

Also, is this the latest ShapeWorks Studio? 6.3.2?

I tried to reduce the number of shapes to 4 and the results are as follows:
Surface reconstruction method:
Legacy:


Mesh Warping based:

Distance Transform Based( default parameters)

The version of ShapeWorks Studio is 6.3.0

Is there a chance you could make a zip of the 4 patient project and point me to it? You can email me at amorris@sci.utah.edu

OK, I have sent the shapes to you. Happy new year! :smiley:

Can you try this project (no need to re-optimize) with the 6.3.1 or 6.3.2 release? I ran the shapes you sent and see a similar problem with the 6.3.0 release, but loading the project in 6.3.1/6.3.2 and the mesh warping is fixed.

I don’t see anything on our release notes for 6.3.1 about the mesh warping, but we must have fixed some bugs in that time.

Hi, I tried this project with the 6.3.2 release. But there is the similar problem with mesh reconstruction.

In this case, the particles look a bit mixed up to me. If you run through the first few PCA modes, do you see particles crossing paths?

Can you try a lower number of particles, such as 64 or 128 and see what that looks like to confirm whether it is a mesh reconstruction problem or a problem with the model itself?

Hi, Amorris
I tried 512 particles with more shapes (40 cases), the results were good as follows.


However, when i tried to analysis the full data (220 cases), it reported mistakes like this.


I sent a log file to shapeworks-dev-support@sci.utah.edu. Thank you!

I haven’t seen the log come through on shapeworks-dev-support yet. Could you try sending it to me directly at amorris@sci.utah.edu?

I have sent it to you. Thank you!

Thanks! I’ve fixed the crash if you want to try the development build of ShapeWorks:

I am not sure about the mesh warp problem, but I added additional diagnostic messages that may help us track it down if you try this version and we check the logs.

Dear Alan Morris:
I tried the new version and the crash did not happen. However, the mean mesh constructed is still a little wired. The attachment is the mean mesh. In addition, I have a question: if the mesh reconstructed was not perfect, are the results of PCA component score still correct? If I want to classify the outcomes with shape statistic model, I shall compare the PCA component score exported by Shapeworks, right? Thank you very much!

[

xby

xbyzju@126.com

](头像签名)

---- Replied Message ----

From | Alan Morris via ShapeWorksnotifications@shapeworks.discoursemail.com |

  • | - |
    Date | 02/11/2023 13:30 |
    To | xbyzju@126.com |
    Subject | [ShapeWorks] Issues with display of optimism |

| amorris
February 11 |

  • | - |

Thanks! I’ve fixed the crash if you want to try the development build of ShapeWorks:

GitHub

Releases · SCIInstitute/ShapeWorks

ShapeWorks. Contribute to SCIInstitute/ShapeWorks development by creating an account on GitHub.

I am not sure about the mesh warp problem, but I added additional diagnostic messages that may help us track it down if you try this version and we check the logs.

(Attachment MeshWarp.vtk is missing)

Dear Alan Morris:
I tried the new version and the crash did not happen. However, the mean mesh constructed is still a little wired. The attachment is the mean mesh. In addition, I have a question: if the mesh reconstructed was not perfect, are the results of PCA component score still correct? If I want to classify the outcomes with shape statistic model, I shall compare the PCA component score exported by Shapeworks, right? Thank you very much!

[

xby

xbyzju@126.com

](头像签名)

---- Replied Message ----

From | Alan Morris via ShapeWorksnotifications@shapeworks.discoursemail.com |

  • | - |
    Date | 02/11/2023 13:30 |
    To | xbyzju@126.com |
    Subject | [ShapeWorks] Issues with display of optimism |

| amorris
February 11 |

  • | - |

Thanks! I’ve fixed the crash if you want to try the development build of ShapeWorks:

GitHub

Releases · SCIInstitute/ShapeWorks

ShapeWorks. Contribute to SCIInstitute/ShapeWorks development by creating an account on GitHub.

I am not sure about the mesh warp problem, but I added additional diagnostic messages that may help us track it down if you try this version and we check the logs.