# Warning in SciMLBase about ContinousClock

**URL:** <https://discourse.julialang.org/t/warning-in-scimlbase-about-continousclock/138534>\
**Category:** Modelling & Simulations\
**Tags:** package, sciml\
**Created:** [July 30, 2026, 10:51am UTC](https://discourse.julialang.org/t/warning-in-scimlbase-about-continousclock/138534 "2026-07-30T10:51:19Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![c-nicomar](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/c-nicomar/32/221935_2.png) [@c-nicomar](https://discourse.julialang.org/u/c-nicomar)\
**Post date:** [July 30, 2026, 10:51am UTC](https://discourse.julialang.org/t/warning-in-scimlbase-about-continousclock/138534/1 "2026-07-30T10:51:19Z")

</div>

During precompilation I get this warning. How could I avoid this? I have this version v2.155.1

```julia-auto
SciMLBase
│ ┌ Warning: the bare singleton variant syntax `ContinuousClock` is deprecated, write `ContinuousClock()` instead (near C:\Users\User\.julia\packages\SciMLBase\hLfdZ\src\clock.jl:4)
│ │ caller = eval(m::Module, e::Any) at boot.jl:489
│ └ @ Core .\boot.jl:489
└   

```

---

<div class="post-metadata">

**Author:** ![ufechner7](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ufechner7/32/51363_2.png) [@ufechner7](https://discourse.julialang.org/u/ufechner7)\
**Post date:** [July 30, 2026, 6:54pm UTC](https://discourse.julialang.org/t/warning-in-scimlbase-about-continousclock/138534/2 "2026-07-30T18:54:36Z")

</div>

Welcome to the Julia community!

Hopefully, this warning gets fixed soon, but for the time being, it will just work anyway.

---

<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 31, 2026, 5:27am UTC](https://discourse.julialang.org/t/warning-in-scimlbase-about-continousclock/138534/3 "2026-07-31T05:27:14Z")

</div>

I registered a backport fix.

I recommend updating to SciMLBase v3 since you’re on very old versions now, but at least the patch to v2 will make the warning go away.

---

<div class="post-metadata">

**Author:** ![ufechner7](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ufechner7/32/51363_2.png) [@ufechner7](https://discourse.julialang.org/u/ufechner7)\
**Post date:** [July 31, 2026, 5:39pm UTC](https://discourse.julialang.org/t/warning-in-scimlbase-about-continousclock/138534/4 "2026-07-31T17:39:45Z")

</div>

There is one more warning we get, which might be related therefore I post it here:

```julia-auto
┌ ModelingToolkit
│ [Output was shown above]
└  
┌ ModelingToolkitTearing
│ ┌ Warning: the bare singleton variant syntax `IntegerSequence` is deprecated, write `IntegerSequence()` instead (near C:\Users\ufechner\.julia\packages\ModelingToolkitTearing\GxqLM\src\clock_inference\clock_inference.jl:15)
│ │ caller = eval(m::Module, e::Any) at boot.jl:489
│ └ @ Core .\boot.jl:489
└  

```

---

<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 31, 2026, 5:46pm UTC](https://discourse.julialang.org/t/warning-in-scimlbase-about-continousclock/138534/5 "2026-07-31T17:46:44Z")

</div>

SciMLBase v2 again?

---

<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 31, 2026, 5:57pm UTC](https://discourse.julialang.org/t/warning-in-scimlbase-about-continousclock/138534/6 "2026-07-31T17:57:42Z")

</div>

That one’s not SciMLBase it’s ModelingToolkitTearing’s own `@data ClockVertex` block. Same Moshi deprecation, fixed in ModelingToolkitTearing v1.20.2 (latest is v1.20.3). `]up` should clear it. If it doesn’t move, `]st ModelingToolkitTearing` and whatever is holding it back is the real culprit.