-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OutOfMemoryError on step without time step size #880
Comments
baggepinnen
added a commit
that referenced
this issue
Oct 12, 2023
The problem here is that this system has one very fast pole, and some very fast poles. When no time-vector is provided, the default time vector tries to be long enough to capture the slow dynamics, but dense enough to capture the fast dynamics. With the change in |
Oh, I understand what you mean: the fast pole is removed.
|
Yeah, the fast pole wasn't observable julia> gram(sys, :o)
4×4 Matrix{Float64}:
1.48543e-6 2.37117e-5 6.53234e-5 4.98637e-5
2.37117e-5 0.000378507 0.00104483 0.000799158
6.53234e-5 0.00104483 0.0176803 0.025
4.98637e-5 0.000799158 0.025 0.0530303
julia> gram(sys, :o) |> svdvals
4-element Vector{Float64}:
0.06599408956924761
0.004809087557537785
0.0002874945673967246
3.685244848996841e-20 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am not sure whether I should report it here, so apologies if this is the wrong place.
throws an
OutOfMemoryError
because the temporal step size is too small. Indeedsize(step(ss(A,B,C,D)).x) = (4, 153847, 2)
, a bit of an overkill for this stable slow system.The text was updated successfully, but these errors were encountered: