Closed remyeltorro closed 3 months ago
Hey @remyeltorro ,
Thanks for the report!
Just wondering, if you do this:
tracker.volume = ((0, volume[1]), (0, volume[0]), (-1e5, 1e5))
does that get rid of the "ghost points"? btrack
takes dimensions as XYZ, whereas most image stacks are ZYX. Also, I'm suprised that the tracking works properly if you set the volume to None. I can remove the line that checks, but that is currently the desired behavior.
Hello @quantumjot, thank you for your reply,
On version 0.6.4, setting the volume works perfectly without creating ghost points,
tracker.volume = ((0, volume[1]), (0, volume[0]), (-1e5, 1e5))
I can also get away with not setting the -z dimension as such (since my data has no -Z dimension):
tracker.volume = ((0, volume[1]), (0, volume[0]))
and it works like a charm. I think I just wanted confirmation that setting the volume was mandatory after version 0.6.4. The strange result I noticed was with version 0.6.3 but I migrated to 0.6.4 since then.
You can consider the case closed, Best,
Hello,
I encountered a bug when migrating from bTrack 0.6.3 to 0.6.4 in the method tracker.to_napari(). Before, I could get away with not setting the tracker volume as setting it created some sort of bug, with for example:
used to give weird ghost points in the trajectories (I suppose a problem of interpretation of 3D points in a 2D image, I don't know if it was a problem with my line or a bug). Anyway, I had no problem by not writing this line above.
With the new version 0.6.4, I get the following error when not setting the volume:
The assertion in to_napari prevents me from using the default parameter (which is the following line in to_napari(). I'm not sure if this behavior is intended or not, maybe setting the volume has always been mandatory but I used to do it wrong or there was a problem in 0.6.3 that has been fixed in 0.6.4, provided I set the volume.
As a complement, this was my tracking config made with the napari-btrack plugin:
Thank you for your attention,