Hello Mike,

I believe the "best fit" fit part comes into play when you have set the Resolution property to some value that would allow the chart to start figuring out what the "best fit" would be.  The default behavior if not set though, is to draw a 1 to 1 representation of the data you give it.  It won't cut any corners to render the series lines from point to point.  Increasing the Resolution value causes the chart to reposition things so that it can render the fewest amount of points and still achieve the similar look as before.

My point from before though, was that on a tablet there is a noticeable increase in cpu usage even in my sample, and that it might need to be an option to lower the resolution/data point count on the chart in order to cut down not only on the number of points that you are updating but also the number of geometry that is rendered by the chart.  I would do this for just the tablet version though.  On a desktop/laptop you should be seeing much more acceptable performance.  On my laptop, the sample never got above 13-ish %.

Rob,

I was under the impression that the XamDataChart would generate a "best fit" line graph given a data set so I fed all the data I get to the chart which is roughly 500 points per second. Regardless of how many points I add I still have to "update" the chart around every 50ms in order to attain a smooth scrolling affect so whether I update 275 points (25 of data + 250 for a "moving gap") or 55 points (5 of data and 50 for moving gap after some data processing) I didn't thinnk it would make much difference. I will try this and see if it makes helps with the cpu.

Hi Mike,

I put together a sample that used our developers data and it turns out this looks more like an EEG than an EKG.  Looking at your update code though, I believe we're doing it similarly, except for the while loop and the wave data buffer part.  Although in my case I'm not pulling datapoints from a queue to override the data source, but I'm instantiating new data points entirely.  It shouldn't matter though, yours may be more memory efficient that way.

One thing I notice in our developers sample though, is that the chart looks like a normal EEG without needing to use 4000 data points.  Now I don't know what your EEG looks like with 4000 data points but when I compare my sample with pictures I see on the internet, it looks pretty close.  I attached the sample so you can take a look.  If I bump up the amount of data points to 4000, I do notice a jump in my cpu usage.  Task Manager isn't really the best tool to use for this but on my laptop it was staying around 13% with 4000 data points.  I then tried it out on a Surface Pro tablet (i5 1.7GHz so a bit more powerful than yours) and Task Manager showed between 30 and 40% cpu usage.  From these tests I definitely can see how it could be worse on your tablet.

My conclusion from all of this is that I don't think there is anything wrong with the way you are updating the data.  I think it just comes down to the chart itself trying to render 4000 constantly changing data points on a tablet.  For the tablet, you may need to try playing with the Resolution property on the LineSeries to try and cut down on the number of geometry that is rendered.  Or you'll have to see if you can get away with lowering the data point count so the chart doesn't have as much to render.

Sorry for the confusion.

This is the code I use to update the collection:

waveForm.WaveData.SuspendCollectionChangeNotification();
//_logger.Info(String.Format("Enter OC lock - UpdateWaveFormCollections - {0}", waveForm.WaveChannelName));
// add all the points from the buffer to the data list that are older than the updated LastDisplayedTimeStamp
WaveFormDataPoint data;
while (waveForm.WaveDataBuffer.Count > 0
&& waveForm.WaveDataBuffer.TryPeek(out data)
&& data != null
&& data.TimeStamp < waveForm.LastDisplayedTimeStamp)
{
   if (waveForm.CurrentPosition >= collectionSize)
   {
      waveForm.CurrentPosition = 0;
   }
   WaveFormDataPoint queueitem;
   if (waveForm.WaveDataBuffer.TryDequeue(out queueitem))
   {
      waveForm.WaveData[waveForm.CurrentPosition] = queueitem;
      waveForm.CurrentPosition++;
   }
}

// Add the moving space
if (waveForm.WaveDataBuffer.Count > 0)
{
   int spacesize = (int)(0.5 / waveForm.SecondsBetweenPoints); // half second. quan of samples to use for moving space
   int last = 0;
   for (int p = 0; p < spacesize; p++)
   {
      var emptywavedata =
         new WaveFormDataPoint
         {
            TimeStamp = waveForm.LastDisplayedTimeStamp.AddSeconds(waveForm.SecondsBetweenPoints * p),
            Value = float.NaN
         };
      if (waveForm.CurrentPosition + p >= collectionSize)
      {
         waveForm.WaveData[p - last] = emptywavedata;
      }
      else
      {
         waveForm.WaveData[waveForm.CurrentPosition + p] = emptywavedata;
         last = p;
      }
}

// If the control is not visible the do not notify
// the observable collection of changes
if (IsVisible)
{
   waveForm.WaveData.NotifyChanges();
}

EKG is perfect as well. Just need a really efficient method to plot several graphs at 500Hz.

This is a crappy (not all that bad just annoyed with it right now) little Windows tablet using an Atom N2600 @ 1.6GHz

Hi Mike,

I was under the impression that you were just updating the data points by updating their values rather than replacing them, based on your initial description of your implementation.  Since you are just replacing the items, INotifyPropertyChanged will have no bearing on this.

While I don't have an EEG example, our engineers have given me code for an EKG and I imagine that the update strategy would be similar so I'm throwing a sample together.  Out of curiosity, what kind of tablet are you using?  And just to make sure, as I have seen other posts by you on the Silverlight forums, this is for WPF correct?  I should have asked this initially.