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

Sonar processing limits #67

Open
Noitarud opened this issue May 10, 2024 · 2 comments
Open

Sonar processing limits #67

Noitarud opened this issue May 10, 2024 · 2 comments

Comments

@Noitarud
Copy link

My phone appears to be having troubles with showing data (screen updates slow and dis/reappearing or incomplete graphs).

I notice the first screen has history so this means all the graphs are running. There are no options so I cannot hide and disable pages…

@Staacks
Copy link
Member

Staacks commented May 12, 2024

Can you provide a screenshot and a description of the experimental setup?

The sonar measurement is a bit tricky (and to be honest - if it had not been there since the beginning of phyphox I would no longer include it as a standard experiment) and there are two common problems:
a) Sometimes the timing of sending sound and recording it can be wrong on some devices, so the echo is never recorded and a measurement becomes impossible. I have not seen this in a while, but in earlier version we ran into this problem several times and I would not rule it our entirely.
b) A single missed measurement can lead to very high values, which impacts the autoscaling of the graphs, so other measurements become more or less invisible until the bad measurement is shifted out of the history.

Could it be any of these?

@Noitarud
Copy link
Author

Noitarud commented Jun 11, 2024

It was measuring the distance to a wall so I didn't need a ruler.

Yes, the other issue was inconsistent results (i should see things being still or move away). The tablet i have can play and record sounds at the same time (used camera record and played a song) and the first heard would be through device or shortest path, missing measurements ought not be possible. I can play from two apps at the same time (if both do not want exclusive use), so could probably record twice in the same (if it must).

So ramping is from a missed measurement? Couldn't it have a null input or use a copy of last if it missed something?

My first concern was updating all graphs rather than just the ones on screen would slow it down and harm the results (I was looking at the echo-location tab), though graphs probably aren't that much burden though…

This one is a Galaxy A11, dual mic. Which does it use? Video record: bottom mic is Left,top is Right, loudspeaker on bottom. Some devices have two speakers (the performance would vary between them and together could mar the results).

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

2 participants