# Getting warning, but model works well

**URL:** https://discourse.julialang.org/t/getting-warning-but-model-works-well/130850
**Category:** Modelling & Simulations
**Tags:** warning, modelingtoolkit, symbolics
**Created:** [July 18, 2025, 2:59pm UTC](https://discourse.julialang.org/t/getting-warning-but-model-works-well/130850 "2025-07-18T14:59:15Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Bart\_van\_de\_Lint](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bart_van_de_lint/32/212161_2.png) [@Bart\_van\_de\_Lint](https://discourse.julialang.org/u/Bart_van_de_Lint)
#### Post date: [July 18, 2025, 2:59pm UTC](https://discourse.julialang.org/t/getting-warning-but-model-works-well/130850/1 "2025-07-18T14:59:16Z")

</div>

I am getting this warning during `mtkcompile`, while I was not getting it before. It might be related to an update in `StructuralTransformations`. The model still works fine. How can I disable the warning?

```julia
┌ Warning: Internal error: Variable (l0(t))[8] was marked as being in 0 ~ -(stiffness(t))[8] + ifelse(
(len(t))[8] > (l0(t))[8], (0.7853981633974483stiffness_frac*SymbolicAWEModels.get_e_tether(pset)*(Symb
olicAWEModels.get_diameter(psys, 8)^2)) / (len(t))[8], (0.7853981633974483stiffness_frac*SymbolicAWEMo
dels.get_e_tether(pset)*(SymbolicAWEModels.get_diameter(psys, 8)^2)*SymbolicAWEModels.get_compression_
frac(psys, 8)) / (len(t))[8]), but was actually zero
└ @ ModelingToolkit.StructuralTransformations ~/.julia/packages/ModelingToolkit/vyvd9/src/structural_t
ransformation/utils.jl:291

```

---

<div class="post-metadata">

### Author: ![raman\_kumar](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/raman_kumar/32/26782_2.png) [@raman\_kumar](https://discourse.julialang.org/u/raman_kumar)
#### Post date: [July 18, 2025, 3:06pm UTC](https://discourse.julialang.org/t/getting-warning-but-model-works-well/130850/2 "2025-07-18T15:06:30Z")

</div>

Warning are not **error** so your code is working fine. You simply ignore warning.

---

<div class="post-metadata">

### Author: ![Bart\_van\_de\_Lint](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bart_van_de_lint/32/212161_2.png) [@Bart\_van\_de\_Lint](https://discourse.julialang.org/u/Bart_van_de_Lint)
#### Post date: [July 18, 2025, 4:58pm UTC](https://discourse.julialang.org/t/getting-warning-but-model-works-well/130850/3 "2025-07-18T16:58:25Z")

</div>

I am getting this warning hundreds of times, so it is definitely an issue for me, and it is not clear to me what is wrong with my code.

---

<div class="post-metadata">

### Author: ![sablonl](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sablonl/32/217805_2.png) [@sablonl](https://discourse.julialang.org/u/sablonl)
#### Post date: [July 18, 2025, 6:41pm UTC](https://discourse.julialang.org/t/getting-warning-but-model-works-well/130850/4 "2025-07-18T18:41:54Z")

</div>

Does it happen with `@register_array_symbolics` ?  
In my case, the easiest solution was to use Suppressor.jl.

---

<div class="post-metadata">

### Author: ![Bart\_van\_de\_Lint](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bart_van_de_lint/32/212161_2.png) [@Bart\_van\_de\_Lint](https://discourse.julialang.org/u/Bart_van_de_Lint)
#### Post date: [July 18, 2025, 9:05pm UTC](https://discourse.julialang.org/t/getting-warning-but-model-works-well/130850/5 "2025-07-18T21:05:09Z")

</div>

Yes, I do use `@register_array_symbolics`. I did not have this warning before, it came after an update of some package, therefore I don’t want to suppress it.

---

<div class="post-metadata">

### Author: ![ChrisRackauckas](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chrisrackauckas/32/77_2.png) [@ChrisRackauckas](https://discourse.julialang.org/u/ChrisRackauckas)
#### Post date: [July 19, 2025, 2:11am UTC](https://discourse.julialang.org/t/getting-warning-but-model-works-well/130850/6 "2025-07-19T02:11:41Z")

</div>

Open an issue with a reproducer. Generally this message is harmless but it likely shouldn’t be there…
