Skip to content
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

Particle tracing in 3D by holographic data using LODESTAR #213

Open
avi-xd opened this issue Aug 12, 2024 · 1 comment
Open

Particle tracing in 3D by holographic data using LODESTAR #213

avi-xd opened this issue Aug 12, 2024 · 1 comment

Comments

@avi-xd
Copy link

avi-xd commented Aug 12, 2024

Hi, I have been using the LODESTAR model to get the traces of particles for my off-axis Holographic data. I used the model and got results quite accurately on the X-Y plane. However, on the Z axis, the model could not predict very efficiently, as it gave sudden jumps (spikes) between the traces (I am uploading the output).

63134570-9623-4df1-b0d9-e86bd4a80680

But then I checked with the example uploaded by you guys in 07.track_3D_holography.ipynb

I got the same results as in the paper https://www.nature.com/articles/s41467-022-35004-y. But when I plotted the traces in 3D, they also had similar jumps (pics attached below).

In 2D (x-y plane), result is

65806f64-c9a9-493b-ad83-26d3c81b87aa

and similar result in 3D looks like

cdd58616-c7f7-4fb0-9252-6468726e9b30

I am not able to figure out what causes these sudden spikes in the results and how to tackle it and get better results. Any help or key insight will be highly appreciated.

I can provide the exact code I have used if needed. Thanks

@avi-xd
Copy link
Author

avi-xd commented Aug 25, 2024

@BenjaminMidtvedt any inputs here? Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant