# Error in simulating a PBPK model

**URL:** <https://discourse.pumas.ai/t/error-in-simulating-a-pbpk-model/1198>\
**Category:** Simulation\
**Created:** [July 9, 2025, 4:45am UTC](https://discourse.pumas.ai/t/error-in-simulating-a-pbpk-model/1198 "2025-07-09T04:45:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tesh\_sutha99](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.pumas.ai/tesh_sutha99/32/815_2.png) [@tesh\_sutha99](https://discourse.pumas.ai/u/tesh_sutha99)\
**Post date:** [July 9, 2025, 4:45am UTC](https://discourse.pumas.ai/t/error-in-simulating-a-pbpk-model/1198/1 "2025-07-09T04:45:12Z")

</div>

Hello Pumas community,

I am trying to replicate a PBPK model for ADC. The model is running but when i try to simulate observations it is throwing a warning. It is also showing that the simulated dataframe has infinity values.

```julia
Warning: Interrupted. Larger maxiters is needed. If you are using an integrator for non-stiff ODEs or an automatic switching algorithm (the default), you may want to consider using a method for stiff equations. See the solver pages for more details (e.g. https://docs.sciml.ai/DiffEqDocs/stable/solvers/ode_solve/#Stiff-Problems).
└ @ SciMLBase C:\build\run\_work\PumasSystemImages\PumasSystemImages\julia_depot\packages\SciMLBase\SDjaO\src\integrator_interface.jl:597
SimulatedObservations
grator_interface.jl:597
SimulatedObservations
SimulatedObservations
  Simulated variables: cp_plasma, dv_plasma, cp_bc, dv_bc
  Time: 0:50:350

```

Can you help me resolve this issue?

---

<div class="post-metadata">

**Author:** ![andreasnoack](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.pumas.ai/andreasnoack/32/22_2.png) [@andreasnoack](https://discourse.pumas.ai/u/andreasnoack)\
**Post date:** [July 9, 2025, 6:27am UTC](https://discourse.pumas.ai/t/error-in-simulating-a-pbpk-model/1198/2 "2025-07-09T06:27:12Z")

</div>

It is difficult to say without seeing the model and the maybe some summaries of the data. It could be an error in the model implementation or it could be an issue with the data.