-
Notifications
You must be signed in to change notification settings - Fork 100
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
temp/raw drop issue #29
Comments
I made some experiments around this. What is important is that "sensor value" we got decreases when device temperature increases. I have verified that by cooling down camera and then measuring sensor value. So sensor value can't be direct temperature value in the same way raw pixel data are. Another thing to notice is that actual pixel values from camera also go down when camera temperature goes up |
Hi. I'm working too. data16 = np.frombuffer(data,dtype=np.uint16) However, i'm agree with you. I think that sensor_value is like a reference (maybe a thermistor, with exponential curve). The actual value give me a difference with know reference and like this i can measure temp. |
Marking as duplicate of #39 since the two are so closely coupled |
Sorry this might be a bit offtopic but that seems the only place where to discuss...
I just wrote a little QT application that uses libseek-thermal (without flat generated).
I then pointed the cam's middle point to an area that was stable ~26°C and
the app logged the centerpoint values with an average over 7 values to a file.
I plotted the values over time and that's what I got
That is a drop of about 10°C over 20 minutes. The original SeekThermal App (Android)
does not show me such a drop, it starts just ~1-2°C off and stays quite stable over time.
So the question is what are they doing in their app to compensate for that drop?
I assume they also get only raw values from the sensor and the rest is in-app-pre-processing...
Can this be corrected with a flat? Or are they using such a curve that I plotted and
compensate their readings against it over time (given that the curve characteristics stays consistent...)?
The text was updated successfully, but these errors were encountered: