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

Query regarding rescaling of data #3

Open
akkupant opened this issue Apr 8, 2024 · 0 comments
Open

Query regarding rescaling of data #3

akkupant opened this issue Apr 8, 2024 · 0 comments

Comments

@akkupant
Copy link

akkupant commented Apr 8, 2024

Dear Dr. Higham,

I hope this message finds you well. Firstly, I'd like to extend my gratitude for developing the particle tracking toolbox. It appears to hold great promise for my research endeavours, particularly in my exploration of thin film dynamics on water surfaces.

Attached are images that I believe could assist in addressing my queries. In my recent experiments, I've utilised the toolbox to process video footage captured at a high frame rate of 800 fps. Here's a breakdown of my process:

1.) I begin by working with images sized at 1376 x 857 pixels, providing the necessary scaling factor (pix/mm) at the outset of processing.

2.) Subsequently, I opt for a grid size of 172 x 107.

The output from the toolbox yields vector fields presented as a 172 x 107 matrix (not scaled in mm on x and y axes). Please see image 2

However, I find myself pondering two key points:

Should the vector fields be rescaled into millimetres separately or should the code provide scaled values of UX and UY ( in mm/s or m/s).

Given that the code does not provide x and y data as part of its output, should I manually derive this information based on the scaling factor?

I appreciate any guidance or insights you can offer on these matters. Thank you for your time and consideration.

Warm regards,
Anurag Pant (PhD)

step 1
Step2

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