# Issue with ProjectSemiLM

**URL:** https://discourse.slicer.org/t/issue-with-projectsemilm/41438
**Category:** Support
**Tags:** markups-fiducials
**Created:** [February 1, 2025, 12:52am UTC](https://discourse.slicer.org/t/issue-with-projectsemilm/41438 "2025-02-01T00:52:26Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Dlmeyer](https://avatars.discourse-cdn.com/v4/letter/d/779978/32.png) [@Dlmeyer](https://discourse.slicer.org/u/Dlmeyer)
#### Post date: [February 1, 2025, 12:52am UTC](https://discourse.slicer.org/t/issue-with-projectsemilm/41438/1 "2025-02-01T00:52:26Z")

</div>

Hello, I am trying to use the ProjectSemiLM utility to project a field of pseudolandmarks across my dataset of Squamate wrist elements. I have manually placed 6 orientation landmarks on each element, and have selected one out of the sample to be the base mesh on whcih I generated the pseudolandmarks.

When I try this, I reveive the following warning message, which repeats for each elemetn I am trying to project the landmarks on:

“Warning: In vtkMRMLMarkupsNode.cxx, line 3166  
vtkMRMLMarkupsFiducialNode (000002951C72DBB0): vtkMRMLMarkupsNode::GetMarkupPoint method is deprecated, please use GetNthControlPointPosition instead”

I was wondering if there was something wrong with the way that my orientation landmarks are formatted (I have them all saved as .mrk.json files, or if there was some other way I could address this.

Thanks,  
Dalton

---

<div class="post-metadata">

### Author: ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)
#### Post date: [February 1, 2025, 1:45am UTC](https://discourse.slicer.org/t/issue-with-projectsemilm/41438/2 "2025-02-01T01:45:38Z")

</div>

While annoying, it is a warning. You can ignore.

Are lms not projected?

---

<div class="post-metadata">

### Author: ![Dlmeyer](https://avatars.discourse-cdn.com/v4/letter/d/779978/32.png) [@Dlmeyer](https://discourse.slicer.org/u/Dlmeyer)
#### Post date: [February 1, 2025, 2:33am UTC](https://discourse.slicer.org/t/issue-with-projectsemilm/41438/3 "2025-02-01T02:33:30Z")

</div>

No, the lms are not being projected, I had assumed that was why.

This traceback message also comes up:

Traceback (most recent call last):  
File “C:/Users/Dalton/AppData/Local/slicer.org/Slicer 5.8.0/slicer.org/Extensions-33216/SlicerMorph/lib/Slicer-5.8/qt-scripted-modules/ProjectSemiLM.py”, line 198, in onApplyButton  
logic.run(self.modelSelector.currentNode(), self.baseLMSelect.currentNode(), self.baseSLMSelect.currentNode(), self.meshDirectory.currentPath,  
File “C:/Users/Dalton/AppData/Local/slicer.org/Slicer 5.8.0/slicer.org/Extensions-33216/SlicerMorph/lib/Slicer-5.8/qt-scripted-modules/ProjectSemiLM.py”, line 239, in run  
subjectID = [int(x) for x in regex.findall(meshFileName)][0]  
IndexError: list index out of range

---

<div class="post-metadata">

### Author: ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)
#### Post date: [February 1, 2025, 9:48am UTC](https://discourse.slicer.org/t/issue-with-projectsemilm/41438/4 "2025-02-01T09:48:07Z")

</div>

Error suggest there is an issue with the number of landmarks in you samples, but I can’t replicate on my end.

Can you provide a sample test of your LMs?

---

<div class="post-metadata">

### Author: ![Dlmeyer](https://avatars.discourse-cdn.com/v4/letter/d/779978/32.png) [@Dlmeyer](https://discourse.slicer.org/u/Dlmeyer)
#### Post date: [February 1, 2025, 4:26pm UTC](https://discourse.slicer.org/t/issue-with-projectsemilm/41438/5 "2025-02-01T16:26:08Z")

</div>

Absolutely, I just sent you some of them via email. Thank you very much.

---

<div class="post-metadata">

### Author: ![Dlmeyer](https://avatars.discourse-cdn.com/v4/letter/d/779978/32.png) [@Dlmeyer](https://discourse.slicer.org/u/Dlmeyer)
#### Post date: [February 6, 2025, 6:14pm UTC](https://discourse.slicer.org/t/issue-with-projectsemilm/41438/6 "2025-02-06T18:14:26Z")

</div>

Just wanted to update that this issue was solved with the latest update to SlicerMorph! I still had to go in and change many of the file names in order to successfully process the entire dataset, but it worked!

-Thanks so much to the dev team!
