# Reporting NCA bugs

**URL:** <https://discourse.pumas.ai/t/reporting-nca-bugs/1379>\
**Category:** NCA\
**Created:** [February 18, 2026, 8:48pm UTC](https://discourse.pumas.ai/t/reporting-nca-bugs/1379 "2026-02-18T20:48:18Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![donaldlee3](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.pumas.ai/donaldlee3/32/165_2.png) [@donaldlee3](https://discourse.pumas.ai/u/donaldlee3)\
**Post date:** [March 28, 2026, 7:52pm UTC](https://discourse.pumas.ai/t/reporting-nca-bugs/1379/7 "2026-03-28T19:52:50Z")

</div>

Thank you, Arno. That’s perfect.

The only other issue with NCA I recall is with numerical issues as I posted a couple years ago here:

> [@AUC bug with interval](https://discourse.pumas.ai/t/auc-bug-with-interval/990/3):
>
> Hi @vijay, I’ve identified the source of the problem. I have multiple dose data and group by occasion, as opposed to using ii. I still give the read\_NCA time = :time as opposed to time = :tad. It appears that the auc function with a time interval is calculating tad itself for all the occasions, which is resulting in numerical/decimal issues. For example, my last tad should be 27.9999, but if I manually create my own tad column, and give time = :tad to read\_NCA, I will get missing from the a…

Has this been fixed?

---

_[View the full topic](https://discourse.pumas.ai/t/reporting-nca-bugs/1379)._