-
Notifications
You must be signed in to change notification settings - Fork 2
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
Fix docs build #31
Fix docs build #31
Conversation
Strange, I pass the tests locally. |
Any way you can fix the tests? change tolerances or something? Docs wont build if tests fail. Thanks for the PR! |
I will play around with parameters and see if it passes the tests. |
Any tips on how to debug why the tests run locally and not here? |
Can you tell me what is going wrong with the test? What is it supposed to be testing and what it finds instead? |
Given two initial guesses, the algorithm finds an orbit only for one of the guesses. |
Can you just check out the branch, run the initial conditions and see if you get the orbit you should, otherwise change the guess? |
Or, significantly increase the starting guess period for the second orbit. |
I just used two identical initial guesses. If I could simulate the CI environment somehow locally, I could perhaps debug why the CI fails but waiting 10 mins every time I make a change is tedious. |
But that's a poor choice no? We want to test that the algorithm can find at least two different periodic orbits, as it should. I thought that's what the test was trying to do (in the second half) |
Does it not work with a big change like 10 units of time? |
Yes I know that it is a poor choice. |
I can try, but why +10? Does Lorenz System have such orbits? The guess of time acts the same as a guess of spatial coordinates. If there is no orbit near with the spatial guess + temporal guess, the algorithm won't converge. |
I am confused: I thoguth you where searching for unstable periodic orbits in the chaotic lorenz system? |
Yes, I know there should be infinitely many of them. But nevertheless, this algorithm doesn't work so well that it would converge to any guess I input. I think the guess has to be quite precise for the algorithm to converge. |
Okay, then let's simply remove the broken test and make a statement in the algorithm doc that the algorithm is not particularly accurate. |
One of the algorithms stopped converging for examples in the docs. I changed the initial guesses and precision. This must have resulted from some changes in other libraries, probably
NonlinearSolve
.