-
Notifications
You must be signed in to change notification settings - Fork 3
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
Trajectory 1D system starts at t = 0, instead of (t, y) clicked #5
Comments
Yeah it probably shouldn’t work like that - good spot!
From: Gerhard Burger <notifications@github.com>
Reply-To: mjg211/phaseR <reply@reply.github.com>
Date: Sunday, 26 August 2018 at 12:52
To: mjg211/phaseR <phaseR@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [mjg211/phaseR] Trajectory 1D system starts at t = 0, instead of (t, y) clicked (#5)
Came across this when using the phasePlaneAnalysis on a 1D function. It's not really a problem, but it might not be what you expect to happen.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#5>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AEVpA_i4mgWpvh-FhwhvPGPsU9wjvn-hks5uUovggaJpZM4WMwG5>.
|
Still unsure on the best way to resolve this, as at present trajectory() returns a single numeric vector t, given that tlim and tstep define t for ALL initial conditions. If trajectories can be plotting in the 1D case with different initial values of t, should it just calculate the numerical solution back to 0 so a single t can be retained, but then plot from only the chosen initial t? |
Hmm, I see the problem... tlim is also xlim in the 1D case. I will think about possible solutions and try some stuff |
It might be weird for 2D systems as well, if you do trajectory(simplePendulum,
y0 = y0,
tlim = c(0, 10),
parameters = 5)
trajectory(simplePendulum,
y0 = y0,
tlim = c(5, 10),
parameters = 5) do you expect the same starting point? |
Very true; it should probably always be computing the trajectory from t=0, and then just plotting based on tlim. |
Came across this when using the phasePlaneAnalysis on a 1D function. It's not really a problem, but it might not be what you expect to happen.
The text was updated successfully, but these errors were encountered: