-
Notifications
You must be signed in to change notification settings - Fork 57
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
[BUG] Projecting neurons in the Landmarks Widget results in incorrect transformation #2285
Comments
Perhaps related: the "brain hemisphere right" landmark group of volume 1099 has an extra unnamed landmark that can't be deleted, throws this error:
|
I deleted the whole landmarks group and recreated it, but the transform error still continues. |
We found that "MB Vertical / Medial Lobe Intersection" is a landmark that exists both in 1099 and in Seymour, but a break at While on the break, I tested whether The end result is that it uses only 3 landmarks to define a 3D transform, and therefore it's very wrong. |
For testing I am using annotation "thermo-KC right" from Seymour, so only 4 KCs are loaded. The 1099 volume has project_id=4. What I did: login via psql to the catmaid_fibsem database and update the string in the class)_instance table:
And finally:
And now 4 landmarks are used. There must have been an encoding error in the string, entirely invisible to the naked eye but javascript compared the two and returned false. |
An issue persists, though: while 4 landmakrs are now being used, the transformation is OK in the antero-posterior axis but is messed up medio-laterally: inverted or worse. |
Further testing shows that when projecting neurons in Seymour's annotation "thermo-KC right" using Seymour's landmark group "brain hemisphere right" to 1099's landmark group "brain hemisphere left" then the transformation is largely correct, barring differences in the individual landmark positions. Whereas when projecting to 1099's "brain hemisphere right" then the neurons are medio-laterally flipped. I have run out of clues to follow to figure this out. |
Here is a view of Seymour's annotation "thermo-KC right" projected to 1099 via "brain hemisphere right" (yellow) landmark group, and to "brain hemisphere left" (orange) landmark group. Notice how the right-to-right is medio-laterally flipped, whereas the right-to-left looks about correct: |
To further add: I projected one KC from the left hemisphere of 1099 (annotation "KC left" with one neuron) to the right hemisphere, and the transformation is correct. So the issue is likely related to projecting across projects: the landmark names and matching work fine locally across the hemispheres of 1099. |
More issues: when transforming right to right, I see at the end only 6 matches, where there should be 8. |
Found the cause: for the second pair, Turns out, there is only 1 landmark under "MB medial lobe tip", assigned to Seymour's "brain hemisphere left" but not to right. This is what has caused so much trouble when matching with other volumes too. |
Finally, |
To add that the GABA FIBSEM volume with pid=7 also seems to have problems: when projecting "thermo-KC right" from "brain hemisphere right" to "brain hemisphere right", one of the landmarks that matches by name somehow is not used. Another issue is that the resulting transformation is rather wrong. May have to do with the landmarks themselves though, again. |
In volume 1099, we attempted to use the 4 landmarks of the right mushroom body, which we checked are named correctly, and the 3D viewer shows them at the correct 3D location relative to traced Kenyon cells.
When we load neurons from Seymour using the latter's "Kenyon Cell right" annotation, or any other annotation, the transformed neurons are shown in the 3D viewer with an inverted anterior-posterior axis, and overly stretched long that same axis.
This image shows the incorrectly transformed Kenyon cells and the volume of the landmarks used:
And this is how they should look like: in blue, the locally partially traced Kenyon cells:
The text was updated successfully, but these errors were encountered: