-
Notifications
You must be signed in to change notification settings - Fork 39
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
Pitchfork branching code weirdness #19
Comments
-0.0097 seems close to 0.01 to me. You are right that |
For 2. you mean vertically? In which case the solution is sqrt(ds) = 0.1 which is "large". I could perhaps overwrite the |
1 It still feels strange. I would expect the starting point to be on the horizontal axis, and only after a ds step do we travel on the two branches. 2 But it should be ds vertically, right? The curve is vertical there, so the arclength is the same as the vertical. Maybe I'm confused by something, but I would expect (barring ds adaptation) to see something like a parabola equally spaced. Instead the starting point is much too far away. I think the problem is in |
|
2 But then that's not a step of ds in arclength, it's a much bigger step, no? |
2 Well it is "pseudo" arc length but that just evades the question :D ... There is no point on the branch yet (except the bifurcation point which I discarded up to now). Are you confused by what the docs say or something else? In the method |
Ok, I got it. You expect the first point to be at distance |
MWE:
Also plot just
[br, br2]
and[br, br3]
.The pitchfork is well detected, and the two branches get explored. However,
the base of the two branches is at the same point, whereas I would have expected both branches to have opposite starting points
the starting point is off the horizontal axis by an amount relatively large compared to my ds, whereas I would have expected the starting point to be exactly on the horizontal axis. I guess this is easy to fix by just adding the bifurcation point to the branch.
Are both these expected?
The text was updated successfully, but these errors were encountered: