Seasonal sampling with Continental

I am trying to use the seasonal sampling option in the Continental deployment planning, which allows different profile intervals within different date ranges (great idea for a feature, by the way).  I am confused as to where the average interval is applied, or if it is assumed [forced?] to be the same under the different profile intervals.  Related to this, the battery and memory usage does not seem to update correctly.  Finally, does a delayed start still apply? 

Here is what I am trying to do (475 kHz Continental):

10 Nov 2010 - 31 Jan 2011, 60 s profile intervals with 10 s average intervals

31 Jan 2011 - 6 Feb 2011, 1 s profile intervals with 1 s average intervals 

By rough estimates, this should be 150% of 540 Wh and 347 MB.... which is quite different from the deployment planning output. 

Hi Jim,

I've got no experience with the Continental or seasonal sampling, but what's the battery and memory usage if you set up the two deployments separately. Does it match the planning output? Or is that what your rough estimate is based on?

P.J.

Hi PJ, 

It turns out that seasonal sampling requires an average interval equal to the minimum profile interval - 2 s.  That average interval is fixed, even when the profile interval is seasonally changed.  I bench tested this, briefly, during the turnaround before redeployment, and ended up using the following configuration: 

10 Nov 2010 - 31 Jan 2011, 60 s profile intervals with 1 s average intervals

31 Jan 2011 - 10 Feb 2011, 3 s profile intervals with 1 s average intervals 

This leaves me with single-ping data throughout the deployment, and thus worse velocity precision, but it is worthwhile in this case/application.  

Jim

Hi Jim,

This is a software bug! The software is fixed, but is in the test fase. The plan is to release it this week at http://www.nortek-as.com/en/support/software

The workaround is to choose an profile interval equal to or greater than 3 seconds as PJ indicates.

The average interval is the same for both profiling intervals. This will them be limited by the smallest. The average interval must be at least 2 seconds lower than the lowest profile interval.

The delayed start will still apply.

Best regards

Jonas Røstad