Spike reporting incorrect number of span points?

I’m running Spike 4.0.10 on a Linux Mint system (based on Ubuntu). It’s running just fine. However, when looking at the number of points reported on the main window, and looking at the value reported in a .SHR file when doing a sweep record, the sweep record value is higher. Is it possible that the # of points reported on the main window is being divided by 1024 (similar to storage space on some computers) to calculate the number of “k”? For example, when running in “Demo” mode, the # of points reported on the main window in full span is “149k”. But looking at the value reported by the .SHR file says it is actually 153320. Dividing that value by 1024, I get 149.7k, which I could see being rounded to “149k”.
When running the same full span with a BB60C, I get “74k” reported on the main window, but 76661 reported by the .SHR file. Again, dividing this latter value by 1024 gives 74.8k.
Not a real problem, but a curiousity.

[Author]

Posts