-
Notifications
You must be signed in to change notification settings - Fork 7
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
platform integrated sampling rates #71
Comments
Comment from @bastienqueste Sampling frequency is actually more often a function of platform capabilities than sensor capabilities. Seaglider limited to 0.2Hz unless inclusion of scicon board (which is no longer manufactured), because of old TT8 processor and single-thread processing. Analog sensors can essentially be sampled as fast as the platform can handle. Sensors that do onboard analog to digital conversion are limited by their A2D converters (generally 10s to 100s of Hz so not actually the bottleneck). Most often, the issue is if they do any onboard calculations and logging, which slows it to several Hz or 10s of Hz. The only real limitation is the platform. Typical settings for salinity are 0.2Hz for Seaglider, ~0.5 to 1Hz for Slocum if I recall correctly, and ~2Hz for SeaExplorer for the average user, and up to 16Hz for power users (or anybody with a fast Legato set up to log onbaord the sensor). |
Comment from @gkrahmann As far as I remember for old Slocums with a persistor the default sampling rate is 1 every 4 seconds, i.e. 0.25 Hz. This can be changed to 1 every 2 seconds or 0.5 Hz when the science persistor has 'free' time, meaning when you do not have too many other sensors. |
Section 3
Data sheets associated with sensors provide power consumption estimates based on sampling rates. However these are not always the sampling rates that are typically used/possible during deployment.
CT sensors are limited by the processing system of the platform they are integrated with
This issue is associated with PR #55 and issues #49 and #48
The text was updated successfully, but these errors were encountered: