# Some numbers need to be exact - not in K or M

**URL:** <https://discuss.saleae.com/t/some-numbers-need-to-be-exact-not-in-k-or-m/798>\
**Category:** Uncategorized\
**Created:** [October 30, 2020, 3:36pm UTC](https://discuss.saleae.com/t/some-numbers-need-to-be-exact-not-in-k-or-m/798 "2020-10-30T15:36:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Brian](https://avatars.discourse-cdn.com/v4/letter/b/97f17d/32.png) [@Brian](https://discuss.saleae.com/u/Brian)\
**Post date:** [October 30, 2020, 3:36pm UTC](https://discuss.saleae.com/t/some-numbers-need-to-be-exact-not-in-k-or-m/798/1 "2020-10-30T15:36:43Z")

</div>

![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/8dad59e1f86b90224e62abee61e16325bae4c610.png)  
For example, the Nrising and Nfalling values in the measurement bubble should not show 1.406M, but rather the exact number of rising or falling edges. The whole reason I’m asking the measurement to count the edges is to get an exact value.

Hopefully this is a very simple thing to change.

---

<div class="post-metadata">

**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\
**Post date:** [November 3, 2020, 10:21pm UTC](https://discuss.saleae.com/t/some-numbers-need-to-be-exact-not-in-k-or-m/798/2 "2020-11-03T22:21:56Z")

</div>

@Brian You have a point! I’m surprised we didn’t catch this earlier. We’ll get this added to the backlog to fix for “Counting” type of measurements.