I’ve been trying to run GPA analysis with Slicermorph but it hasn’t been doing anything. I’ve already successfully run ALPACA with multiple data sets to get my landmarks, but when I try to put them into GPA and click the “execute GPA + PCA” button nothing happens. It simply doesn’t run it. I checked the python log to see if I received any kind of error messages in there, and it appears that something is wrong there (although I am not that technically savvy, so I’m not sure what). I’ve tried running GPA with different and smaller landmark data sets and have shut the program down multiple times, but none of that has worked.
I can’t replicate this with two mrk.json files I have. Couple things to check:
Make sure you are using the latest version of the SlicerMorph extension. Go to the extension manager and click “CHeck Updates”. If you are running a version prior to June 12th, you will see an update. If there is no update, it is the latest version.
Make sure you have exactly the same number of landmarks in both files. The error indicates there is a mismatch in the array in somehow.
If you can share two files, we can take a closer look.
I have not tried saving them in a different format. However, it takes so long to produce the files with ALPACA (because I’m doing a couple hundred at a time) that I don’t know how feasible it is for me to redo them as .fcsv files instead of .json
I did just check, and I have not been using the most updated version of Slicermorph. I just updated it and will try running GPA again to see if that fixes the issue. As for the number of landmarks, they should have the same amount. They are files that I auto-landmarked with ALPACA from one source model/landmark file. These are only two of about a couple hundred files that I auto-landmarked with ALPACA. I can’t share the files directly because I can’t upload .json files here, but I was able to put them in a google drive folder, so here is that link to all the files I produced with ALPACA:
You should stop using fcsv and keep them as mrk.json, as eventually fcsv support will be dropped. Earlier we had a bug with a mrk.json reading, but that has been fixed long time ago.