You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We created a project, and after a lot of tracing we realized that we didn't record broken slices. So catmaid doesn't know that there should be a gap in the middle of the stack, and distances are wrong. How can we fix this? For images it's easy - just renumber folders, and enter broken slices into catmaid. But what about the traces? Can they easily be moved?
The text was updated successfully, but these errors were encountered:
Hi Sanja,
There isn't, as far as I know, a point-and-click way to do this.
One way to do it is to use psql and directly write an SQL command that, for every coordinate with Z larger than that of a single broken slice, would increase the value of its Z dimension as needed.
Another way to do this is from a python script run from the ipython prompt that gives you access to django and its postgres backend, to do the same.
Let's leave this issue open as a reminder that there should be a UI on the admin side to address this problem of not having configured broken slices ahead of tracing.
Albert
We created a project, and after a lot of tracing we realized that we didn't record broken slices. So catmaid doesn't know that there should be a gap in the middle of the stack, and distances are wrong. How can we fix this? For images it's easy - just renumber folders, and enter broken slices into catmaid. But what about the traces? Can they easily be moved?
The text was updated successfully, but these errors were encountered: